From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Igor Yu. Zhbanov" <bsg@uniyar.ac.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: __buggy_fxsr_alignment() not found.
Date: Mon, 1 Mar 2004 12:24:28 -0800 [thread overview]
Message-ID: <20040301122428.7dc96b00.rddunlap@osdl.org> (raw)
In-Reply-To: <Pine.GSO.3.96.SK.1040229200132.17294A-100000@univ.uniyar.ac.ru>
On Sun, 29 Feb 2004 20:02:12 +0300 (MSK) Igor Yu. Zhbanov wrote:
| Hello!
| My system is:
| AMD K6-II 450
| Linux-2.4.24
| glibc-2.2.5
|
| I cannot compile 2.4.24 kernel because linker says:
| init/main.o: In function `check_fpu':
| init/main.o(.text.init+0x53): undefined reference to `__buggy_fxsr_alignment'
|
| It's prototype is in inculude/asm-i386/bugs.h:
| -----
| /* Enable FXSR and company _before_ testing for FP problems. */
| /*
| * Verify that the FXSAVE/FXRSTOR data will be 16-byte aligned.
| */
| if (offsetof(struct task_struct, thread.i387.fxsave) & 15) {
| extern void __buggy_fxsr_alignment(void);
| __buggy_fxsr_alignment();
| -----
| But there is no realisation of this function in source files.
| When I comment the lines above, everything works.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This function is not supposed to be defined anywhere.
It is there to indicate a build error and to keep the kernel
build from completing successfully.
For some reason, with your config (and CPU arch.) and compiler,
the 'fxsave' field is not on a 16-byte alignment. Have you applied
any patches to 2.4.24? What version of gcc are you using (gcc -v)?
--
~Randy
next prev parent reply other threads:[~2004-03-01 20:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 17:02 Igor Yu. Zhbanov
2004-02-29 17:54 ` Michael Frank
2004-03-01 20:24 ` Randy.Dunlap [this message]
2004-03-04 11:01 ` Igor Yu. Zhbanov
2004-03-04 13:18 ` Mikael Pettersson
2004-03-04 13:21 ` Brian Gerst
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=20040301122428.7dc96b00.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=bsg@uniyar.ac.ru \
--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
all inboxes | Powered by JetHome®