Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Joel Soete <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: Sat, 13 Jul 2002 17:06:54 +0000	[thread overview]
Message-ID: <3D305E2E.7020800@freebel.net> (raw)
In-Reply-To: 20020712073628.GB8838@tausq.org

[-- Attachment #1: Type: text/plain, Size: 2146 bytes --]

Hi Randolph,

Well I reach to compile gcc-3.1.1 without error (xc toolchain hppa -> 
hppa as gcc bootstrap).

Now I compile kernel 2.4.18-pa54 (last cvs I got Friday morning) for 
32-bits config first (not 64-bits yet) and may be that is why I do not 
met the problem mentioned below

> 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...
> 

OTC I met a strange problem with modules:

find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
if [ -r System.map ]; then /sbin/depmod -ae -F System.map  2.4.18-pa54; fi
depmod: *** Unresolved symbols in 
/lib/modules/2.4.18-pa54/kernel/drivers/input/input.o
depmod:         mod_timer_R1f13d309
depmod:         unregister_chrdev_Rc192d491
depmod:         printk_Rdd132261
depmod:         jiffies_R0da02d67
depmod:         del_timer_Rfc62f16d
depmod:         register_chrdev_Rddc3984b
depmod:         sprintf_R1d26aa98
depmod:         try_inc_mod_count_R133c9d8f
depmod: *** Unresolved symbols in 
/lib/modules/2.4.18-pa54/kernel/drivers/input/keybdev.o
depmod:         kmalloc_R93d4cfe6
...

Any idea?

Thanks again for help and advises,
	Joel

PS: I join my compile log just in case you notice other details

[-- Attachment #2: k-2.4.18-pa54-gcc311.gz --]
[-- Type: application/gzip, Size: 55379 bytes --]

  parent reply	other threads:[~2002-07-13 17:08 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
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 ` Joel Soete [this message]
     [not found] <no.id>
2002-07-15 17:21 ` [parisc-linux] compiling kernels with gcc-3.1 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=3D305E2E.7020800@freebel.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox