Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Tue, 2 Jul 2013 17:47:58 -0400
From: Rich Felker <>
Subject: Re: Why add stubs to network/ether.c?

On Tue, Jul 02, 2013 at 01:27:20PM -0700, Isaac wrote:
> Yes, I know this is a pretty small issue.
> But commit fbcd8204 (add stubs for additional legacy ether.h functions)
> is likely to bloat a full static busybox by a few bytes, for no additional
> gain.  Could stubs like these be kept separate from functional code?

Well the tradeoff is between making the .a file significantly larger
for each .o file we add, and making binaries a couple bytes larger.
I'm not sure what the right decision is here. We could try to assemble
lots of stubs together in one file I suppose. I'm open to ideas on
what ppl think is best.


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.