From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Documenting the GRUB configure (during build)
Date: Fri, 04 Dec 2009 19:46:24 -0600 [thread overview]
Message-ID: <4B19BB70.8010509@gmail.com> (raw)
I want to submit an update to the INSTALL file. In looking at
./configure, it does some guessing. We have:
`--enable-efiemu'
Build and install the efiemu runtimes (default=guessed)
`--enable-grub-emu'
Build and install the `grub-emu' debugging utility (default=guessed)
`--enable-grub-emu-usb'
Build and install the `grub-emu' debugging utility with USB support
(default=guessed)
`--enable-grub-fstest'
Build and install the `grub-fstest' debugging utility
(default=guessed)
`--enable-grub-mkfont'
Build and install the `grub-mkfont' utility (default=guessed)
------
I am trying to see how configure guesses. It looks like:
enable-efiemu depends on gcc supporting
-m64 -mcmodel=large -mno-red-zone -nostdlib
enable-grub-emu depends on ncurses
enable-grub-emu-usb depends on enable-grub-emu and libusb
enable-grub-fstest really has a default of yes
enable-grub-mkfont depends on fontconfig
-------
Is this analysis right?
Should the description of enable-grub-fstest be changed to yes in
configure.ac?
Actually, I would think the four testing/debug programs above should
default to no with perhaps a global --enable-testing-programs to turn
them all on.
Of course grub-mkfont should be on by default if fontconfig is
available, as it is
now.
--- Bruce
next reply other threads:[~2009-12-05 1:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-05 1:46 Bruce Dubbs [this message]
2009-12-05 20:43 ` Documenting the GRUB configure (during build) Robert Millan
2009-12-05 21:42 ` Bruce Dubbs
2009-12-06 0:03 ` Seth Goldberg
2009-12-10 1:15 ` Robert Millan
2009-12-10 21:17 ` Bruce Dubbs
2009-12-10 21:28 ` Seth Goldberg
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=4B19BB70.8010509@gmail.com \
--to=bruce.dubbs@gmail.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.