All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niels Kristian Bech Jensen <nkbj@mail.tele.dk>
To: linuxppc-dev@ozlabs.org
Subject: latest git: compile error: arch/powerpc/kernel/built-in.o
Date: Fri, 11 Aug 2006 08:13:55 +0200	[thread overview]
Message-ID: <1155276835.4844.2.camel@localhost> (raw)

>   LD      .tmp_vmlinux1
> arch/powerpc/kernel/built-in.o: In function `__restore_cpu_setup':
> (.text+0xcd34): undefined reference to `kexec_sr_activated'
> arch/powerpc/kernel/built-in.o: In function `__restore_cpu_setup':
> (.text+0xcd44): undefined reference to `crash_kexec_secondary'
> arch/powerpc/kernel/built-in.o: In function `early_init_devtree':
> (.init.text+0x1cdc): undefined reference to `reserve_crashkernel'
> arch/powerpc/kernel/built-in.o: In function `early_init_devtree':
> (.init.text+0x1e1c): undefined reference to `overlaps_crashkernel'
> make[1]: *** [.tmp_vmlinux1] Error 1
> make[1]: Leaving directory `/home/shorty/kernel-factory/git.08102006/linux-2.6'
> make: *** [debian/stamp-build-kernel] Error 2

I've hit the same build error in 2.6.18-rc4. Maybe the patches should also be added to the main kernel tree?

Regards,
Niels Kristian

             reply	other threads:[~2006-08-11  6:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11  6:13 Niels Kristian Bech Jensen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-10 18:11 latest git: compile error: arch/powerpc/kernel/built-in.o Wolfgang Pfeiffer
2006-08-10 21:14 ` Haren Myneni
2006-08-10 23:21   ` Wolfgang Pfeiffer
2006-08-10 23:48     ` Michael Ellerman
2006-08-17  6:41     ` Paul Mackerras
2006-08-17 12:06       ` Wolfgang Pfeiffer
2006-08-18  0:01         ` Michael Ellerman

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=1155276835.4844.2.camel@localhost \
    --to=nkbj@mail.tele.dk \
    --cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.