[parisc-linux] Re: hppa-linux gcc-3.0.3:

JoŽl Soete jso@europay.com
Tue, 19 Feb 2002 16:49:40 +0100

Hey Matthias,

Just a stupid question: "/usr/lib/gcc-snapshot/" is there where you put
your sources gcc-snapshot sources?

Thanks for help,

                    Klose                To:     "John David Anglin" <dave@hiauly1.hia.nrc.ca>                     
                    <doko@cs.tu-b        cc:     jso@europay.com (JoŽl Soete), carlos@baldric.uwo.ca,              
                    erlin.de>            parisc-linux@lists.parisc-linux.org                                       
                                         Subject:     Re: [parisc-linux] Re: hppa-linux gcc-3.0.3:                 
                    10:47 PM                                                                                       

John David Anglin writes:
> > Thanks for advise but I speek well about the new (annonced on
> > http://www.gnu.org/software/gcc/gcc.html: ...The next major release,
> > 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 just uploaded the gcc-snapshot_20020216 build to incoming (without
any extra patches).

To use this snapshot, you should set the following environment


Unset these variables before building Debian packages destined for an
upload to ftp-master.debian.org.

The snapshot packages doesn't build automatically. I had to restart
the build due to bash problems (the same you saw as well).


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.