This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Always include elf.lo?


On 5/21/07, Pedro Alves <pedro_alves@portugalmail.pt> wrote:
Mike Frysinger escreveu:
> On 5/21/07, Pedro Alves <pedro_alves@portugalmail.pt> wrote:
>> Nick Clifton wrote:
>> >> Does anyone object to always compiling elf.lo for BFD, regardless of
>> >> the target?  I haven't tried it, but looking at the tangled
>> >> dependencies I think this will mean all of $elf too.
>> >
>> > This does seem to be overkill.   Unless there is a good reason why GDB
>> > cannot be modified I would prefer not bloat the non-ELF versions of the
>> > BFD library in this way.
>>
>> Isn't bfd normally used as a static lib?  If so, then only gdb
>> would suffer the extra "bloat", which is needed anyway.
>> Perhaps the only real bad effect would added build time.
>
> i guess you're implying that the option "--enable-shared" is
> discouraged and effectively not supported ?

Where did you get that from?  Where does always adding elf.lo
suddenly turns into "discouraged" and "not supported" ?

The "Isn't bfd normally used as a static lib?" part was a
real question.  Notice the *normally*.

you're saying that bloating the library is OK because normally bfd is static -mike


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]