From: Andrey Panin <pazke@donpac.ru>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Don Guy <mostly_harmless@sympatico.ca>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: v2.4.29 won't compile with PCI support disabled
Date: Mon, 4 Apr 2005 16:28:51 +0400 [thread overview]
Message-ID: <20050404122851.GD16003@pazke> (raw)
In-Reply-To: <16977.12215.621136.359066@alkaid.it.uu.se>
On 094, 04 04, 2005 at 02:14:47 +0200, Mikael Pettersson wrote:
> Don Guy writes:
> > PROBLEM:
> >
> > Attempts to compile v2.4.29 with PCI support disabled result in the
> > following errors:
> >
> > drivers/char/char.o: In function `siig10x_init_fn':
> > drivers/char/char.o(.text.init+0x12cd): undefined reference to
> > `pci_siig10x_fn'
> > drivers/char/char.o: In function `siig20x_init_fn':
> > drivers/char/char.o(.text.init+0x12ed): undefined reference to
> > `pci_siig20x_fn'
> >
> > It has been suggested that enabling PCI support in the kernel will make this
> > go away however a) enabling PCI support on a 486 which only has ISA & VLB is
> > downright silly, and b) a test run with CONFIG_PCI=y resulted in a plethora
> > of other errors.
>
> Presumably this is because of other CONFIG options which are still
> enabled but don't work w/o CONFIG_PCI. So please post your .config.
>
d> Both 2.4 and 2.6 kernels with CONFIG_PCI=n work Ok(*) on my 486.
Disable CONFIG_PARPORT_SERIAL in your config.
--
Andrey Panin | Linux and UNIX system administrator
pazke@donpac.ru | PGP key: wwwkeys.pgp.net
prev parent reply other threads:[~2005-04-04 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <002401c53900$9a47b0e0$1d2aa8c0@stormie>
2005-04-04 10:25 ` PROBLEM: v2.4.29 won't compile with PCI support disabled Don Guy
2005-04-04 12:14 ` Mikael Pettersson
2005-04-04 12:28 ` Andrey Panin [this message]
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=20050404122851.GD16003@pazke \
--to=pazke@donpac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=mostly_harmless@sympatico.ca \
/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