This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Questions about ``[PATCH] GCC side of .eh_frame_hdr support (take 3)''
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: obrien at FreeBSD dot org
- Cc: Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>, jakub at redhat dot com, java at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: 05 May 2002 03:03:08 -0300
- Subject: Re: Questions about ``[PATCH] GCC side of .eh_frame_hdr support (take 3)''
- Organization: GCC Team, Red Hat
- References: <200204241809.g3OI9gJ15955@latour.rsch.comm.mot.com><20020426092948.D32482@sunsite.ms.mff.cuni.cz><200204262248.g3QMmX340100@latour.rsch.comm.mot.com><20020430134026.D45632@dragon.nuxi.com>
On Apr 30, 2002, "David O'Brien" <obrien@FreeBSD.org> wrote:
> On Fri, Apr 26, 2002 at 05:48:33PM -0500, Loren James Rittle wrote:
>> platform. I have no idea how widespread this problem is/was; for some
>> reason libtool insists upon incrementally building libjava.so (to work
>> around perceived command line length limitations even though the
>> entire unbroken command line seems to run fine on this platform).
> Interested in making a libtool patch to stop doing that? :-)
This would be trivial. Libtool doesn't measure the exact command-line
length, just a power of two or so. Since it can't know for sure how
much additional command-line space the compiler driver is going to
add, measuring the exact length is kind of pointless. You can
override the measured value by setting lt_cv_sys_max_cmd_len in your
environment. Look for this variable name in ltconfig for the gory
details.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer