From: Keith Owens <kaos@ocs.com.au>
To: Willy Tarreau <willy@w.ods.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19 make allmodconfig - undefined symbols
Date: Sun, 04 Aug 2002 23:22:24 +1000 [thread overview]
Message-ID: <1876.1028467344@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sun, 04 Aug 2002 14:35:13 +0200." <20020804123513.GC13316@alpha.home.local>
On Sun, 4 Aug 2002 14:35:13 +0200,
Willy Tarreau <willy@w.ods.org> wrote:
>On Sun, Aug 04, 2002 at 08:13:20PM +1000, Keith Owens wrote:
>> 2.4.19 make allmodconfig. Besides the perennial drivers/net/wan/comx.o
>> wanting proc_get_inode, there was only one undefined symbol. In the
>> extremely unlikely event that binfmt_elf is a module (how do you load
>> modules when binfmt_elf is a module?), smp_num_siblings is unresolved.
>
>I also get an unresolved reference to __io_virt_debug in misc.o:puts()
>when building bzImage. If you don't get it, it means that my tree is
>corrupted.
Neither. It is a problem with CONFIG_DEBUG_IOVIRT which allmod and
allyesconfig turn on. My builds stop at vmlinux and do not build
bzImage so I did not detect this problem. The outb_p calls in misc.c
need fixing for CONFIG_DEBUG_IOVIRT=y, or force CONFIG_DEBUG_IOVIRT=n.
Interesting that the comment for CONFIG_DEBUG_IOVIRT says "Temporary
debugging check to catch old code using unmapped ISA addresses. Will be
removed in 2.4".
next prev parent reply other threads:[~2002-08-04 13:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 10:13 Keith Owens
2002-08-04 12:35 ` Willy Tarreau
2002-08-04 13:22 ` Keith Owens [this message]
2002-08-04 15:02 ` Adrian Bunk
2002-08-04 12:52 ` Paul P Komkoff Jr
2002-08-04 16:10 ` Adrian Bunk
2002-08-04 18:18 ` Alan Cox
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=1876.1028467344@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@w.ods.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®