From: Randy Dunlap <rdunlap@xenotime.net>
To: Miles Lane <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org
Subject: Re: 3.4.0+ - Linus GIT -- drivers/built-in.o: In function `nouveau_acpi_edid': (.text+0x112337): undefined reference to `acpi_video_get_edid'
Date: Mon, 30 Jul 2012 10:40:24 -0700 [thread overview]
Message-ID: <5016C708.3090509@xenotime.net> (raw)
In-Reply-To: <CAHFgRy_gc0sbgp2O6r4jHiDpMu0nX-ZefgEtkma1et3HAKG5+A@mail.gmail.com>
On 05/31/2012 12:10 AM, Miles Lane wrote:
> I suspect this is due to a dependency not enforced in the Kconfig logic?
>
> LD init/built-in.o
> drivers/built-in.o: In function `nouveau_acpi_edid':
> (.text+0x112337): undefined reference to `acpi_video_get_edid'
This build error still happens in Linux 3.5.
It is attempting to call a symbol in a loadable module from
a builtin driver.
CONFIG_ACPI_VIDEO=m
CONFIG_VIDEO_OUTPUT_CONTROL=m
If I use change CONFIG_VIDEO_OUTPUT_CONTROL to y,
CONFIG_ACPI_VIDEO also changes to y, so the relevant
functions are all builtin, and there is no build problem.
I guess that this line in drivers/gpu/drm/nouveau/Kconfig:
select ACPI_VIDEO if ACPI && X86 && BACKLIGHT_CLASS_DEVICE && VIDEO_OUTPUT_CONTROL && INPUT
sets ACPI_VIDEO=m since VIDEO_OUTPUT_CONTROL=m, even though all of the
other symbols are =y.
xconfig tells me:
Selects: FW_LOADER [=y] && DRM_KMS_HELPER [=y] && DRM_TTM [=y] && FB_CFB_FILLRECT [=y] && FB_CFB_COPYAREA [=y] && FB_CFB_IMAGEBLIT [=y] && FB [=y] && FRAMEBUFFER_CONSOLE [=y] && FB_BACKLIGHT [=y] && ACPI_VIDEO [=m] && ACPI_WMI [=y] && MXM_WMI [=y] && POWER_SUPPLY [=y]
--
~Randy
prev parent reply other threads:[~2012-07-30 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 7:10 3.4.0+ - Linus GIT -- drivers/built-in.o: In function `nouveau_acpi_edid': (.text+0x112337): undefined reference to `acpi_video_get_edid' Miles Lane
2012-07-30 17:40 ` Randy Dunlap [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=5016C708.3090509@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.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