From: "Joël Soete" <jso@europay.com>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: carlos@baldric.uwo.ca, jso <jso@europay.com> (Joël Soete),
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: hppa-linux gcc-3.0.3:
Date: Mon, 18 Feb 2002 18:53:49 +0100 [thread overview]
Message-ID: <OFB6528EDF.C6603F22-ONC1256B64.00615768@com> (raw)
David,
Ok I just launch the download of binutils snapshot dated of today.
I will then follow the 'recipe'.
Than again for all,
Joel
PS: I would try natively (on my palinux box directly) with MACH=3Dhppa-linux
i.e.: ~/source/binutils/configure --host=3Dhppa-linux ... ?
=
=20
"John David =
=20
Anglin" To: jso@europay.com (Jo=EBl =
Soete) =20
<dave@hiauly1.h cc: carlos@baldric.uwo.ca, p=
arisc-linux@lists.parisc-linux.org =20
ia.nrc.ca> Subject: Re: [parisc-linux] =
Re: hppa-linux gcc-3.0.3: =20
=
=20
18-02-02 05:41 =
=20
PM =
=20
=
=20
=
=20
> Thanks for advise but I speek well about the new (annonced on
> http://www.gnu.org/software/gcc/gcc.html: ...The next major release, GCC
> 3.1,...) gcc release 3.1.
I am building 3.1 experimental regularly from the main gcc cvs source.
I have built glibc with it. You probably should get the cvs binutils
because it contains a long branch related fix which will cause a seg
fault early in the bootstrap. You can avoid it by using "-O2" in
stage1. I have a couple of small fixes that need to go in regarding
linking with milli and pthreads routines. The gcc testsuite (expect)
seems to trigger a parisc-linux bug which fills /var with page fault
error mesages.
I am currently trying to get dw2 unwinding working.
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX:
952-6605)
**********************************************************************
This e-mail and any attachments to it may contain confidential information =
which is strictly intended for the use of the authorised recipient. If you=
have received this e-mail in error, please delete it and notify the sender=
by replying to this e-mail.
Thank you for your co-operation.
**********************************************************************
next reply other threads:[~2002-02-18 17:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-18 17:53 Joël Soete [this message]
2002-02-18 18:03 ` [parisc-linux] Re: hppa-linux gcc-3.0.3: John David Anglin
-- strict thread matches above, loose matches on Subject: below --
2002-02-20 6:36 Joël Soete
2002-02-19 17:03 Joël Soete
2002-02-19 21:57 ` Matthias Klose
2002-02-19 15:49 Joël Soete
2002-02-19 14:43 Joël Soete
2002-02-19 15:58 ` John David Anglin
2002-02-18 14:54 Joël Soete
2002-02-18 16:41 ` John David Anglin
2002-02-18 21:47 ` Matthias Klose
2002-02-18 21:54 ` John David Anglin
2002-02-18 10:19 Joël Soete
2002-02-18 14:29 ` Carlos O'Donell Jr.
2002-02-18 16:25 ` John David Anglin
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=OFB6528EDF.C6603F22-ONC1256B64.00615768@com \
--to=jso@europay.com \
--cc=carlos@baldric.uwo.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@lists.parisc-linux.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: 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