Compiling 2.4.1: undefined reference to `__buggy_fxsr_alignment'
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
[email protected] 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 [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 21 lines · Matt Yourst
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.hto 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.)
Quoted 4 lines
Anyone else had this problem?
- Matt Yourst
What GCC version did you compile with?
--
Brian Gerst
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 1 line
reference to `__buggy_fxsr_alignment'" when trying to do the final
Dont use pgcc 2.95, at least until they fix that 8)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
pgcc borks 2.4.1 kernel and prereleases (sadly I found this out the same way).
Shawn.
Quoted 24 lines · Matt Yourst
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.hto 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
Quoted 9 lines
-------------------------------------------------------------
Matt T. Yourst Massachusetts Institute of Technology
[email protected] 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 [email protected]
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 [email protected]
Please read the FAQ at http://www.tux.org/lkml/
I used regular gcc 2.95.2 and it compiled and linked without problems. Thanks.
Quoted 17 lines · Shawn Starr
pgcc borks 2.4.1 kernel and prereleases (sadly I found this out the same way).
Shawn.
Quoted 10 lines · Matt Yourst
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.hto 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.
Quoted 1 line
...
-------------------------------------------------------------
Matt T. Yourst Massachusetts Institute of Technology
[email protected] 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 [email protected]
Please read the FAQ at http://www.tux.org/lkml/