From: Steven Cole <elenstev@mesatop.com>
To: linux-kernel@vger.kernel.org
Cc: alan@lxorguk.ukuu.org.uk
Subject: Re: Linux 2.4.0test11-ac1
Date: Tue, 21 Nov 2000 18:20:29 -0700 [thread overview]
Message-ID: <00112118202900.25333@localhost.localdomain> (raw)
Alan Cox wrote:
>
>> I tried to compile 2.4.0-test11-ac1, and here is where the compile bombed
out:
>>
>> /usr/bin/kgcc -D__KERNEL__ -I/usr/src/linux/include -Wall
-Wstrict-prototypes
>> -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -march=i686 -c -o
>> sched.o sched.c
>> irq.c:182: conflicting types for `global_irq_lock'
>> /usr/src/linux/include/asm/hardirq.h:45: previous declaration of
>> `global_irq_lock'
>
>I'll check this. I take it you tried an SMP build ?
Yes, this above build attempt was for an SMP kernel. When I got home,
I tried to build an UP kernel with test11-ac1, and as I'm sure you know
already, it worked perfectly. I then tried to build another SMP kernel, with
the same results as above.
I submitted a tiny patchlet earlier for this. It seems to fix the symptoms.
I compiled and ran a kernel with this patch on the SMP box at work.
I replicated the associated comment for people searching on this pattern.
I'm at home now, please cc any questions or comments to elenstev@mesatop.com.
Steven
Here is the patchlet again:
diff -u linux/include/asm/hardirq.h.orig linux/include/asm/hardirq.h
--- linux/include/asm/hardirq.h.orig Tue Nov 21 13:38:07 2000
+++ linux/include/asm/hardirq.h Tue Nov 21 13:40:13 2000
@@ -42,7 +42,7 @@
#include <asm/smp.h>
extern unsigned char global_irq_holder;
-extern unsigned volatile int global_irq_lock;
+extern unsigned volatile long global_irq_lock; /* long for set_bit --RR */
static inline int irqs_running (void)
{
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-22 1:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-22 1:20 Steven Cole [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-22 18:18 Linux 2.4.0test11-ac1 Bruce_Holzrichter
2000-11-21 19:07 Steven Cole
2000-11-21 23:27 ` Alan Cox
2000-11-21 13:51 Alan Cox
2000-11-21 18:14 ` Johannes Erdfelt
2000-11-21 18:18 ` Alan Cox
2000-11-21 18:25 ` Maciej W. Rozycki
2000-11-21 18:31 ` Alan Cox
2000-11-21 18:40 ` Maciej W. Rozycki
2000-11-21 18:49 ` Alan Cox
2000-11-21 19:08 ` Maciej W. Rozycki
2000-11-21 19:34 ` Brian Gerst
2000-11-21 23:31 ` Alan Cox
2000-11-22 0:07 ` H. Peter Anvin
2000-11-22 0:29 ` Alan Cox
2000-11-22 0:19 ` H. Peter Anvin
2000-11-22 15:48 ` Maciej W. Rozycki
2000-11-22 16:47 ` Alan Cox
2000-11-22 17:49 ` Maciej W. Rozycki
2000-11-22 17:58 ` Alan Cox
2000-11-22 18:02 ` H. Peter Anvin
2000-11-22 18:06 ` Alan Cox
2000-11-23 8:23 ` Maciej W. Rozycki
2000-11-23 8:52 ` Vojtech Pavlik
2000-11-22 16:02 ` Maciej W. Rozycki
2000-11-21 18:54 ` Jeff Garzik
2000-11-21 23:25 ` Alan Cox
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=00112118202900.25333@localhost.localdomain \
--to=elenstev@mesatop.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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