From: Pavel Roskin <proski@gnu.org>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: mkdep patch in 2.4.21-pre4-ac7 breaks pci/drivers
Date: Mon, 03 Mar 2003 03:32:55 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.51.0303030313450.26129@localhost.localdomain> (raw)
In-Reply-To: <200303020213.h222DM7O003304@eeyore.valparaiso.cl>
Hello!
On Sat, 1 Mar 2003, Horst von Brand wrote:
> Pavel Roskin <proski@gnu.org> said:
> > If I compile linux 2.4.21-pre4-ac7, then run "make depend" and "make
> > clean", then "make bzImage" fails in pci/drivers:
>
> make drivers/pci/gen-devlist; pushd drivers/pci; ./gen-devlist < pci.ids; popd
>
> Needed for all 2.4.x I've seen (lately at least).
That shouldn't be needed unless you skip "make depend" completely or do
something else wrong, or your "make" is buggy. It shouldn't be necessary.
names.o depends on devlist.h explicitly in drivers/pci/Makefile.
As explained in the section "Multiple Rules for One Target" of GNU make
documentation, other rules (i.e. in .depend) don't cancel this dependency.
Further, devlist.h depends on gen-devlist, so whenever drivers/pci/names.o
is to be compiled, devlist.h will be created before that.
> > This is caused by the patch for scripts/mkdep.c (part of the
> > 2.4.21-pre4-ac7 patch)
>
> Nope. It's the same with 2.4 from Marcelo.
Not true. 2.4.20 is fine:
make distclean
cp ~/local/linux/.config .
make oldconfig
make dep
make bzImage
No problems whatsoever.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2003-03-03 8:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 22:00 Pavel Roskin
2003-03-02 2:13 ` Horst von Brand
2003-03-03 8:32 ` Pavel Roskin [this message]
2003-03-04 1:27 ` Horst von Brand
2003-03-03 9:00 ` [PATCH] " Pavel Roskin
2003-03-03 9:58 ` Pavel Roskin
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=Pine.LNX.4.51.0303030313450.26129@localhost.localdomain \
--to=proski@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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
all inboxes | Powered by JetHome®