From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GRUB 1.91 is released
Date: Sun, 16 Oct 2005 23:06:44 +0200 [thread overview]
Message-ID: <874q7hb28r.fsf@student.han.nl> (raw)
In-Reply-To: <4352ACF1.8050908@gmail.com> (Joe Ciccone's message of "Sun, 16 Oct 2005 15:41:37 -0400")
Joe Ciccone <jciccone@gmail.com> writes:
> Yoshinori K. Okuji wrote:.
>
>>* Add support for x86_64.
>>
>
> I am curious if support for x86_64 still uses -m32 in the build process,
> and if so, why?
It does. And the reason is that it works like that for me. My
question: why not?
At the moment GRUB itself (so what you use at boot time) is build as
32 bits binaries. The utilities to install GRUB are compiled as AMD64
binaries. So you do not need any 32 bits libraries.
There is a problem, there is a bug in some test that requires 32 bits
binaries. It's a bug and it will be fixed.
So I do not see a reason why we shouldn't use -m32.
--
Marco
next prev parent reply other threads:[~2005-10-16 21:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 18:15 GRUB 1.91 is released Yoshinori K. Okuji
2005-10-15 22:57 ` [SFS breaks PPC build] " Cyril Plisko
2005-10-16 0:47 ` Dennis Clarke
2005-10-16 11:49 ` Marco Gerards
2005-10-16 19:17 ` Dennis Clarke
2005-10-16 19:28 ` Cyril Plisko
2005-10-16 19:51 ` Dennis Clarke
2005-10-16 21:12 ` Marco Gerards
2005-10-16 21:28 ` Cyril Plisko
2005-10-16 21:39 ` Marco Gerards
2005-10-16 21:48 ` Cyril Plisko
2005-10-16 22:13 ` Marco Gerards
2005-10-17 7:30 ` Sparc bootblock [Was: SFS breaks PPC build ] Bart Grantham
2005-10-17 8:20 ` Sparc bootblock Marco Gerards
2005-10-17 10:37 ` Cyril Plisko
2005-10-17 13:38 ` Andrei Warkentin
2005-10-17 13:28 ` Sparc bootblock [Was: SFS breaks PPC build ] Andrei Warkentin
2005-10-17 16:59 ` Vincent Pelletier
2005-10-17 18:01 ` Bart Grantham
2005-10-17 18:13 ` Sparc bootblock Marco Gerards
2005-10-16 19:41 ` GRUB 1.91 is released Joe Ciccone
2005-10-16 21:06 ` Marco Gerards [this message]
2005-10-18 21:14 ` Joe Ciccone
2005-10-20 18:20 ` Marco Gerards
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=874q7hb28r.fsf@student.han.nl \
--to=metgerards@student.han.nl \
--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.