Re: work around libtool to fix alpha libgcj build

[Alexandre Oliva <aoliva at redhat dot com>]

On Feb 11, 2005, David Daney <ddaney@avtrex.com> wrote:

> Alexandre Oliva wrote:
>> On Feb 11, 2005, Andrew Haley <aph@redhat.com> wrote:
>> 
>>> Alexandre Oliva writes:
>>> 
>>>> On Feb 11, 2005, Andrew Haley <aph@redhat.com> wrote:
>>>> 
>>>> 
>>>>> Richard Henderson writes:
>>>>> 
>>>>>> now libgcj.a, the static library, is built with -fPIC.  I mentioned
>>>>>> this to tromey on irc, and he thought that while it was
>>>>>> unfortunate, it'd be ok.
>>>> 
>>>>> That ought to be a huge advantage, because it'll only be necessary to
>>>>> compile each java file once, rather than twice.
>>>> 
>>>> But only if you were to compile them with --tag disable-static.
>>>> Otherwise, you compile them twice, but only use one of them.
>> 
>>> Can we not fix this?
>> We probably can.  I just have no idea of how to accomplish this with
>> automake.  Basically, you want to add --tag=disable-static before (or
>> right after) --tag={CC,CXX,GCJ} --mode=compile.
>> 

> Probably a naive question, but why not fix libtool so we don't have to
> trick it into doing the right thing?

What do you mean, fix?

Unless you tell libtool you're not interested in the static object
files, how could it magically learn at compile time that, later on,
you're only going to use the PIC object files for linking?

-- 
Alexandre Oliva             http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}