public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Guertin <andrew.guertin@uvm.edu>
To: gcc-help@gcc.gnu.org
Subject: Force to not use system ld / compiling on AIX
Date: Thu, 11 Mar 2010 23:24:00 -0000	[thread overview]
Message-ID: <4B99531A.1070706@uvm.edu> (raw)

I'm trying to compile gcc 4.2.4 on AIX. The AIX installation has a system copy 
of gcc 3.3.2 installed. When compiling, the system gcc uses the system ld, which 
runs out of memory (I have a 32MB ulimit). I would like to use a copy of gnu ld, 
which I have installed in $HOME/local, as gnu ld has options for reducing memory 
usage. However, no matter what I've tried so far the system ld has been used.

Things I have done, mostly in combination:
Set $PATH so that $HOME/local/bin is searched first
Configured with --with-ld=$HOME/local/bin/ld
Set $LD=$HOME/local/bin/ld, both during configure and make
Set $CFLAGS="-B$HOME/local/bin"
Manually run the affected gcc command with $PATH="$HOME/local/bin" (nothing 
else), $LD set, and with the option -B$HOME/local/bin
...Probably some other things, too.

Nothing has worked. The system ld is still used in all cases.

During configure, the messages
searching for powerpc-ibm-aix5.3.0.0-ld ... $HOME/local/bin/ld
searching for ld ... $HOME/local/bin/ld
(or something like them, don't have them in front of me) are printed. Setting 
$PATH got the second one away from system ld, setting $LD was required for the 
first one. Still, when actually compiling, the system ld is used.

Any ideas, either on how to force my copy of ld to be used, or how to work 
around the problem?

Thanks,
--dolphinling

             reply	other threads:[~2010-03-11 20:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 23:24 Andrew Guertin [this message]
2010-03-12  9:30 ` Cedric Roux
2010-03-12 15:56   ` dolphinling
2010-03-13  2:29 ` dolphinling
2010-03-16 14:59   ` Ian Lance Taylor
2010-03-16 16:14     ` dolphinling
2010-03-18  0:51       ` Ian Lance Taylor

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=4B99531A.1070706@uvm.edu \
    --to=andrew.guertin@uvm.edu \
    --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).