From: "Ramit Bhalla" <ramit.bhalla@wipro.com>
To: <linux-kernel@vger.kernel.org>
Subject: Compiling bug - broken compile
Date: Mon, 22 Jul 2002 16:30:28 +0530 [thread overview]
Message-ID: <KMELKICNHILNIJDACGAIIECCCKAA.ramit.bhalla@wipro.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
Hi,
I'm using the 2.4.7 Kernel.
I'm trying to make this work without any BIOS support so I configure the
kernel to use "Direct" PCI calls through the menuconfig scripts. I also turn
off PCI Hot Pluggable support.
The build will break during "make zImage" at the end during the link phase.
It says it cannot find the symbol pcibios_set_irq_routing and
pcibios_get_irq_routing_table.
If I configure PCI to use BIOS calls, it work fine.
I noticed the problem lies in the file arch/i386/kernel/i386_ksyms.c
In that file EXPORT_SYMBOL(pcibios_set_irq_routing) is placed under #ifdef
CONFIG_PCI. If I add another clause #ifdef CONFIG_PCI_BIOS (which I presume
from the Config.in file is the definition for PCI Bios calls instead of
Direct calls), then it works fine.
Regards,
Ramit Bhalla.
Wipro Technologies,
No. 8
7th Main, 1st Block,
Koramangala,
Bangalore.
India - 560034.
E-mail - ramit.bhalla@wipro.com
Ph. - 91-80-5530035 ext 1082
Fax - 91-80-5530086
www.wipro.com
[-- Attachment #2: Wipro_Disclaimer.txt --]
[-- Type: text/plain, Size: 522 bytes --]
**************************Disclaimer**************************************************
Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged'
and 'confidential' and intended for use only by the individual or entity to which it is
addressed. You are notified that any use, copying or dissemination of the information
contained in the E-MAIL in any manner whatsoever is strictly prohibited.
****************************************************************************************
next reply other threads:[~2002-07-22 10:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 11:00 Ramit Bhalla [this message]
2002-07-22 13:53 ` Adrian Bunk
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=KMELKICNHILNIJDACGAIIECCCKAA.ramit.bhalla@wipro.com \
--to=ramit.bhalla@wipro.com \
--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®