Re: [Boost-build] Error message: gcc.link.dll actions too long (max 102400):

Subject: Re: [Boost-build] Error message: gcc.link.dll actions too long (max 102400):
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2011-07-08 14:11:06

On 7/8/2011 11:56 AM, Matthew Chambers wrote:
> On 7/6/2011 2:10 PM, Jürgen Hunold wrote:
>>
>> Use response files. On gcc they are known as "linker input files".
>>
>> The attached patch works with gcc-4.6 and maybe all 4.x.
>> Developed on windows, but works on Kubuntu 11.04.
>> Feedback welcome.
>> If this works for other, I can try to get this into Boost.Build.
>
> I'd vote for it. I routinely build on MSVC and GCC and I much prefer the
> crazy long compile commands to be hidden away in a response file. When a
> source file fails to compile, I typically start editing that file and/or
> its includes and instead of rerunning bjam, I simply copy/paste the
> failed compile command and run it directly. This technique is much nicer
> on MSVC than GCC.

I've often done the same when using MSVC, so doing the same with GCC 
would be welcomed. One problem though is what versions of GCC support 
response files? And hence how do we deal with the ones that do not. Do 
we not support them? Or do we have multiple link actions for 
with/without response support?

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org (msn) - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail