From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: autogen.sh warnings
Date: Mon, 07 Dec 2009 16:49:08 -0600 [thread overview]
Message-ID: <4B1D8664.4070403@gmail.com> (raw)
In-Reply-To: <4B1D6AB9.8070105@gmail.com>
I've been looking at autogen.sh some more.
Does anyone know why the lines:
# FIXME: automake doesn't like that there's no Makefile.am
automake -a -c -f || true
are present at all? Since there is no Makefile.am, it looks like
automake only creates a few files and aborts.
Doing an experiment, I checked out a new version of trunk twice. In
both cases I ran md5sum on all the files in the top level directory. In
case 1, I didn't change anything and ran autogen.sh and then ran md5sum
again. In case 2, I commented out the automake line above.
As you can see below, automake only adds standard 'config.guess',
'config.sub', and 'missing' scripts.
The real purpose of automake is to create a Makefile.in for configure.
GRUB doesn't use it for that. Is there any reason to not just add the
three files to the bzr repository and remove the automake line from
autogen.sh?
Along with the other changes I proposed, it would create a really clean
build process.
-- Bruce
Case 1:
> b30696711539bc73520a58a595d488d3 DISTLIST
10a12
> 7e34eb2ddac5ca0b3a0852302ef0970d aclocal.m4
11a14,17
> f9410e9a94fc672046d4997ecf1b69c9 config.guess
> 55061a86b93fd314344c7f41a9662db9 config.h.in
> acb6cfae431c5ce7b2319cd668c86555 config.sub
> 904614dd3a3ea6442432dba9b20062df configure
25a32,34
> 0afce91a3daa1fdc32ee36370c1129dd install-sh
> 6c12e662cd14b9b276338ec99c6ef3a7 md5sums
> 9d9668fb32d0542b712be2c34ca79bd7 missing
26a36
> 1ded054093de910d9786c62bc4fe8cc6 stamp-h.in
Case 2:
3a4
> b30696711539bc73520a58a595d488d3 DISTLIST
10a12
> 7e34eb2ddac5ca0b3a0852302ef0970d aclocal.m4
12a15,16
> 55061a86b93fd314344c7f41a9662db9 config.h.in
> 904614dd3a3ea6442432dba9b20062df configure
26a31
> 29505be85d45d8a9b0a5fd3478ff6887 md5sums
27a33
> 1ded054093de910d9786c62bc4fe8cc6 stamp-h.in
next prev parent reply other threads:[~2009-12-07 22:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 17:38 autogen.sh warnings Bruce Dubbs
2009-12-07 19:21 ` Colin Watson
2009-12-07 20:28 ` Bruce Dubbs
2009-12-07 22:12 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-07 23:07 ` Bruce Dubbs
2009-12-07 22:40 ` Colin Watson
2009-12-07 23:26 ` Bruce Dubbs
2009-12-09 21:52 ` Robert Millan
2009-12-09 22:19 ` Bruce Dubbs
2009-12-09 22:34 ` Felix Zielcke
2009-12-09 23:28 ` Bruce Dubbs
2009-12-10 0:25 ` Felix Zielcke
2009-12-10 6:05 ` Bruce Dubbs
2009-12-10 10:15 ` Felix Zielcke
2009-12-10 16:20 ` Bruce Dubbs
2009-12-24 21:13 ` Robert Millan
2009-12-29 3:50 ` Bruce Dubbs
2010-01-01 11:33 ` Robert Millan
2010-01-01 16:57 ` Bruce Dubbs
2010-01-03 16:25 ` Robert Millan
2009-12-10 0:49 ` Robert Millan
2009-12-09 22:56 ` Robert Millan
2009-12-07 19:50 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-07 20:51 ` Bruce Dubbs
2009-12-07 22:16 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-07 22:49 ` Bruce Dubbs [this message]
2009-12-07 23:54 ` Colin Watson
2009-12-08 0:01 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-08 0:13 ` Bruce Dubbs
2010-01-07 19:14 ` Robert Millan
2009-12-08 0:16 ` Colin Watson
2009-12-08 0:34 ` Building system (Re: autogen.sh warnings) Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-08 3:40 ` Bruce Dubbs
2009-12-08 10:20 ` autogen.sh warnings Felix Zielcke
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=4B1D8664.4070403@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.