Linux PARISC architecture development
 help / color / mirror / Atom feed
From: "Joel Soete" <jsoe0708@tiscali.be>
To: "Randolph Chung" <tausq@debian.org>
Cc: "Matthias Klose" <doko@cs.tu-berlin.de>,
	debian-hppa@lists.debian.org, debian-gcc@lists.debian.org,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: gcc-3.2 -> gcc-3.3 transition on hppa
Date: Thu, 20 Mar 2003 19:06:36 +0100	[thread overview]
Message-ID: <3E689FC400004700@ocpmta1.freegates.net> (raw)
In-Reply-To: <3E68A24B00000CC9@ocpmta6.freegates.net>

Hi Randolph,

>>
>>> I am looking to rebuild gcc-3.3 64bits to rebuild the last kernel 2.4
>to
>>> conitnue my investigation about smp(64bits) [which failled to boot on
>a
>>N4000
>>> when compile d with gcc-3.2 get from unofficial-debs].
>>
>>If you are working on 64-bit, I would advise staying with 3.0.4 for
>>now.... no one has tested 3.3 hppa64-linux-gcc at all, so it will just
>>be introducing more unknowns into the problem.
>>
>Ok I am gonna try to rebuild it with gcc-3.0.
>
Well just a small follow up to say that I had not much success with gcc-3.0
(64bits).

Also I did some other test:
this same kernel (smp64) boots well on a b2k (pa8600 up),
it boots also well on the N4000 when I 'disable' the second cpu?

(It seems to fail before 'Add swap...' but not sure because I notice that
all boot blabla is not output to the console [ie compare to dmesg nothing
is print out before 'sym53c8xx: at PCI...']?)

I will so try to ack dump_analyser to see how may I got analyse of the piminfo
which I grab from the two processor.

See you,
    Joel


---------------------------------
Vous surfez avec une ligne classique ?
Economisez jusqu'à 25% avec Tiscali Complete !
Offre spéciale : première année d'abonnement offerte.
... Plus d'info sur http://complete.tiscali.be

  parent reply	other threads:[~2003-03-20 18:06 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15968.40812.741982.606734@gargle.gargle.HOWL>
     [not found] ` <15969.1828.456001.122737@gargle.gargle.HOWL>
2003-03-02  4:59   ` [parisc-linux] Re: gcc-3.2 -> gcc-3.3 transition on hppa Randolph Chung
2003-03-02  5:40     ` John David Anglin
2003-03-02  5:40     ` John David Anglin
2003-03-02  9:24       ` M. Grabert
2003-03-02  9:24       ` M. Grabert
2003-03-02 17:01         ` Randolph Chung
2003-03-02 17:01         ` Randolph Chung
2003-03-02 18:50         ` John David Anglin
2003-03-02 18:50         ` John David Anglin
2003-03-03 14:27     ` Joel Soete
2003-03-03 14:27     ` Joel Soete
2003-03-03 16:17       ` John David Anglin
2003-03-03 16:17       ` John David Anglin
2003-03-03 16:24         ` Randolph Chung
2003-03-03 17:22           ` Joel Soete
2003-03-09 20:06     ` Matthias Klose
2003-03-09 20:06     ` Matthias Klose
2003-03-09 20:27       ` John David Anglin
2003-03-09 20:27       ` John David Anglin
2003-03-09 20:45         ` Randolph Chung
2003-03-09 20:45         ` Randolph Chung
2003-03-12 17:33     ` Joel Soete
2003-03-12 17:33     ` Joel Soete
2003-03-12 17:35       ` Randolph Chung
2003-03-12 17:35       ` Randolph Chung
2003-03-12 17:53         ` Joel Soete
2003-03-12 17:53         ` Joel Soete
2003-03-14 12:48           ` Joel Soete
2003-03-14 12:48           ` Joel Soete
2003-03-14 13:17             ` Matthew Wilcox
2003-03-14 16:31               ` Joel Soete
2003-03-14 16:31               ` Joel Soete
2003-03-18 18:14                 ` b.gunreben
2003-03-18 18:14                 ` b.gunreben
2003-03-18 18:53                   ` John David Anglin
2003-03-18 18:53                   ` John David Anglin
2003-03-18 19:02                     ` Randolph Chung
2003-03-18 19:02                     ` Randolph Chung
2003-03-18 19:16                       ` John David Anglin
2003-03-18 19:16                       ` John David Anglin
2003-03-18 20:21                         ` Randolph Chung
2003-03-18 20:55                           ` John David Anglin
2003-03-20 17:51                             ` Joel Soete
2003-03-20 18:13                               ` John David Anglin
2003-03-20 18:23                                 ` John David Anglin
2003-03-20 18:23                                 ` John David Anglin
2003-03-21 12:44                                   ` Joel Soete
2003-03-21 12:44                                   ` Joel Soete
2003-03-21 13:36                                     ` Matthew Wilcox
2003-03-21 15:07                                       ` Joel Soete
2003-03-20 18:13                               ` John David Anglin
2003-03-20 17:51                             ` Joel Soete
2003-03-18 20:55                           ` John David Anglin
2003-03-18 20:21                         ` Randolph Chung
2003-03-18 21:59                     ` John David Anglin
2003-03-18 21:59                     ` John David Anglin
2003-03-16 22:52               ` Michael S.Zick
2003-03-16 23:06                 ` Matthew Wilcox
2003-03-16 23:17                   ` Michael S.Zick
2003-03-20 18:20                     ` Joel Soete
2003-03-14 13:17             ` Matthew Wilcox
2003-03-20 18:06           ` Joel Soete [this message]
2003-03-20 18:06           ` Joel Soete
2003-03-02  4:59   ` 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=3E689FC400004700@ocpmta1.freegates.net \
    --to=jsoe0708@tiscali.be \
    --cc=debian-gcc@lists.debian.org \
    --cc=debian-hppa@lists.debian.org \
    --cc=doko@cs.tu-berlin.de \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=tausq@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