public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Chris Majewski <majewski@cs.ubc.ca>
To: gcc-help@gcc.gnu.org
Subject: Re: --with-gnu-ld ?
Date: Tue, 03 Jul 2001 15:04:00 -0000	[thread overview]
Message-ID: <Pine.SOL.4.21.0107031504080.4688-100000@okocim.cs.ubc.ca> (raw)

Yeah.  The problem  seems to  be that  if my  current compiler  uses a
non-gnu   ld,   --with-gnu-ld   confuses   the  gcc   build.   Setting
LD=/path/to/gnu/ld  seems  to have  done  the  right  thing, though  I
haven't tested it yet.. 
-chris

On Tue, 3 Jul 2001, Peter Kurpis wrote:

> Oops.  I could've sworn I had done this, but my notes say:
> 
> 	configure ... --with-ld=/path/to/gnu/ld --with-gnu-ld ...
> 
> The first tells where to look (as opposed to just using PATH, I think),
> the second one tells the build system that it can generate code assuming
> that the GNU ld is being used.
> 
> > Is  not! '--with-gnu-ld'  is an  option, but  '--with-gnu-ld=blah' did
> > nothing for me. 
> > -chris
> > 
> > On Tue, 3 Jul 2001, Peter Kurpis wrote:
> > 
> > > 
> > > > To configure  gcc3.0 to use a different  ld than the one  used by your
> > > > previous  compiler,  you have  to  do  an "export  LD=/path/to/gnu/ld"
> > > > before running  configure.  This really should be  a configure option,
> > > > no? Something like '--with-gnu-ld=/path/to/gnu/ld'.
> > > 
> > > It is.
> > > 
> > 
> > 
> 


             reply	other threads:[~2001-07-03 15:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-03 15:04 Chris Majewski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-03 13:20 Peter Kurpis
2001-07-03 13:57 ` Chris Majewski
2001-07-03 14:35   ` Alexandre Oliva
2001-07-03 12:49 Chris Majewski
2001-07-03 13:15 ` Chris Majewski

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=Pine.SOL.4.21.0107031504080.4688-100000@okocim.cs.ubc.ca \
    --to=majewski@cs.ubc.ca \
    --cc=gcc-help@gcc.gnu.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).