linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lane <mark@harddata.com>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.22 and Athlon64
Date: Wed, 29 Oct 2003 13:38:40 -0700	[thread overview]
Message-ID: <5.1.1.6.0.20031029125436.03dcd050@mail.harddata.com> (raw)
In-Reply-To: <m3llr3zv98.fsf@averell.firstfloor.org>

At 12:41 PM 10/29/03, Andi Kleen wrote:
>Mark Lane <mark@harddata.com> writes:
>
> > I am having trouble compiling the 2.4.22 kernel for x86-64 non-smp. I
> > can compile the smp kernel but not the regular kernel.
>
>2.4.22 broke the ACPI compilation in the last minute. You can either
>disable ACPI or apply ftp://ftp.x86-64.org/pub/linux/v2.4/acpi-2.4.22-hotfix

Yeah I have tried compiling with ACPI off. This is not my problem.


> > It seems that ksyms.c for x86-64 is looking for some smp stuff from
> > the errors I am getting.
> >
> > I have tried 2.4.23-8 and the problem seems gone but I get an error
> > when linking fs/fs.o into vmlinux. I have attached the errors I
> > received.
>
>fs/fs.o(.text+0x1429f): In function `dput':
>: undefined reference to `atomic_dec_and_lock'
>
>either your tree is unclean (do a make mrproper and try again)
>or your compiler does not properly inline. What compiler are you using?

make mrproper worked thanks
-- 
Mark Lane, CET  mailto:mark@harddata.com
Hard Data Ltd.  http://www.harddata.com
T: 01-780-456-9771      F: 01-780-456-9772
11060 - 166 Avenue Edmonton, AB, Canada, T5X 1Y3
--> Ask me about our Excellent 1U Systems! <--


  reply	other threads:[~2003-10-29 20:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <M4ba.8dv.3@gated-at.bofh.it>
2003-10-29 19:41 ` 2.4.22 and Athlon64 Andi Kleen
2003-10-29 20:38   ` Mark Lane [this message]
2003-10-29 19:21 Mark Lane

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=5.1.1.6.0.20031029125436.03dcd050@mail.harddata.com \
    --to=mark@harddata.com \
    --cc=ak@muc.de \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).