public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rasmus Andersen <rasmus@jaquet.dk>
To: Keith Owens <kaos@ocs.com.au>
Cc: Tom Rini <trini@kernel.crashing.org>,
	kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 1.1 is available.
Date: Sun, 12 Aug 2001 09:31:40 +0200	[thread overview]
Message-ID: <20010812093140.A820@jaquet.dk> (raw)
In-Reply-To: <20010811212051.A819@jaquet.dk> <6820.997582287@ocs3.ocs-net>
In-Reply-To: <6820.997582287@ocs3.ocs-net>; from kaos@ocs.com.au on Sun, Aug 12, 2001 at 12:11:27PM +1000

On Sun, Aug 12, 2001 at 12:11:27PM +1000, Keith Owens wrote:
[...] 
> >pp_makefile2: Cannot find source for target drivers/sound/emu10k1/efxmgr.o
> >pp_makefile2: Cannot find source for target drivers/sound/emu10k1/joystick.o
> >pp_makefile2: Cannot find source for target drivers/sound/emu10k1/passthrough.o
> 
> You put kbuild-2.5-2.4.8-1 on an 2.4.8-pre kernel.  Linus moved emu10k1
> to its own directory in 2.4.8.  You have match kbuild with the correct
> kernel.

Yes, I have to and no, I did not. It was kbuild-2.5-2.4.8-1 on a
freshly untarred 248.tar.gz from a mirror. But kbuild-...-2 fixes
it for me fine.

-- 
        Rasmus(rasmus@jaquet.dk)

"Give a man a fish, and he eats for a day. Teach a man to fish, and a
US Navy submarine will make sure he's never hungry again." -- Chris
Neufeld

  parent reply	other threads:[~2001-08-12  7:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010811212051.A819@jaquet.dk>
2001-08-12  2:11 ` Announce: Kernel Build for 2.5, Release 1.1 is available Keith Owens
2001-08-12  2:27   ` Tom Rini
2001-08-12  7:31   ` Rasmus Andersen [this message]
2001-08-12  7:44     ` Keith Owens
2001-08-12  7:57       ` Daniel T. Chen

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=20010812093140.A820@jaquet.dk \
    --to=rasmus@jaquet.dk \
    --cc=kaos@ocs.com.au \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trini@kernel.crashing.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