From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb@sources.redhat.com
Subject: Re: GDB 5.3.91 available
Date: Wed, 03 Sep 2003 02:42:00 -0000 [thread overview]
Message-ID: <20030903024238.GA2423@nevyn.them.org> (raw)
In-Reply-To: <200309030236.h832aZ2G032503@duracef.shout.net>
On Tue, Sep 02, 2003 at 10:36:35PM -0400, Michael Elizabeth Chastain wrote:
> ac> GDB 5.3.91 (a pre-release of GDB 6.0) is available for download.
> ac> ftp://sources.redhat.com/pub/gdb/snapshots/branch/
>
> Just shoot me ...
>
> First gcc HEAD ICE's during in the bootstrap. When I go to
> date-search it, I find two different dates with two different ICE's.
> No idea when gcc HEAD will be available for testing again.
>
> So I back up to an old version of gcc HEAD, and my BuildGcc.pl coughs up:
>
> assembler not found: /berman/fsf/_today_/berman/install/target/native/binutils/HEAD/bin/as at /berman/home/mgnu/migbat/BuildGcc.pl line 128.
>
> That's funny, I wonder if I screwed up my scripts.
>
> [mgnu@berman _today_]$ ls /berman/fsf/_today_/berman/install/target/native/binutils/HEAD/bin/
> addr2line ld readelf
> ar nm size
> c++filt objcopy strings
> gprof objdump strip
> i686-pc-linux-gnu-as ranlib
>
> That ain't cool. It looks like binutils HEAD has a regression bug
> in the name handling for installing 'as'.
>
> Fortunately, regression-searching binutils is a lot easier than
> regression-searching gcc. In fact someone is likely to say 'aha'
> before I even get a proper bug write-up.
It's either my fault or my fault and the autoconf author's fault.
Please send me a config.log.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-09-03 2:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 2:36 Michael Elizabeth Chastain
2003-09-03 2:42 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-03 2:55 Michael Elizabeth Chastain
2003-09-03 3:24 ` Daniel Jacobowitz
2003-09-02 14:52 gdbadmin
2003-09-04 17:47 ` Joel Brobecker
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=20030903024238.GA2423@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=mec@shout.net \
/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