From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: multiboot code asking for stubs-32.h under x86-64?
Date: Fri, 5 Oct 2007 13:59:52 +0200 [thread overview]
Message-ID: <20071005115952.GA32297@thorin> (raw)
In-Reply-To: <1191534607.2586.5.camel@mobile.box.org>
On Thu, Oct 04, 2007 at 11:50:07PM +0200, Julio Meca Hansen wrote:
> hmm... a regression test? but... the only thing that's not behaving
> properly in my almost-fully-compiled system is the search for
> stubs-32.h, I suppose the correct behaviour would be to search just for
> stubs.h or in the excessive case, for stubs-64.h, but as I have a pure64
> system there's not any presence of 32bit libraries...
>
> anyway... if grub-1.95 can support journaled ext3 filesystems, it would
> suffice to me, but I'm not sure and I was quite afraid of messing
> something...
>
> to be honest, I'm not much of an experienced programmer in linux and
> performing a regression tests looks like a bit difficult, and you're
> refering to wine instructions, but my system, to be clear... just needs
> grub2 in order to obtain the 'stage 1' system status, that's...
>
> just pure console linux, no aditional libraries, not any kind of X
> server, no desktop, and so on... so I need this step successfully
> fulfilled
Why are you compiling GRUB in 64-bit mode then? It's not supported yet.
Doesn't the build system automaticaly ressort to 32-bit build for you?
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2007-10-05 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 6:28 multiboot code asking for stubs-32.h under x86-64? Julio Meca Hansen
2007-10-04 20:53 ` Robert Millan
2007-10-04 21:50 ` Julio Meca Hansen
2007-10-05 11:59 ` Robert Millan [this message]
2007-10-05 13:15 ` Julio Meca Hansen
2007-10-05 20:45 ` Robert Millan
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=20071005115952.GA32297@thorin \
--to=rmh@aybabtu.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.