From: "Wil Reichert" <wil.reichert@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Can't build kernel
Date: Sat, 19 May 2007 12:46:26 -0700 [thread overview]
Message-ID: <7a329d910705191246y7cde7d79mfcba4afad0a929a0@mail.gmail.com> (raw)
In-Reply-To: <175872.89004.qm@web83303.mail.sp1.yahoo.com>
> By genkernel do you mean the gentoo kernel? I do. How do I switch to
> vanilla? If I'm going to do that I like to make it permanent.
genkernel is a program which automatically configures and builds a
kernel for you. Its handy if you know nothing about the hardware you
are building a kernel for. You'll do far better taking the 10 minutes
to look at lspci, lsusb, etc & manually configure via menuconfig.
Judging from the current gentoo-sources patch list there not really
much of a difference from the stock kernel. To use the untouched
kernel.org sources just emerge vanilla-sources, then use 'eselect
kernel' to modify the /usr/src/linux symlink (or do it manually).
Wil
> I usually remove all the acpi stuff anyway, which is why this message has
> been particularly puzzling.
>
>
> ----- Original Message ----
> From: "Hemmann, Volker Armin"
> <volker.armin.hemmann@tu-clausthal.de>
> To: gentoo-amd64@lists.gentoo.org
> Sent: Saturday, May 19, 2007 11:45:12 AM
> Subject: Re: [gentoo-amd64] Can't build kernel
>
> On Samstag, 19. Mai 2007, Peter Hoff wrote:
> > I haven't been able to build 2.6.21. I was hoping it was maybe just a "-0"
> > release problem, but I'm getting the same error with -r1. Here it is:
> >
> > drivers/built-in.o: In function `acpi_bus_generate_event':
> > (.text+0x4325d): undefined reference to `event_is_open'
> > drivers/built-in.o: In function `acpi_bus_get_power':
> > (.text+0x43515): undefined reference to `acpi_power_get_inferred_state'
> > drivers/built-in.o: In function `acpi_bus_set_power':
> > (.text+0x4362b): undefined reference to `acpi_power_transition'
> > drivers/built-in.o: In function `acpi_bus_set_power':
> > (.text+0x4369d): undefined reference to `acpi_power_transition'
> > make: *** [.tmp_vmlinux1] Error 1
>
>
> did you use genkernel?
> If yes. Don't.
>
> And don't built acpi-stuff modular.
>
> If problem persists, use vanilla-sources. They do always work...
>
> --
> gentoo-amd64@gentoo.org mailing list
>
>
>
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2007-05-19 19:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 18:55 [gentoo-amd64] Can't build kernel Peter Hoff
2007-05-19 19:46 ` Wil Reichert [this message]
2007-05-20 1:40 ` Hemmann, Volker Armin
-- strict thread matches above, loose matches on Subject: below --
2007-05-21 13:24 Peter Hoff
2007-05-22 12:00 ` Alan Young
2007-05-21 13:19 Peter Hoff
2007-05-21 5:04 Peter Hoff
2007-05-21 5:11 ` Dustin J. Mitchell
2007-05-20 16:39 Peter Hoff
2007-05-20 19:49 ` Hemmann, Volker Armin
2007-05-20 22:21 ` david
2007-05-21 7:58 ` Peter Humphrey
2007-05-21 11:00 ` Hemmann, Volker Armin
2007-05-21 11:55 ` Naga
2007-05-20 16:24 Peter Hoff
2007-05-19 18:02 Peter Hoff
2007-05-19 18:45 ` Hemmann, Volker Armin
2007-05-19 18:52 ` Drake Donahue
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=7a329d910705191246y7cde7d79mfcba4afad0a929a0@mail.gmail.com \
--to=wil.reichert@gmail.com \
--cc=gentoo-amd64@lists.gentoo.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