public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Timothy Borgeaud <tim.borgeaud@csc.mrc.ac.uk>
To: Eric Botcazou <ebotcazou@libertysurf.fr>,  gcc@gcc.gnu.org
Subject: Re: Odd problem with building 3.4.2 on Solaris (use of as and ld)
Date: Thu, 23 Sep 2004 11:49:00 -0000	[thread overview]
Message-ID: <41527FC6.6050600@csc.mrc.ac.uk> (raw)
In-Reply-To: <200409222322.51563.ebotcazou@libertysurf.fr>

Eric Botcazou wrote:

>>What I'm trying to do is build version 3.4.2 with the prefix /opt/hi and
>>which will use the gnu binutils which will also be in /opt/hi (actually
>>they are in place already but /opt/hi is currently a link to a temporary
>>space).
>>
>>If I build 3.4.2 with just --prefix=/opt/hi everything works ok and I
>>end up with a working version of 3.4.2 that uses /usr/ccs/bin.
>>
>>However if I use the configure options:
>>
>>--with-gnu-as --with-as=/opt/hi/bin/as
>>
>>and
>>
>>--with-gnu-ld --with-ld=/opt/hi/bin/ld
>>    
>>
>
>Just to be sure: are GNU as and GNU ld installed where you tell the configure 
>script they are?
>
>  
>
No, when I build gcc /opt/hi actually points to an empty area. Building 
with /opt/hi
pointing to the place where all the stuff is actually installed causes 
me a problem with
conflicting copies of libiconv. It's a bit of a mess because I'm 
building a version of gcc
designed to run from /opt/hi on a machine with a bunch of stuff in 
/usr/local/.
I suppose I might have to remove the conflicting packages from 
/usr/local/ which is
not really a problem but means I have to be more careful about where 
/opt/hi points
during various installs as the system will be more dependent upon 
/opt/hi rather than
/usr/local/.

>>Which is what I expect. The --with-gnu-as --with-as=/opt/hi/bin/as
>>options seem to trigger the build into assuming Gnu as is being used to
>>perform the build as well as configuring the new compiler to use this tool.
>>    
>>
>
>Note that the line you pasted starts with ./xgcc.  The newly built compiler 
>attempts to compile its libgcc, so it will invoke /opt/hi/bin/as and 
>/opt/hi/bin/ld as you instructed it to do.
>
>  
>
Thanks. I see that when /opt/hi/bin/ld etc are not found then the build 
uses /usr/bin/ccs/ld.
Which is why my fudge of linking /usr/bin/ccs/as to /usr/local/bin/as 
(Gnu) works.

Tim

  reply	other threads:[~2004-09-23  7:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-22 16:42 Timothy Borgeaud
2004-09-22 23:16 ` Eric Botcazou
2004-09-23 11:49   ` Timothy Borgeaud [this message]
2004-09-23 11:53     ` Eric Botcazou

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=41527FC6.6050600@csc.mrc.ac.uk \
    --to=tim.borgeaud@csc.mrc.ac.uk \
    --cc=ebotcazou@libertysurf.fr \
    --cc=gcc@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).