From: Daniel Jacobowitz <drow@false.org>
To: Don Lindsay <lindsayd@cisco.com>, binutils@sourceware.org
Subject: Re: binutils-2.16.92 build failures, Linux X PPC, SPARC.
Date: Thu, 27 Apr 2006 03:58:00 -0000 [thread overview]
Message-ID: <20060427022217.GA14227@nevyn.them.org> (raw)
In-Reply-To: <20060427011405.GA17615@bubble.grove.modra.org>
On Thu, Apr 27, 2006 at 10:44:06AM +0930, Alan Modra wrote:
> > I ran the same script on Solaris 8, bootstrapping from a GCC 3.4.3 instead
> > of /usr/bin/gcc. The bootstrap failed with:
> >
> > /bin/ksh $src/gcc/mkconfig.sh tconfig.h
> > ./xgcc -B./ -B$i/sparc-sun-solaris2.8/bin/
> > -isystem $i/sparc-sun-solaris2.8/include
> > -isystem $i/sparc-sun-solaris2.8/sys-include
> > -L$b/gcc/../ld -c -o crt1.o -x assembler-with-cpp
> > $src/gcc/config/sparc/sol2-c1.asm
> > ./as: error: $b/gcc/.libs/as-new does not exist
>
> This also doesn't look like a binutils problem, but rather that the gcc
> build can't find an as yet uninstalled gas.
Oh, now I know what's going on - this must be a combined tree
consequence of the new gcc/as handling. Might want to report it to
gcc's bugzilla.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-27 2:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 17:19 binutils-2.16.92 build failure on SPARC Martin Michlmayr
2006-04-17 19:14 ` Martin Michlmayr
2006-04-17 20:57 ` Andreas Schwab
2006-04-18 0:25 ` Martin Michlmayr
2006-05-04 18:45 ` Daniel Jacobowitz
2006-05-16 8:36 ` Martin Michlmayr
2006-04-27 2:22 ` binutils-2.16.92 build failures, Linux X PPC, SPARC Don Lindsay
2006-04-27 3:14 ` Alan Modra
2006-04-27 3:58 ` Daniel Jacobowitz [this message]
2006-05-04 18:46 ` binutils-2.16.92 build failure on SPARC Daniel Jacobowitz
2006-05-04 18:59 ` Martin Michlmayr
2006-05-04 19:00 ` Daniel Jacobowitz
2006-05-04 20:28 ` Martin Michlmayr
2006-05-17 21:51 ` Daniel Jacobowitz
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=20060427022217.GA14227@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sourceware.org \
--cc=lindsayd@cisco.com \
/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).