mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: bjorn.helgaas@hp.com, linux-next@vger.kernel.org,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: linux-next build error (PNP/IXJ)
Date: Tue, 22 Jul 2008 23:19:30 +0300	[thread overview]
Message-ID: <20080722201930.GB14846@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <20080722124152.facaa724.rdunlap@xenotime.net>

On Tue, Jul 22, 2008 at 12:41:52PM -0700, Randy Dunlap wrote:
> On Tue, 22 Jul 2008 20:39:57 +0300 Adrian Bunk wrote:
> 
> > On Tue, Jul 22, 2008 at 10:27:39AM -0700, Randy Dunlap wrote:
> > > Hi,
> > > 
> > > I'm seeing several build errors in linux-next-20080722 that I haven't
> > > seen previously, although I don't know what changed to cause this.
> > > 
> > > They are all basically the same, in ixj (drivers/telephony/ixj*), when
> > > CONFIG_PNP=n, and CONFIG_PHONE_IXJ=y or =m (so the actual error message
> > > varies depending on IXJ=y or =m):
> > > 
> > > IXJ=y:
> > > ixj.c:(.text+0x329d98): undefined reference to `pnp_get_resource'
> > > or IXJ=m:
> > > ERROR: "pnp_get_resource" [drivers/telephony/ixj.ko] undefined!
> > > 
> > > 
> > > Suggestions?
> > 
> > Please send a .config
> 
> attached.  (IXJ=m)

Works for me with gcc 4.3.1.
Which gcc version are you using?

Does disabling CONFIG_OPTIMIZE_INLINING fix it for you?

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


  reply	other threads:[~2008-07-22 20:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22 17:27 Randy Dunlap
2008-07-22 17:39 ` Adrian Bunk
2008-07-22 19:41   ` Randy Dunlap
2008-07-22 20:19     ` Adrian Bunk [this message]
2008-07-22 20:32       ` Randy Dunlap
2008-07-22 17:57 ` Bjorn Helgaas
2008-07-22 19:52   ` 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=20080722201930.GB14846@cs181140183.pp.htv.fi \
    --to=bunk@kernel.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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®