public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Emil Block <blime@his.com>
To: Hugh Sasse Staff Elec Eng <hgs@dmu.ac.uk>
Cc: gcc-help@gcc.gnu.org
Subject: GCC 3.1.1 Build Problem
Date: Wed, 31 Jul 2002 14:59:00 -0000	[thread overview]
Message-ID: <3D485D60.E2230BEF@his.com> (raw)
In-Reply-To: <Pine.GSO.4.44.0207301648050.9747-100000@neelix>

Hugh Sasse Staff Elec Eng wrote:
> 
> On Tue, 30 Jul 2002, Emil Block wrote:
> 
> > Hugh Sasse Staff Elec Eng wrote:
> > >
> > > On Tue, 30 Jul 2002, Emil Block wrote:
> > >
> > > >
> > > > I am getting  the following error message during the build of GCC 3.1.1, and
>         [...]
> > > > -isystem /usr/local/sparc-sun-solaris2.7/include  -m64"  "LD=/usr/ccs/bin/ld"
> > >
> > > I think this is your problem. You need to build the latest binutils
> > > first, this will give you gnu-as and gnu-ld.
> 
> This statement is because it will not build (in my experience) with
> Sun's as and Sun's ld.  Binutils will, however, so you can use it
> as the stepping stone to a working Gcc.
> > >
> > > Next time you configure DON'T use --with-gnu-as and --with-gnu-ld;
> > > DO use
> > > configure --with-as=/usr/local/bin/as  --with-ld=/usr/local/bin/ld
> > >
> > > with the correct path to configure, gnu ld and gnu as.
> > > If you don't do this then the Java build will
> > > insist on finding /usr/ccs/bin/as and will fail because it won't
> > > accept the right options.
> 
> This is one of the places where it will blow up if the sun utils are
> used.
> 
> > Thanks for the fast response, but I'm a little confused.
> 
> No problem, and I'll explain more clearly
> >
> > I didn't configure with --with-gnu-as and --with-gnu-ld.  This is the
> > command I used:
> 
> no, but if you do that after building binutils you will get some
> progress.
> >
> > configure --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld --disable-nls
> 
> This will almost certainly fail at some point.  GCC builds more happily
> with binutils.  This makes some kind of sense because it is code from
> another Gnu project, such that GCC people have access to it.
> 
> If for some reason you cannot use gnu as and gnu ld then I am at a loss
> as to how to help you.  Others may be able to, however.
> >
> > Emil Block
> 
> I hope this helps.
> >
>         Hugh


Hugh 

Thanks for your assistance. I followed your suggestion, and downloaded the
latest binutils from Sun Freeware for Solaris 2.7. I still received the same
build error message; however, based on your comment about the Sun AS and LD, and
the error message:

 "mksh: Fatal error in reader: = missing from replacement macro reference"

I checked and determined that the command "make bootstrap" was picking up the
Sun MAKE instead of the GNU MAKE because of the directory order in my PATH. The
following provided a successful build:

 "/usr/local/bin/make bootstrap" 

Thanks again!

Emil Block

       reply	other threads:[~2002-07-31 21:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.44.0207301648050.9747-100000@neelix>
2002-07-31 14:59 ` Emil Block [this message]
2002-07-30  7:53 Emil Block
2002-07-30  8:08 ` Hugh Sasse Staff Elec Eng

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=3D485D60.E2230BEF@his.com \
    --to=blime@his.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=hgs@dmu.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).