From: "Sean" <seanlkml@rogers.com>
To: "carbonated beverage" <ramune@net-ronin.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.5 bk build failure.
Date: Thu, 24 Jul 2003 08:04:43 -0400 [thread overview]
Message-ID: <002a01c351db$c4e426c0$7f0a0a0a@lappy7> (raw)
In-Reply-To: fa.etf9pq0.cj6k82@ifi.uio.no
> Searched the archive, found a few posts talking about this, but no solution
> seems to have been posted.
> Anyone have an idea?
> Thanks,
> ld -m elf_i386 -T arch/i386/vmlinux.lds.s [snip]
> drivers/built-in.o: In function `x25_asy_changed_mtu':
> drivers/built-in.o(.text+0x6eae6): undefined reference to `save_flags'
> drivers/built-in.o(.text+0x6eaeb): undefined reference to `cli'
> drivers/built-in.o(.text+0x6eba1): undefined reference to `restore_flags'
> make: *** [.tmp_vmlinux1] Error 1
Those macros are being phased out in the new kernel. The code needs to
be updated in the x25_asy driver. Until then, it should still work fine for you
if you compile the kernel for UP instead of SMP.
Cheers,
Sean
next parent reply other threads:[~2003-07-24 11:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.etf9pq0.cj6k82@ifi.uio.no>
2003-07-24 12:04 ` Sean [this message]
2003-07-24 10:33 2.5 bk build failure carbonated beverage
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='002a01c351db$c4e426c0$7f0a0a0a@lappy7' \
--to=seanlkml@rogers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ramune@net-ronin.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