From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Gerd Hoffmann <kraxel@suse.de>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: more build errors ...
Date: Tue, 09 Jan 2007 10:55:17 -0800 [thread overview]
Message-ID: <45A3E515.8010004@goop.org> (raw)
In-Reply-To: <45A396AE.8090109@suse.de>
Gerd Hoffmann wrote:
>> arch/i386/kernel/built-in.o: In function `APIC_init_uniprocessor':
>> (.init.text+0x6357): undefined reference to `setup_boot_clock'
>>
>
>
>> drivers/built-in.o: In function `xencons_rx':
>> (.text+0x17f09): undefined reference to `sysrq_enabled'
>>
>
> Here is the fix for both. Not fully sure the first one is correct
> though, I've just moved the inline functions into the correct #ifdef
> CONFIG_foo section, but didn't uninline them like rusty did for the
> apic_* ones. As they are hardly called by modules it should be ok this
> way I think.
>
Thanks. I've merged the xen-console one; I'll do the other one shortly.
J
prev parent reply other threads:[~2007-01-09 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 11:25 more build errors Gerd Hoffmann
2007-01-09 13:20 ` Gerd Hoffmann
2007-01-09 18:55 ` Jeremy Fitzhardinge [this message]
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=45A3E515.8010004@goop.org \
--to=jeremy@goop.org \
--cc=kraxel@suse.de \
--cc=virtualization@lists.osdl.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;
as well as URLs for NNTP newsgroup(s).