From: Colin Watson <cjwatson@ubuntu.com>
To: grub-devel@gnu.org
Subject: Re: "Illegal Instruction" error in grub_script_comments
Date: Mon, 17 Oct 2016 23:32:40 +0100 [thread overview]
Message-ID: <20161017223240.GA13916@riva.ucam.org> (raw)
In-Reply-To: <CAP8WD_YrGj255VMrU=x_hQwJQ2H67cPAJKOKQfcaCreSjrLN2w@mail.gmail.com>
On Mon, Oct 17, 2016 at 02:34:16PM -0400, tedheadster wrote:
> I am building the older grub2-1.98+20100804 under the similarly old Debian
> 'squeeze' distribution. However, I bet the error persists with newer
> version. This is because I am building it on a true Intel 80486 and I don't
> thing the compiler is building for the correct architecture.
If it is in fact the lack of an -march= option that's at fault, then
that was fixed in 2.02~beta1:
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=02663ee9d9cae806f90518bc4c89d31ae11b84e4
(You may be best simply setting TARGET_CFLAGS='-march=i386 -Os' in the
environment when running configure, rather than trying to regenerate
configure with that patch.)
If that doesn't do it, then it may be something more involved such as
hand-written non-486-compatible assembly somewhere, which won't be cured
by a compiler option. GRUB is mostly in C, but something running at the
level of a boot loader does tend to need at least a little bit of
assembly to get itself going.
--
Colin Watson [cjwatson@ubuntu.com]
next prev parent reply other threads:[~2016-10-17 22:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 18:34 "Illegal Instruction" error in grub_script_comments tedheadster
2016-10-17 22:32 ` Colin Watson [this message]
2016-10-18 19:12 ` Lennart Sorensen
2016-10-19 15:32 ` Matthew Whitehead
2016-10-19 19:06 ` Lennart Sorensen
2016-10-19 19:16 ` Matthew Whitehead
2016-10-31 3:17 ` Matthew Whitehead
2016-10-20 17:34 ` Andrei Borzenkov
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=20161017223240.GA13916@riva.ucam.org \
--to=cjwatson@ubuntu.com \
--cc=grub-devel@gnu.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.