linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: nsheeley@austin.rr.com
To: linuxppc-dev@lists.linuxppc.org
Subject: semaphore-helper.h
Date: Wed, 24 Feb 1999 16:34:23 -0600 (CST)	[thread overview]
Message-ID: <013092421221829FE5@mail5.austin.rr.com> (raw)



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

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? 

	b.  If yes to a., does anyone have a patch for the above problem.

Thanks.

Nate








[[ 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 ]]

             reply	other threads:[~1999-02-24 22:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-24 22:34 nsheeley [this message]
1999-02-25  7:18 ` semaphore-helper.h Martin Costabel
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=013092421221829FE5@mail5.austin.rr.com \
    --to=nsheeley@austin.rr.com \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).