public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Starr <Shawn.Starr@Home.net>
To: Matt Yourst <yourst@mit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compiling 2.4.1: undefined reference to `__buggy_fxsr_alignment'
Date: Wed, 31 Jan 2001 18:06:41 -0500	[thread overview]
Message-ID: <3A789A81.78A59680@Home.net> (raw)
In-Reply-To: <3A788DDE.AF82E72F@mit.edu>

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.
>
> The problem is that I don't know how to fix it (at least not reliably
> and cleanly.) I tried rearranging the fields in the task structure,
> but the alignment still wasn't right. I did apply a few non-standard
> patches that expanded the task structure, but the additional fields
> came well after the task's struct thread (which was causing the
> alignment problem.) FYI, I'm compiling with pgcc 2.95.2 and linking
> with binutils/ld 2.10 (I've used both of these successfully for
> countless kernel compiles before this.)
>
> Anyone else had this problem?
>
> - Matt Yourst
>
> -------------------------------------------------------------
>  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/

-
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/

  parent reply	other threads:[~2001-01-31 23:07 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 [this message]
2001-02-01  6:52   ` Matt Yourst
  -- 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=3A789A81.78A59680@Home.net \
    --to=shawn.starr@home.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yourst@mit.edu \
    /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