From: joel.soete@freebel.net
To: Randolph Chung <randolph@tausq.org>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] compiling kernels with gcc-3.1
Date: Fri, 12 Jul 2002 11:49:48 +0200 (CEST) [thread overview]
Message-ID: <1026467388.3d2ea63c0ac65@webmail.tiscalinet.be> (raw)
In-Reply-To: <20020712073628.GB8838@tausq.org>
Hi Randolph,
I am on going to build mirroring on my test server.
But I will test it asap (as I already cvs update gcc-3.1.. ) and let you inform.
Thanks a lot for info,
Joel
PS: Can you do a telnet or an ssh connection when this kernel is running? IIRC
as well as gcc-3.1 as gcc-3.2, I always reach well to build and boot kernels
(without kdb) but the system crashes as soon as you try to connect it via the
network.
Quoting Randolph Chung <randolph@tausq.org>:
> I seem to recall some reports that you cannot build a working kernel
> with gcc-3.1....
>
> Well, maybe they've changed things upstream, but I just tried with
> gcc-3.1.1 (3.1.1 20020708 snapshot) and it seems to work well, at least
> with my limited testing... this is with the debian default 64-bit smp
> .config.
>
> I did have to hack up a bunch of code... it seems like gcc-3.1.1
> doesn't
> like this construct:
>
> typedef struct {
> volatile unsigned int __attribute__((aligned(16))) lock;
> } spinlock_t;
>
> typedef struct {
> spinlock_t lock;
> volatile unsigned int count;
> } rwlock_t;
>
> rwlock_t foo = (rwlock_t) { (spinlock_t) { 1 }, 0 };
>
> it complains that the initializer is not constant in this case.
> removing the (rwlock_t) cast fixed that....
>
> also it doesn't like it when you have a variable and you initialize it
> after declaration with the { (spinlock_t) { 1 }, 0 } stuff...
>
> (e.g.
> rwlock_t foo;
>
> foo = { (spinlock_t) { 1 }, 0 };
>
> gives a "parse error at {" message)
>
> after working through these problems i got a working kernel...
>
> randolph
> --
> Randolph Chung
> Debian GNU/Linux Developer, hppa/ia64 ports
> http://www.tausq.org/
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
>
-------------------------------------------------
This mail sent through Tiscali Webmail (http://webmail.tiscali.be)
next prev parent reply other threads:[~2002-07-12 9:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-12 7:36 [parisc-linux] compiling kernels with gcc-3.1 Randolph Chung
2002-07-12 9:49 ` joel.soete [this message]
2002-07-12 15:01 ` Randolph Chung
2002-07-12 16:23 ` joel.soete
2002-07-15 7:03 ` joel.soete
2002-07-15 7:24 ` joel.soete
2002-07-15 15:06 ` Randolph Chung
2002-07-15 15:56 ` joel.soete
2002-07-15 15:24 ` John David Anglin
2002-07-15 15:52 ` joel.soete
2002-07-15 16:22 ` Randolph Chung
2002-07-15 17:13 ` John David Anglin
2002-07-15 17:27 ` joel.soete
2002-07-13 5:20 ` [parisc-linux] compiling kernels with gcc-3.2 Randolph Chung
2002-07-13 10:24 ` Joel Soete
2002-07-13 18:54 ` Carlos O'Donell
2002-07-13 17:06 ` [parisc-linux] compiling kernels with gcc-3.1 Joel Soete
[not found] <no.id>
2002-07-15 17:21 ` John David Anglin
2002-07-15 17:32 ` Randolph Chung
2002-07-15 17:43 ` Matthew Wilcox
2002-07-15 18:18 ` John David Anglin
2002-07-16 9:02 ` joel.soete
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=1026467388.3d2ea63c0ac65@webmail.tiscalinet.be \
--to=joel.soete@freebel.net \
--cc=parisc-linux@parisc-linux.org \
--cc=randolph@tausq.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.