From: Joe Lewis <joe@joe-lewis.com>
To: grub-devel@gnu.org
Subject: Question about static compiling
Date: Sat, 25 Oct 2008 09:47:52 -0600 [thread overview]
Message-ID: <49033FA8.5010106@joe-lewis.com> (raw)
Hello, folks;
I joined this list as I have been unable to find a solution that I agree
with on a simple question. This should be short, and an answer should
help others to find solutions through searching. My simple question is
- how do I compile a static form of grub2?
The background - I am trying to create my own LFS system on a dual
quad-core Xeon (x86_64), and the LFS turns out to be a pure-64 bit
environment. I am unable to compile grub, as it requires a 32 bit libc,
and everything I find about grub shows I will have to use a statically
compiled version. My research (mailing list, google, etc) only revealed
setting the enviroment variable for the CFLAGS with a -static, but that
STILL resulted in the binaries holding a reference to /lib/ld-linux.so,
which doesn't exist in a true 64 bit environment - it is
/lib/ld-linux-x86_64.so . And, since it is a 64 bit environment, the
"static" binaries complain about a corrupt shared object if one just
slaps a symlink in there (I've tried everything I can think of).
I finally hit a wall, and I do not know where to look next. Has anyone
built grub2 on another platform for use in an LFS pure-64 bit
environment? Has anyone successfully compiled grub2 in a 64 bit
environment (I doubt this, but it doesn't hurt to ask) ? I'd be willing
to act as a guinea pig if anyone has some patches to test with, etc. I
had the svn version of 1886.
Many thanks for taking the time to read this,
Joe
next reply other threads:[~2008-10-25 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-25 15:47 Joe Lewis [this message]
2008-10-25 17:14 ` Question about static compiling Manoel
2008-10-26 22:45 ` Joe Lewis
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=49033FA8.5010106@joe-lewis.com \
--to=joe@joe-lewis.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.