From: Hans-Peter Nilsson <hp@bitrange.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] note non-building architectures
Date: Tue, 10 May 2005 03:47:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.58.0505092109540.86763@dair.pair.com> (raw)
In-Reply-To: <42756233.5080809@gnu.org>
On Sun, 1 May 2005, Andrew Cagney wrote:
> As part of getting ready for GCC 4, I've found that a number of arches
> don't build with gcc-3.4 when using gdb_mbuild.sh. As an aid, and to
> stop me and presumably others from going round in circles, I've updated
> the MAINTAINERS file to both reflect current reality note the problem.
Eh... What is your current reality and why don't I see the
problem you see for cris-elf that warrants marking it as broken?
There was a build issue before for sim/cris, but it's been fixed
to the best of my knowledge. (FWIW in a hackish way, but with
the same effect to the generated sim/cris files as a proper fix.
The proper fix has been ok'd by fche FWIW, I just haven't
regened all CGEN files for all other simulators and tested them;
it's kind of low-priority.) That issue seems to match what you
allude to by "(sim/cris/modelv10.c:4181
crisv10f_engine_run_full?)"
I build sim/cris just now (beware, cutnpaste with wrapping):
/tmp/hptmp/src/configure --target=cris-axis-elf && make all
... in short, no problems.
I also built with gdb_mbuild.sh same host, no problems:
...
cris-elf ...
... /tmp/hptmp/src/configure --target=cris-elf --enable-gdb-build-warnings=,-Werror --enable-sim-build-warnings=,-Werror
... make cris-elf
... run cris-elf
... cleanup cris-elf
... cris-elf built
...
Of course, that was with this obvious patch to make
gdb_mbuild.sh build cris-elf (at least it *seemed* necessary):
--- /home/hp/combined/src/src/gdb/MAINTAINERS Mon May 9 21:45:37 2005
+++ ./MAINTAINERS Tue May 10 03:23:30 2005
@@ -67,8 +67,7 @@ the native maintainer when resolving ABI
avr --target=avr ,-Werror
Theodore A. Roth troth@openavr.org
- cris --target=cris-elf broken
- (sim/cris/modelv10.c:4181 crisv10f_engine_run_full?)
+ cris --target=cris-elf ,-Werror
d10v OBSOLETE
And that's a gcc-3.4 on a i686:
hydra-13:hp:~: rpm -q gcc
gcc-3.4.2-6.fc3
hydra-13:hp:/tmp/hptmp/obj: gcc -v
Reading specs from /usr/lib/gcc/i386-redhat-linux/3.4.2/specs
Configured with: ../configure --prefix=/usr
--mandir=/usr/share/man --infodir=/usr/share/info
--enable-shared --enable-threads=posix --disable-checking
--with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-java-awt=gtk
--host=i386-redhat-linux
Thread model: posix
gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)
I've also build with the configure line above (in a gcc-combined
tree) on x86_64-unknown-linux-gnu (FC4t2, which uses a
gcc-4.0-derivate: gcc-4.0.0-2). No problems. Same thing on i686
FC2, (gcc-3.3.3-7) no problems.
What problem do you see and on what host, and have you updated
since Mar 24 with no local patches, at least none related to the
cris-elf build issue mentioned above?
brgds, H-P
next prev parent reply other threads:[~2005-05-10 2:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 23:14 Andrew Cagney
2005-05-01 23:32 ` Mark Kettenis
2005-05-01 23:54 ` Andreas Schwab
2005-05-02 15:58 ` Andrew Cagney
2005-05-02 16:35 ` Mark Kettenis
2005-05-02 16:50 ` Stan Shebs
2005-05-10 3:47 ` Hans-Peter Nilsson [this message]
2005-05-19 16:53 ` Andrew Cagney
2005-05-19 19:31 ` Hans-Peter Nilsson
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=Pine.BSF.4.58.0505092109540.86763@dair.pair.com \
--to=hp@bitrange.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.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