Linux PARISC architecture development
 help / color / mirror / Atom feed
From: joel.soete@freebel.net
To: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
Cc: Matthew Wilcox <willy@debian.org>,
	Joel Soete <joel.soete@freebel.net>,
	Randolph Chung <tausq@debian.org>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] gcc-3.2 experimental debs
Date: Tue, 23 Apr 2002 19:16:08 +0200 (CEST)	[thread overview]
Message-ID: <1019582168.3cc596d87ba8a@webmail.tiscalinet.be> (raw)
In-Reply-To: <20020423111903.A8545@systemhalted>

Hello Carlos,

Quoting "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>:

> > > "Stack pointer and cr30 do not correspond!
> > > Dumping virtual address stack instead
> > > 
> > > Dumping Stack from ... to ...:
> > > 
> > > Humm as it appends as well with telnet as ssh I suspect a inetd
> problem?
> > 
> > I'd bet on gcc-3.2 miscompiling something in the network part of the
> kernel,
> > personally.
> >
> 
> Tested today.
> 
> Happens in the 3.1 main branch aswell (don't remember it previously
> happening).
> Maybe I shouldn't be recommending the use of 3.1 as a cross compiler?
> ;)

I also notice it on 3.1 about two mount ago (that is why I do another try with 3.2)


> 
> I'll kdb on a serial tommorow morning and see what is causing it to
> die.
> 

I would also to do so. But I had the bad idea to co the last gcc release
(yesterday and today) to rebuild the toolchain.
But gcc build seems to be broken (step 4.2 of your procedure):

gcc -c -DIN_GCC    -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes   -DHAVE_CONFIG_H    -I. -Ijava
-I/GNU-Dev/parisc-linux/src/gcc/gcc -I/GNU-Dev/parisc-linux/src/gcc/gcc/java
-I/GNU-Dev/parisc-linux/src/gcc/gcc/config
-I/GNU-Dev/parisc-linux/src/gcc/gcc/../include
/GNU-Dev/parisc-linux/src/gcc/gcc/java/parse.c -o java/parse.o
/tmp/ccj2Nlrs.s: Assembler messages:
/tmp/ccj2Nlrs.s:148746: Error: Field out of range [-262144..262143] (-263392).
make[1]: *** [java/parse.o] Error 1
make[1]: Leaving directory `/GNU-Dev/parisc-linux/build/gcc/gcc'
make: *** [all-gcc] Error 2

Last week co did not try to build any java.
Any idea or work-around?

Joel

PS1: about step 4.2 of your howto-xc, I notice a small difference between html
and pdf (in html you use gcc option "enable-shared" in pdf "disable-shared").
But this not the cause of the above problem.

PS2: I also make an apt-get dist-upgrade (with ftp.de.debian.org) so that native
gcc is now 3.0.4-5 (I think it was already installed last week)




-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)

  reply	other threads:[~2002-04-23 17:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-21 13:05 [parisc-linux] gcc-3.2 experimental debs Joel Soete
2002-04-21 15:25 ` Matthew Wilcox
2002-04-23 15:19   ` Carlos O'Donell Jr.
2002-04-23 17:16     ` joel.soete [this message]
2002-04-23 17:24       ` John David Anglin
2002-04-23 21:47       ` Carlos O'Donell Jr.
2002-04-24 13:42         ` joel.soete
2002-04-24 13:50       ` joel.soete
2002-04-21 15:53 ` Randolph Chung
2002-04-22  6:18   ` joel.soete
  -- strict thread matches above, loose matches on Subject: below --
2002-04-19 22:16 Randolph Chung

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=1019582168.3cc596d87ba8a@webmail.tiscalinet.be \
    --to=joel.soete@freebel.net \
    --cc=carlos@baldric.uwo.ca \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=tausq@debian.org \
    --cc=willy@debian.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