public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Starr <Shawn.Starr@Home.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [PROBLEM] 2.4.1-pre2 - Undefined symbol `__buggy_fxsr_alignment' -  (FIXED)
Date: Thu, 11 Jan 2001 22:49:24 -0500	[thread overview]
Message-ID: <3A5E7EC4.39CC7298@Home.net> (raw)
In-Reply-To: <3A5E4B1D.5EF1B0EB@Home.net> <3A5E7DB2.A7126A68@Home.net>

errrr i think it was just fixed in pre3 ;-)

+       if (offsetof(struct task_struct, thread.i387.fxsave) & 15) {
+               extern void __buggy_fxsr_alignment(void);
+               __buggy_fxsr_alignment();
+       }


> GCC 2.95.2 -> PGCC 2.95.2(3?) patched. 2.4.0 compiles fine
>
> init/main.o: In function `check_fpu':
> init/main.o(.text.init+0x53): undefined reference to `__buggy_fxsr_alignment'
>
> make: *** [vmlinux] Error 1
>
> On compiling (and recompiling) i get this fatal error. This function
> does not exist anymore?
>
> Anyone else having this problem?
>
> Shawn Starr.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-12  3:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-12  0:09 Critical compile bug: 2.4.1-pre2 alpha Shawn Starr
2001-01-12  3:44 ` [PROBLEM] 2.4.1-pre2 - Undefined symbol `__buggy_fxsr_alignment' Shawn Starr
2001-01-12  3:49   ` Shawn Starr [this message]
2001-01-12 20:02     ` [CONT PROBLEM] 2.4.1-pre3 " Shawn Starr
2001-01-12 21:20       ` Matti Aarnio
2001-01-12 21:30         ` Shawn Starr

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=3A5E7EC4.39CC7298@Home.net \
    --to=shawn.starr@home.net \
    --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