public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Kenneth Lareau <elessar@numenor.org> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/6969: cannot build gcc-3.1 with binutils-2.12.1 on solaris8 Date: Sat, 08 Jun 2002 14:26:00 -0000 [thread overview] Message-ID: <20020608212601.10825.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/6969; it has been noted by GNATS. From: Kenneth Lareau <elessar@numenor.org> To: Mark Mentovai <mark@moxienet.com> Cc: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, niki.waibel@gmx.net Subject: Re: bootstrap/6969: cannot build gcc-3.1 with binutils-2.12.1 on solaris8 Date: Sat, 8 Jun 2002 14:19:26 -0700 Unfortunately, I'm running into this same issue, and using both of the work- arounds you mention (simultaneously, even) doesn't fix the problem. Checking the configure output, the excluded files you mention are being included. Could there be something else that's being missed? Kenneth Lareau elessar@numenor.org On Sat, 08 Jun 2002 14:27:33 -0400 Mark Mentovai <mark@moxienet.com> wrote: > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p > r=6969 > > gcc/configure does not attempt to detect whether ld is GNU ld unless you > specify a path to ld using --with-ld. It defaults to assuming that GNU ld > is not in use, which causes the target macro files necessary for use with > GNU ld to not be included. The same applies for as. The excluded files are > gcc/config/sparc/sol2-gld.h, gcc/config/sparc/sol2-gld-bi.h for ld, and > gcc/config/sparc/sol2-gas-bi.h for as. > > In this particular case, the omission of sol2-gld-bi results in link_arch > not including an emulation name to pass ld; GNU ld requires this and > defaults to elf32_sparc, while Solaris ld is capable of determining whether > 32- or 64-bit operation is desired based on the format of the supplied > object files. > > As a workaround, configure with "--with-gnu-as --with-gnu-ld" to force the > use of the GNU tools, or "--with-as=/usr/local/bin/as > --with-ld=/usr/local/bin/ld" to force gcc/configure to detect whether as and > ld are the GNU versions. My preference is for the former. > > The fix would involve making gcc/configure set with_gas and with_gnu_ld > appropriately based on the as and ld that will be used by the compiler > before running gcc/config.gcc. gcc/configure checks for which as and ld > will be used a bit later in the process, so this would most likely involve a > minor reordering. > > Mark >
next reply other threads:[~2002-06-08 21:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-08 14:26 Kenneth Lareau [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-06-08 11:36 Mark Mentovai 2002-06-07 20:26 niki.waibel
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=20020608212601.10825.qmail@sources.redhat.com \ --to=elessar@numenor.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).