From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: grub-devel@gnu.org
Subject: grub-1.97
Date: Tue, 27 Oct 2009 20:59:15 -0500 [thread overview]
Message-ID: <4AE7A573.4030002@gmail.com> (raw)
I am putting grub2 into the Linux From Scratch book and have built/tested it and
it works quite well for us. Thank you.
I do have a question. After building a package, we like to test it for those
packages that have tests built in. When I tried `make test`, I got an error
about missing m2c. I then went to the Debian repository and built m2c. Now I
get the error:
bdubbs@core2:/usr/src/grub/grub-1.97$ make test
m2c -o test -e test test.mod
m2c: unknown flag `-e'
make: *** [test] Error 1
What version of m2c are you using and where is it available? Is this a valid
way to run a regression test for grub-1.97?
I'd also like to make a comment. It may be useful if you split up the build
into subdirectories by component. When I extracted the tarball, there were 57
files/directories in the top of the build tree. After configure it was 64. So
far so good. However, after make it was over 2400 files, many with very long
file names. This makes it almost impossible to navigate form the command line,
even on a very big screen. If you split it up, you could also shorten the
filenames. I would think that would be an advantage to encourage programmers to
read the code and contribute to the project.
-- Bruce Dubbs
linuxfromscratch.org
next reply other threads:[~2009-10-28 1:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 1:59 Bruce Dubbs [this message]
2009-10-28 9:21 ` grub-1.97 Colin Watson
2009-10-28 15:40 ` grub-1.97 Bruce Dubbs
2009-10-28 11:34 ` grub-1.97 Michal Suchanek
2009-10-28 16:02 ` grub-1.97 Bruce Dubbs
2009-10-28 16:39 ` grub-1.97 Felix Zielcke
2009-10-28 17:23 ` grub-1.97 Felix Zielcke
2009-10-28 17:41 ` grub-1.97 Bruce Dubbs
2009-10-29 3:50 ` grub-1.97 richardvoigt
2009-10-29 4:44 ` grub-1.97 Bruce Dubbs
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=4AE7A573.4030002@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.