public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>,
	kai@germaschewski.name, sam@ravnborg.org, rusty@rustcorp.com.au
Cc: Vincent Vanackere <vincent.vanackere@gmail.com>,
	keenanpepper@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: Undefined symbols in 2.6.11-rc5-mm1
Date: Wed, 2 Mar 2005 15:00:19 +0100	[thread overview]
Message-ID: <20050302140019.GC4608@stusta.de> (raw)
In-Reply-To: <20050302032414.13604e41.akpm@osdl.org>

On Wed, Mar 02, 2005 at 03:24:14AM -0800, Andrew Morton wrote:
> Vincent Vanackere <vincent.vanackere@gmail.com> wrote:
> >
> > I have the exact same problem. 
> >  .config is attached
> >  (this may be a debian specific problem as I'm running debian too)
> 
> OK, there are no vmlinux references to lib/parser.o's symbols.  So it isn't
> getting linked in.

That much I figured out after Vincent sent his bug report two weeks ago.

> In lib/Makefile, remove parser.o from the lib-y: rule and add
> 
> obj-y	+= parser.o

This I didn't find.

Is it really the intention to silently omit objects that are not 
referenced or could this be changed?

Why doesn't an EXPORT_SYMBOL create a reference?

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2005-03-02 14:00 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02  5:37 Undefined symbols in 2.6.11-rc5-mm1 Keenan Pepper
2005-03-02  9:23 ` Andrew Morton
2005-03-02  9:45   ` Vincent Vanackere
2005-03-02 11:24     ` Andrew Morton
2005-03-02 13:26       ` Vincent Vanackere
2005-03-02 14:00       ` Adrian Bunk [this message]
2005-03-02 16:28         ` Andrew Morton
2005-03-02 17:23           ` Valdis.Kletnieks
2005-03-02 17:34             ` Andrew Morton
2005-03-04 10:26             ` Rusty Russell
2005-03-03 13:41           ` Adrian Bunk
2005-03-04 10:23         ` Rusty Russell
2005-03-04 18:56           ` Adrian Bunk
2005-03-04 19:13             ` Adrian Bunk
2005-03-04 19:11           ` Kai Germaschewski
2005-03-04 20:28             ` Adrian Bunk
2005-03-05  5:09               ` Kai Germaschewski
2005-03-05 13:04                 ` Adrian Bunk
2005-03-05 15:19                   ` Kai Germaschewski
2005-03-05 15:36                     ` Adrian Bunk
2005-03-05 16:36                       ` Kai Germaschewski
2005-03-05 17:15                         ` Adrian Bunk
2005-03-05 18:48                           ` Kai Germaschewski
2005-03-05 23:58                         ` Christoph Hellwig
2005-03-05 23:57                     ` Christoph Hellwig
     [not found]   ` <4225C613.7010701@gmail.com>
2005-03-02 14:03     ` Keenan Pepper

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=20050302140019.GC4608@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=kai@germaschewski.name \
    --cc=keenanpepper@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=sam@ravnborg.org \
    --cc=vincent.vanackere@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