From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] 2.4.3 ACPI build errors
Date: Fri, 06 Apr 2001 17:24:01 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005379@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005377@msgid-missing>
>>>>> On Fri, 6 Apr 2001 11:53:50 -0400 (EDT), "Michael F. Brown" <mbrown@emc.com> said:
Mike> Hello, I'm trying to build the 2.4.3 kernel after applying the
Mike> 2.4.3 ia64 patch. I see the following build errors:
Mike> gcc -D__KERNEL__ -I/usr/src/linux-2.4.3/include -Wall
Mike> -Wstrict-prototypes -g -O2 -fomit-frame-pointer
Mike> -fno-strict-aliasing -pipe -Wa,-x -ffixed-r13
Mike> -mfixed-rangeñ0-f15,f32-f127 -funwind-tables
Mike> -falign-functions2 -mb-step -mconstant-gp -c -o iosapic.o
Mike> iosapic.c iosapic.c: In function `iosapic_init':
Mike> iosapic.c:355: structure has no member named `pci_vectors'
Mike> iosapic.c:356: structure has no member named `num_pci_vectors'
Mike> make[1]: *** [iosapic.o] Error 1 make[1]: Leaving directory
Mike> `/usr/src/linux-2.4.3/arch/ia64/kernel' make: ***
Mike> [_dir_arch/ia64/kernel] Error 2
Ah, yes, you *must* turn on CONFIG_ACPI_KERNEL_CONFIG as the new
bootloader no longer has ACPI built in (actually, I thought that had
been removed a while ago).
Thanks for pointing this out. I will clean away this configuration
option in the patch.
Mike> So to work around this, I've tried setting
Mike> CONFIG_ACPI_KERNEL_CONFIG. Using make xconfig, this option is
Mike> greyed out or disabled.
If you selected the "DIG" platform, the option should be active. You
could try "make menuconfig" as well.
Mike> So I tried manually adding:
Mike> CONFIG_ACPI20=y CONFIG_ACPI_KERNEL_CONFIG=y
That doesn't work.
--david
prev parent reply other threads:[~2001-04-06 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-06 15:53 [Linux-ia64] 2.4.3 ACPI build errors Michael F. Brown
2001-04-06 17:24 ` David Mosberger [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=marc-linux-ia64-105590693005379@msgid-missing \
--to=davidm@hpl.hp.com \
--cc=linux-ia64@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