public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Gerhard Mack <gmack@innerfire.net>
Cc: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: linux 2.6.14.4 sparc compile problem
Date: Fri, 16 Dec 2005 23:21:54 +0100	[thread overview]
Message-ID: <20051216222154.GK23349@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0512160832350.995@innerfire.net>

On Fri, Dec 16, 2005 at 08:33:48AM -0500, Gerhard Mack wrote:
> Hello, 
> 
> I tried to compile kernel 2.6.14.4 on my sparc and I got this:
> 
> drivers/built-in.o(.init.text+0x1184): In function `rtc_init':
> : undefined reference to `ebus_chain'
> drivers/built-in.o(.init.text+0x1188): In function `rtc_init':
> : undefined reference to `ebus_chain'
> drivers/built-in.o(.init.text+0x1190): In function `rtc_init':
> : undefined reference to `isa_chain'
> drivers/built-in.o(.init.text+0x11d4): In function `rtc_init':
> : undefined reference to `isa_chain'
> drivers/built-in.o(.init.text+0x11d8): In function `rtc_init':
> : undefined reference to `isa_chain'
> make: *** [.tmp_vmlinux1] Error 1

Please send your .config .

> Gerhard Mack

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:[~2005-12-16 22:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-16 13:33 linux 2.6.14.4 sparc compile problem Gerhard Mack
2005-12-16 22:21 ` Adrian Bunk [this message]
2005-12-17  0:10   ` Gerhard Mack
2005-12-17 14:10     ` [2.6 patch] on sparc{,64}, RTC must depend on PCI Adrian Bunk
2005-12-19 22:52       ` David S. Miller
2005-12-23  2:15         ` [2.6 patch] introduce a SPARC Kconfig symbol Adrian Bunk
2005-12-23  5:04           ` David S. Miller

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=20051216222154.GK23349@stusta.de \
    --to=bunk@stusta.de \
    --cc=gmack@innerfire.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@vger.kernel.org \
    /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