This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: ia64 linux doesn't bootstrap
----- Original Message -----
From: "Jim Wilson" <wilson@redhat.com>
To: <tprince@computer.org>
Cc: <gcc@gcc.gnu.org>
Sent: Tuesday, October 22, 2002 12:30 PM
Subject: Re: ia64 linux doesn't bootstrap
> >I was unaware of the sourceforge gdbf95 project, which provides a more
> >functional gdb than I had seen before.
>
> I don't know about gdb Fortran support. Perhaps you are seeing problems
> which are Fortran specific rather than IA-64 specific.
Not unless trying to step through gcc code when there are g77 built files included is considered Fortran specific. gdb works fine
with the same build on linux-ia32 and cygwin, and so does the newer .rpm from sourceforge for ia64.
>
> > I've tried to build gdb-5.2.1 with
> >gcc-3.3, and it failed with many complaints about illegal code.
>
> You will have to be more specific. I just tried building gdb-5.2.1 with
> a 021014 gcc snapshot, and I didn't have any problems building it.
Since there were many diagnostics about violation of standards, such as about the pointer aliasing, I thought maybe options such
as -fno-strict-aliasing or -traditional might be needed, but saw no improvement. I couldn't find a clear reason for the build to
die where it did consistently.
> I did
> have a problem building dejagnu-gdb-5.2.1, but that was a binutils/gcc
> mismatch. ld tries to pretty-print a "mktemp is dangerous" warning by reading
> the debug info, and gets confused because it doesn't have DW_FORM_strp support.
> That is fixed by using a newer binutils. I don't feel like going to that
> much trouble at the moment though.
I've been shooting in the dark trying to figure out which binutils to use. 2.13 died while building with gcc-3.3; 2.12.91 appeared
to work fine, gave good testsuite results, and cured some of my gcc testsuite failures.
>
> It would also be possible to get a similar gcc/gdb mismatch, since older gdbs
> won't have DW_FORM_strp support, and current gcc is likely to emit them.
>
> > It did
> >succeed with a buggy pre-3.0 gcc; there were I think 254 unexpected errors in
> >testsuite. Maybe that's acceptable?
>
> No, that isn't an acceptable number of gdb failures, but you might have to
> live with it for now if you aren't interested in trying to fix gdb problems
> yourself.
Since someone has been working on adding Fortran-specific support to gdb-5.1.1 on sourceforge, which I do need, and that version
appears to work well enough, I'm not inclined to work on a version which isn't likely to help anyone. I'm only trying to get
adequate versions of binutils and gdb going so that I could diagnose gcc failures.
>
> Jim
Thanks,
Tim
-------------------------------------------
Introducing NetZero Long Distance
Unlimited Long Distance only $29.95/ month!
Sign Up Today! www.netzerolongdistance.com