From: "Dave Korn" <dk@artimi.com>
To: "'binutils'" <binutils@sourceware.org>
Subject: RE: ld resulting long command line arguments when calling collect2 workaround
Date: Thu, 08 Apr 2004 17:46:00 -0000 [thread overview]
Message-ID: <NUTMEGRWr2c7IWnObpV000003de@NUTMEG.CAM.ARTIMI.COM> (raw)
In-Reply-To: <NUTMEGhmhVHL74TheTt000003d6@NUTMEG.CAM.ARTIMI.COM>
> -----Original Message-----
> From: binutils-owner On Behalf Of Dave Korn
> Sent: 08 April 2004 14:08
> > -----Original Message-----
> > From: binutils-owner On Behalf Of Ian Lance Taylor
> > Sent: 08 April 2004 00:20
>
> > "J. Grant" writes:
>
> > > However, the problem is that ld/g++ seems to "expand" the
> > @make.objects
> > > file and pass all the filenames to the objects again on the
> > command line
> > > to collect2 (which appears to do the final linking and
> > creation of elf
> > > etc). collect2 has the same problem with command line
> > argument limit
> >
> > I don't know what expands the @make.objects argument. I very much
> > doubt that there is any code in gcc or collect2 or ld which expands
> > that argument. If you are using cygwin, then perhaps the
> cygwin shell
> > expands it.
>
> WRS' cygwin-x-vxworks toolchain implements that feature.
> It may have been
> ported into the cygwin native tools as well, I'm not sure.
BTW, the exact same discussion has come up just now on the cygwin list: see
http://www.cygwin.com/ml/cygwin/2004-04/msg00285.html
and followups, in particular the one that recommends a solution at
http://cygwin.com/ml/cygwin/2004-03/msg01300.html
If JG wants more help, it would be appropriate to join the cygwin list,
since ISTM this is cyg-specific rather than binutils-specific.
http://www.cygwin.com/cygwin/lists.html
cheers,
DaveK
--
Can't think of a witty .sigline today....
prev parent reply other threads:[~2004-04-08 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 23:13 J. Grant
2004-04-07 23:20 ` Ian Lance Taylor
2004-04-08 13:09 ` Dave Korn
2004-04-08 17:46 ` Dave Korn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=NUTMEGRWr2c7IWnObpV000003de@NUTMEG.CAM.ARTIMI.COM \
--to=dk@artimi.com \
--cc=binutils@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).