From: "Krzysztof Helt" <krzysztof.h1@wp.pl>
To: sparclinux@vger.kernel.org
Subject: 2.6.17-rc5 does not build for sparc
Date: Sat, 27 May 2006 21:09:17 +0000 [thread overview]
Message-ID: <4478bffd45960@wp.pl> (raw)
[-- Attachment #1: Type: text/plain, Size: 454 bytes --]
Hello,
I tried to build the 2.6.17-rc5 for sparc with SMP enabled. The
kernel was not build due to a missing macro. Here is a patch
which fixes this (I copied the macro from a sparc64 header).
Best wishes,
Krzysztof
----------------------------------------------------
John Malkovich w filmie KLIMT.
Kontrowersyjny. Dekadencki. Rozpasany. Genialny.
W kinach od 26 maja.
http://klik.wp.pl/?adr=http%3A%2F%2Fadv.reklama.wp.pl%2Fas%2Fklimt.html&sid=771
[-- Attachment #2: missing_raw_lock.patch --]
[-- Type: application/octet-stream, Size: 589 bytes --]
Only in linux-2.6.17smp/include/asm-sparc: asm-offsets.h
diff -ur linux-2.6.16/include/asm-sparc/spinlock.h linux-2.6.17smp/include/asm-sparc/spinlock.h
--- linux-2.6.16/include/asm-sparc/spinlock.h 2006-05-27 19:35:16.000000000 +0200
+++ linux-2.6.17smp/include/asm-sparc/spinlock.h 2006-05-27 21:33:28.000000000 +0200
@@ -154,6 +154,8 @@
#define __raw_spin_lock_flags(lock, flags) __raw_spin_lock(lock)
#define __raw_read_trylock(lock) generic__raw_read_trylock(lock)
+#define __raw_write_can_lock(rw) (!(rw)->lock)
+
#endif /* !(__ASSEMBLY__) */
#endif /* __SPARC_SPINLOCK_H */
next reply other threads:[~2006-05-27 21:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 21:09 Krzysztof Helt [this message]
2006-05-27 22:43 ` 2.6.17-rc5 does not build for sparc Bob Breuer
2006-05-28 9:30 ` BERTRAND Joël
2006-05-28 10:27 ` Christian Joensson
2006-05-29 6:03 ` Krzysztof Helt
2006-06-06 4:15 ` David Miller
2006-06-06 4:59 ` Bob Breuer
2006-06-06 5:08 ` David Miller
2006-06-06 7:09 ` Bob Breuer
2006-06-08 11:33 ` Krzysztof Helt
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=4478bffd45960@wp.pl \
--to=krzysztof.h1@wp.pl \
--cc=sparclinux@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 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.