From: Grant Grundler <grundler@cup.hp.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] CONFIG_SYSCTL is not set
Date: Mon, 29 May 2000 19:01:07 -0700 (PDT) [thread overview]
Message-ID: <200005300201.TAA11206@milano.cup.hp.com> (raw)
Hi folks,
By default, CONFIG_SYSCTL is not set.
And I get the following errors when linking:
fs/fs.o: In function `nfs_put_inode':
fs/fs.o(.text+0x399dc): undefined reference to `nfs_debug'
fs/fs.o: In function `L1261':
fs/fs.o(.text.init+0x18fc): undefined reference to `nfs_debug'
net/network.a(sunrpc.o): In function `rpc_create_client':
sunrpc.o(.text+0x360): undefined reference to `rpc_debug'
All of these errors are a result of not having globals defined in
net/sunrpc/sysctl.c. sysctl.o only gets built when CONFIG_SYSCTL=y.
With CONFIG_SYSCTL=y, I get a different linker error
kernel/kernel.o(.data+0x3b4c): undefined reference to `sysrq_enabled'
(which willy already pointed out...See
http://puffin.external.hp.com/mailing-lists/parisc-linux/2000/05-May/0103.html)
This is very reproducible (going back and forth) in my build tree.
I don't see how willy got around it.
Do we want the build to work with or without CONFIG_SYSCTL?
>From the Documentation/Configure.help:
| As it is generally a good thing, you should say Y here unless
| building a kernel for install/rescue disks or your system is very
| limited in memory.
Philipp Rumpf wrote:
> I wouldn't really consider this a bug, but if anyone does he should
> probably report it to whoever is working on that code in 2.3.
If anyone wants to build x86 install/rescue disks, I think they can't now.
Either the Configure.help is wrong or the code is wrong.
I don't know how to submit a BUG.
Any pointers on where this bug should go?
thanks,
grant
next reply other threads:[~2000-05-30 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-30 2:01 Grant Grundler [this message]
2000-05-30 7:53 ` [parisc-linux] CONFIG_SYSCTL is not set Richard Hirst
2000-05-30 15:15 ` Paul Bame
2000-06-01 0:01 ` Philipp Rumpf
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=200005300201.TAA11206@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=parisc-linux@thepuffingroup.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.