mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Grozdan <neutrino8@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: Can't compile 2.6.32
Date: Sat, 5 Dec 2009 03:12:54 +0100	[thread overview]
Message-ID: <c5bd819b0912041812g394aa26eia1b839e1f0c3c98d@mail.gmail.com> (raw)
In-Reply-To: <173abc14-0cbc-4340-b21f-3e8bc15f02dd@default>

On Sat, Dec 5, 2009 at 3:03 AM, Randy Dunlap <randy.dunlap@oracle.com> wrote:
>
> A bit more info on this. It seems there's a
> CONFIG_ACPI_CUSTOM_OVERRIDE_INITRAMFS in the "normal" SUSE source RPM
> package (which in my config is not enabled, but there is an option for
> that) and looking at the drivers/acpi/osl.c and the
> include/acpi/acpiosxf.h file, there's a define for this in the header
> which has acpi_load_override_tables(void); and also this is present in
> the osl.c file.... see both attachments. I could not find the same
> thing in the kernel-default-vanilla source RPM package also present in
> the repo.
>
> ~~~~~~~~~~~~~~~~~~  reply: ~~~~~~~~~~~~~~~~~~~~~~~~
>
> You should take this up with the OpenSUSE people, not lkml.

Yeah I know, and what I've been planning to. But, I enabled this
option some minutes ago and tried to compile again. It passed
compilation of osl.c so I think it's all good now. There have been
quite a lot of complains about how SUSE configures and splits its
kernel packages; for the new 11.2 release, I've read a lot of them on
the SUSE forum where people couldn't even boot if the kernel-desktop
was selected and installed but had no problems with the
kernel-default. I don't know who configures these kernels (I don't use
SUSE configured/compiled kernels, only grab them from the build
service & configure/compile them myself) but it seems it's getting
progressively worse, not to mention in how many different packages
they've split the kernel and people are getting confused about this :(

Anyways, thanks so far ;)

>
> Thanks,
> ~Randy
>

  reply	other threads:[~2009-12-05  2:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-05  2:03 Randy Dunlap
2009-12-05  2:12 ` Grozdan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-12-04 13:32 Grozdan
2009-12-04 22:25 ` Randy Dunlap
2009-12-04 22:30   ` Grozdan
2009-12-04 23:05     ` Randy Dunlap
2009-12-05  0:29       ` Justin P. Mattock
2009-12-05  0:43         ` Randy Dunlap

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=c5bd819b0912041812g394aa26eia1b839e1f0c3c98d@mail.gmail.com \
    --to=neutrino8@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    /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®