This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: GCC 4.1: Buildable on GHz machines only?
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: Andrew Haley <aph at redhat dot com>, rth at redhat dot com
- Cc: Per Bothner <per at bothner dot com>, tromey at redhat dot com, Ranjit Mathew <rmathew at gmail dot com>, GCC <gcc at gcc dot gnu dot org>, GCJ <java at gcc dot gnu dot org>
- Date: 05 May 2005 16:57:48 -0300
- Subject: Re: GCC 4.1: Buildable on GHz machines only?
- References: <426EFE00.3060903@3am-software.com><20050427025707.GA20956@nevyn.them.org><20050427053042.GA1317@redhat.com> <426F2611.7060801@3am-software.com><426FD0DC.50601@codesourcery.com> <427962FC.5000305@bothner.com><4279C184.6050909@gmail.com> <m3oebpu47j.fsf@localhost.localdomain><427A3F08.4000109@bothner.com><17018.16701.719032.745892@cuddles.cambridge.redhat.com>
On May 5, 2005, Andrew Haley <aph@redhat.com> wrote:
> Per Bothner writes:
>>
>> We could also save time by making --disable-static the default.
>> Building static libraries is not very useful on other than
>> embedded-class systems.
> I <empahsis>strongly</emphasis> agree.
The savings of creating static libraries would be small if we
refrained from building non-PIC object files. This is exactly what
--tag disable-static for compilations accomplishes, and we had a patch
to use that in our tree for some time, but RTH ran into a (probably
libtool) bug on alpha that led him to revert the change, and then
didn't provide enough info for anyone else without access to an alpha
box to figure out what the problem was and then try to fix it :-(
--
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}