From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
Russell King <rmk@arm.linux.org.uk>
Subject: Re: 2.4.6 PCMCIA NET modular build breakage
Date: Sat, 07 Jul 2001 10:41:28 -0400 [thread overview]
Message-ID: <3B471F98.42875269@mandrakesoft.com> (raw)
In-Reply-To: <200107071423.f67ENv707049@linuxhacker.ru>
Oleg Drokin wrote:
> arm-linux-ld -p -X -T arch/arm/vmlinux.lds arch/arm/kernel/head-armv.o arch/arm/kernel/init_task.o init/main.o init/version.o \
> --start-group \
> arch/arm/kernel/kernel.o arch/arm/mm/mm.o arch/arm/mach-sa1100/sa1100.o
> kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \
> drivers/char/char.o drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/cdrom/driver.o drivers/mtd/mtdlink.o drivers/net/pcmcia/pcmcia_net.o drivers/net/wireless/wireless_net.o drivers/video/video.o \
> net/network.o \
> arch/arm/fastfpe/fast-math-emu.o arch/arm/nwfpe/math-emu.o arch/arm/lib/lib.a /home/green/arm/cvs/linux/kernel/lib/lib.a /skiff/local/lib/gcc-lib/arm-linux/2.95.2/soft-float/libgcc.a \
> --end-group \
> -o vmlinux
> arm-linux-ld: cannot open drivers/net/pcmcia/pcmcia_net.o: No such file or directory
> make: *** [vmlinux] Error 1
>
> And Rules.make is almost identical to that in vanilla kernel (if someone is
> interested). (almost means that it have rule on how to make .o files from .S)
It is clear that,
(1) your config has CONFIG_NET_PCMCIA, and appears to be ok
(2) your linux/Makefile is correct, as the link statement includes
pcmcia_net.o
So that leaves us with drivers/net/Makefile and
drivers/net/pcmcia/Makefile.
drivers/net/Makefile is a potential problem source, perhaps the
following change is not in your arch tree:
subdir-$(CONFIG_NET_PCMCIA) += pcmcia
If that statement exists in drivers/net/Makefile, you need to run a
kernel build, and start staring at make output to see exactly why it is
not building.
--
Jeff Garzik | A recent study has shown that too much soup
Building 1024 | can cause malaise in laboratory mice.
MandrakeSoft |
next prev parent reply other threads:[~2001-07-07 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-07 9:16 2.4.6 PCMCIA NET modular build breakage Russell King
2001-07-07 12:12 ` Alan Cox
2001-07-07 14:23 ` Oleg Drokin
2001-07-07 14:41 ` Jeff Garzik [this message]
2001-07-07 13:23 ` Kai Germaschewski
2001-07-07 14:30 ` Oleg Drokin
2001-07-07 16:43 ` Russell King
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=3B471F98.42875269@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=green@linuxhacker.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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