From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: alan@lxorguk.ukuu.org.uk
Cc: 5740@mail.ru, acme@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: 2.4.3 compile error No 3
Date: Wed, 11 Apr 2001 18:02:35 +0200 [thread overview]
Message-ID: <20010411180235.A29195@vana.vc.cvut.cz> (raw)
In-Reply-To: <4AB83BD5FB4@vcnet.vc.cvut.cz>
In-Reply-To: <4AB83BD5FB4@vcnet.vc.cvut.cz>; from VANDROVE@vc.cvut.cz on Wed, Apr 11, 2001 at 05:40:35PM +0000
> # CONFIG_IPX_INTERN is not set
> # CONFIG_SYSCTL is not set
> net/network.o: In function `ipx_init':
> net/network.o(.text.init+0x1008): undefined reference to `ipx_register_sysctl'
Do not do it! You cannot control some very important features of IPX without
sysctl! Anyway below is patch, Alan please apply (although I must say that
this Makefile changed a bit my opinion on how obj-y and obj-m works...).
As for your other reports - No1 is fixed in Alan tree and patch is flying somewhere
around, and No2 looks like that your semaphore.h is corrupted. For parport
problems in No4, you have broken compiler or you changed some options in the
middle of compilation.
Petr Vandrovec
vandrove@vc.cvut.cz
diff -urdN linux/net/ipx/Makefile linux/net/ipx/Makefile
--- linux/net/ipx/Makefile Fri Dec 29 22:07:24 2000
+++ linux/net/ipx/Makefile Wed Apr 11 15:52:59 2001
@@ -13,13 +13,12 @@
export-objs = af_ipx.o af_spx.o
-obj-y := af_ipx.o
+obj-y := af_ipx.o sysctl_net_ipx.o
ifeq ($(CONFIG_IPX),m)
obj-m += $(O_TARGET)
endif
-obj-$(CONFIG_SYSCTL) += sysctl_net_ipx.o
obj-$(CONFIG_SPX) += af_spx.o
include $(TOPDIR)/Rules.make
next parent reply other threads:[~2001-04-11 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AB83BD5FB4@vcnet.vc.cvut.cz>
2001-04-11 16:02 ` Petr Vandrovec [this message]
2001-04-11 13:29 ` Arnaldo Carvalho de Melo
2001-04-11 16:15 ` info
2001-04-12 8:49 ` Repeating 2.4.3 compile error with ipx makefile patch info
2001-04-11 18:23 2.4.3 compile error No 3 Petr Vandrovec
2001-04-11 16:34 ` info
2001-04-11 18:59 Petr Vandrovec
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=20010411180235.A29195@vana.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=5740@mail.ru \
--cc=acme@conectiva.com.br \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®