linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Andrew Morton <akpm@osdl.org>, toralf.foerster@gmx.de
Subject: Re: linux- 2.6.18-rc3 undefined reference to `fb_register_client'
Date: Mon, 31 Jul 2006 07:56:17 +0800	[thread overview]
Message-ID: <44CD4721.20909@gmail.com> (raw)
In-Reply-To: <200607301817.39411.toralf.foerster@gmx.de>

Toralf Förster wrote:
> During compile tests of different .configs I got :
> ...
> 
>   AR      arch/i386/lib/lib.a
>   GEN     .version
>   CHK     include/linux/compile.h
>   UPD     include/linux/compile.h
>   CC      init/version.o
>   LD      init/built-in.o
>   LD      .tmp_vmlinux1
> drivers/built-in.o: In function `backlight_device_register':
> : undefined reference to `fb_register_client'
> drivers/built-in.o: In function `backlight_device_unregister':
> : undefined reference to `fb_unregister_client'
> make: *** [.tmp_vmlinux1] Error 1
> 

Try this patch:
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc2/2.6.18-rc2-mm1/broken-out/fbdev-statically-link-the-framebuffer-notification-functions.patch

Andrew,

Maybe this patch should go to mainline?

Tony

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2006-07-30 23:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-30 16:17 linux- 2.6.18-rc3 undefined reference to `fb_register_client' Toralf Förster
2006-07-30 23:56 ` Antonino A. Daplas [this message]
2006-07-31  0:04   ` Antonino A. Daplas

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=44CD4721.20909@gmail.com \
    --to=adaplas@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=toralf.foerster@gmx.de \
    /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;
as well as URLs for NNTP newsgroup(s).