From: Martin Costabel <costabel@wanadoo.fr>
To: nsheeley@austin.rr.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: semaphore-helper.h
Date: Thu, 25 Feb 1999 08:18:26 +0100 [thread overview]
Message-ID: <36D4F941.AF069CBD@wanadoo.fr> (raw)
In-Reply-To: 013092421221829FE5@mail5.austin.rr.com
nsheeley@austin.rr.com wrote:
>
> I just checked out the current CVS from
>
> :pserver:cvs@cvs.samba.org:/cvsroot
>
> All seems well until I try to do a make:
>
> make[2]: Entering directory `/local/src/CVS_kernel/linux/kernel'
> gcc -D__KERNEL__ -I/local/src/CVS_kernel/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -D__powerpc__ -fsigned-char -msoft-float -pipe -fno-builtin -ffixed-r2 -Wno-uninitialized -mmultiple -mstring -fno-omit-frame-pointer -c -o sched.o sched.c
> sched.c:39: asm/semaphore-helper.h: No such file or directory
You don't get the __down_trylock error in ksyms.c? Did they already
start repairing the 2.2.2 bug?
>
> Hmm.. only three arch's asm-includes have semaphore-helper.h
> (i386, sparc, sparc64), but its not ifdef'ed in any way in
> sched.c
>
> So my question are:
>
> a. Should I expect to be able to CVS checkout and
> make a working kernel? I am wondering about the stability
> of the tree -- what's my percent chance that I won't have
> to debug anything?
In principle, it should work. But there are always bugs possible. And
then there are guys with a weird sense of humour, in this case Linus
Himself. Read
http://lists.linuxppc.org/listarcs/linuxppc-user/199902/msg01298.html
> b. If yes to a., does anyone have a patch for the above problem.
Check out ("cvs update") kernel/ksyms.c -r1.107 and kernel/sched.c
-r1.124.
--
Martin
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-02-25 7:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-24 22:34 semaphore-helper.h nsheeley
1999-02-25 7:18 ` Martin Costabel [this message]
1999-02-25 8:15 ` semaphore-helper.h Martin Costabel
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=36D4F941.AF069CBD@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=nsheeley@austin.rr.com \
/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;
as well as URLs for NNTP newsgroup(s).