This is the mail archive of the mailing list for the GCC 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: Questions about ``[PATCH] GCC side of .eh_frame_hdr support (take 3)''

On Apr 30, 2002, "David O'Brien" <> 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 (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

Alexandre Oliva   Enjoy Guarana', see
Red Hat GCC Developer                  aoliva@{,}
CS PhD student at IC-Unicamp        oliva@{,}
Free Software Evangelist                Professional serial bug killer

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