From: Eric Botcazou <ebotcazou@libertysurf.fr>
To: Timothy Borgeaud <tim.borgeaud@csc.mrc.ac.uk>
Cc: 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:53:00 -0000 [thread overview]
Message-ID: <200409231047.33057.ebotcazou@libertysurf.fr> (raw)
In-Reply-To: <41527FC6.6050600@csc.mrc.ac.uk>
> >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.
Ok, that's the problem.
> Building with /opt/hi pointing to the place where all the stuff is actually
> installed causes me a problem with conflicting copies of libiconv.
Oh! yes, this tricky libiconv conflict. I think it can be solved by making
sure that the bootstrap compiler and the final compiler will see the same
libiconv library. You can browse Bugzilla for more detailed info.
--
Eric Botcazou
prev parent reply other threads:[~2004-09-23 8:48 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
2004-09-23 11:53 ` Eric Botcazou [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=200409231047.33057.ebotcazou@libertysurf.fr \
--to=ebotcazou@libertysurf.fr \
--cc=gcc@gcc.gnu.org \
--cc=tim.borgeaud@csc.mrc.ac.uk \
/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).