From: Matt Yourst <yourst@mit.edu>
To: unlisted-recipients:; (no To-header on input)@pop.zip.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compiling 2.4.1: undefined reference to `__buggy_fxsr_alignment'
Date: Thu, 01 Feb 2001 01:52:25 -0500 [thread overview]
Message-ID: <3A7907A9.4D501C22@mit.edu> (raw)
In-Reply-To: <3A788DDE.AF82E72F@mit.edu> <3A789A81.78A59680@Home.net>
I used regular gcc 2.95.2 and it compiled and linked without problems.
Thanks.
Shawn Starr wrote:
>
> pgcc borks 2.4.1 kernel and prereleases (sadly I found this out the same
> way).
>
> Shawn.
> Matt Yourst wrote:
>
> > Hi,
> >
> > I just tried to compile 2.4.1 and I'm getting the error "undefined
> > reference to `__buggy_fxsr_alignment'" when trying to do the final
> > link. It looks like this check was something 2.4.1 added to
> > include/asm-i386/bugs.h to fail the kernel build if part of the thread
> > structure wasn't aligned on a 16-byte boundary (which seems to make
> > sense given FXSR's alignment requirements.) When was this check added?
> > I assumed it was a bug in 2.4.0 that was just recently discovered, but
> > I didn't see anything in the ChangeLog to that effect.
>...
-------------------------------------------------------------
Matt T. Yourst Massachusetts Institute of Technology
yourst@mit.edu 617.225.7690
513 French House - 476 Memorial Drive - Cambridge, MA 02139
-------------------------------------------------------------
-
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/
next prev parent reply other threads:[~2001-02-01 6:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 22:12 Compiling 2.4.1: undefined reference to `__buggy_fxsr_alignment' Matt Yourst
2001-01-31 22:16 ` Brian Gerst
2001-01-31 22:18 ` Alan Cox
2001-01-31 23:06 ` Shawn Starr
2001-02-01 6:52 ` Matt Yourst [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-31 23:04 Gian Piero Sala
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=3A7907A9.4D501C22@mit.edu \
--to=yourst@mit.edu \
--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 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.