autogen.sh warnings

2009-12-07 Thread Bruce Dubbs
I did a fresh checkout of revision 1917 and autogen.sh produces several warnings, although the configure and make stages are OK. I am using relatively new versions of autoconf and automake: automake (GNU automake) 1.11 autoconf (GNU Autoconf) 2.64 When building, a lot of warnings is a red fla

Re: autogen.sh warnings

2009-12-07 Thread Colin Watson
On Mon, Dec 07, 2009 at 11:38:06AM -0600, Bruce Dubbs wrote: > configure.ac:176: required file `./config.rpath' not found > > The can be fixed by `touch config.rpath` configure does actually run this, so I'd recommend copying the file from gettext or gnulib instead. > automake: no `Makefile.am' f

Re: autogen.sh warnings

2009-12-07 Thread Vladimir 'φ-coder/phcoder' Serbinenko
Bruce Dubbs wrote: > I did a fresh checkout of revision 1917 and autogen.sh produces > several warnings, although the configure and make stages are OK. I am > using relatively new versions of autoconf and automake: > > automake (GNU automake) 1.11 > autoconf (GNU Autoconf) 2.64 > > When building,

Re: autogen.sh warnings

2009-12-07 Thread Bruce Dubbs
Vladimir 'φ-coder/phcoder' Serbinenko wrote: Thanks. I'll let someone more familiar with automake to review automake parts. Just a comment to import_gcry These are generated by util/import_gcry.py by copying (and in some cases modifying) the files in lib/libgcrypt to lib/libgcrypt-grub. It al

Re: autogen.sh warnings

2009-12-07 Thread Bruce Dubbs
Colin Watson wrote: On Mon, Dec 07, 2009 at 11:38:06AM -0600, Bruce Dubbs wrote: configure.ac:176: required file `./config.rpath' not found The can be fixed by `touch config.rpath` configure does actually run this, so I'd recommend copying the file from gettext or gnulib instead. The gettex

Re: autogen.sh warnings

2009-12-07 Thread Vladimir 'φ-coder/phcoder' Serbinenko
Bruce Dubbs wrote: > > I'm not sure GRUB uses or needs the output of config.rpath. I was > just suppressing a warning. > Just suppressing warning is a wrong approach. If warning is there it usually means there is a reason for it. And the reason should be corrected, we shouldn't just silence the wa

Re: autogen.sh warnings

2009-12-07 Thread Vladimir 'φ-coder/phcoder' Serbinenko
Bruce Dubbs wrote: > Vladimir 'φ-coder/phcoder' Serbinenko wrote: > >> Thanks. I'll let someone more familiar with automake to review automake >> parts. Just a comment to import_gcry > >>> These are generated by util/import_gcry.py by copying (and in some >>> cases modifying) the files in lib/libgc

Re: autogen.sh warnings

2009-12-07 Thread Colin Watson
On Mon, Dec 07, 2009 at 02:28:19PM -0600, Bruce Dubbs wrote: > Colin Watson wrote: >> On Mon, Dec 07, 2009 at 11:38:06AM -0600, Bruce Dubbs wrote: >>> configure.ac:176: required file `./config.rpath' not found >>> >>> The can be fixed by `touch config.rpath` >> >> configure does actually run this,

Re: autogen.sh warnings

2009-12-07 Thread Bruce Dubbs
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,

Re: autogen.sh warnings

2009-12-07 Thread Bruce Dubbs
Vladimir 'φ-coder/phcoder' Serbinenko wrote: Bruce Dubbs wrote: I'm not sure GRUB uses or needs the output of config.rpath. I was just suppressing a warning. Just suppressing warning is a wrong approach. If warning is there it usually means there is a reason for it. And the reason should be

Re: autogen.sh warnings

2009-12-07 Thread Bruce Dubbs
Colin Watson wrote: On Mon, Dec 07, 2009 at 02:28:19PM -0600, Bruce Dubbs wrote: Colin Watson wrote: It is very likely to be incorrect to suppress a warning about a missing executable by touching an empty file. As I said, configure does use the output of config.rpath. You can verify this f

Re: autogen.sh warnings

2009-12-07 Thread Colin Watson
On Mon, Dec 07, 2009 at 04:49:08PM -0600, Bruce Dubbs wrote: > 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 l

Re: autogen.sh warnings

2009-12-07 Thread Vladimir 'φ-coder/phcoder' Serbinenko
Colin Watson wrote: > On Mon, Dec 07, 2009 at 04:49:08PM -0600, Bruce Dubbs wrote: > >> 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

Re: autogen.sh warnings

2009-12-07 Thread Bruce Dubbs
Vladimir 'φ-coder/phcoder' Serbinenko wrote: Why can't Makefile.in moved to Makefile.am and then just let automake mostly copy Makefile.am to Makefile.in ? (I'm automake newbie), just an idea I've been invoking automake for years, but not writing for it. I'll volunteer to try to make a prope

Re: autogen.sh warnings

2009-12-07 Thread Colin Watson
On Tue, Dec 08, 2009 at 01:01:28AM +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote: > Why can't Makefile.in moved to Makefile.am and then just let automake > mostly copy Makefile.am to Makefile.in ? (I'm automake newbie), just an idea I wouldn't recommend it. The syntax looks similar, but ther

Re: autogen.sh warnings

2009-12-08 Thread Felix Zielcke
Am Montag, den 07.12.2009, 23:54 + schrieb Colin Watson: > > 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 > >

Re: autogen.sh warnings

2009-12-09 Thread Robert Millan
On Mon, Dec 07, 2009 at 07:21:28PM +, Colin Watson wrote: > On Mon, Dec 07, 2009 at 11:38:06AM -0600, Bruce Dubbs wrote: > > configure.ac:176: required file `./config.rpath' not found > > > > The can be fixed by `touch config.rpath` > > configure does actually run this, so I'd recommend copyin

Re: autogen.sh warnings

2009-12-09 Thread Bruce Dubbs
Robert Millan wrote: On Mon, Dec 07, 2009 at 07:21:28PM +, Colin Watson wrote: On Mon, Dec 07, 2009 at 11:38:06AM -0600, Bruce Dubbs wrote: configure.ac:176: required file `./config.rpath' not found The can be fixed by `touch config.rpath` configure does actually run this, so I'd recommen

Re: autogen.sh warnings

2009-12-09 Thread Felix Zielcke
Am Mittwoch, den 09.12.2009, 16:19 -0600 schrieb Bruce Dubbs: > config.guess, config.sub, missing, mkinstalldirs, and install-sh are > only copied from /usr/share/automake- as a part of automake. > AFAICT, they are not used in GRUB. I'm pretty sure they are the same > on > all architectures, bu

Re: autogen.sh warnings

2009-12-09 Thread Robert Millan
On Wed, Dec 09, 2009 at 04:19:08PM -0600, Bruce Dubbs wrote: > Robert Millan wrote: >> On Mon, Dec 07, 2009 at 07:21:28PM +, Colin Watson wrote: >>> On Mon, Dec 07, 2009 at 11:38:06AM -0600, Bruce Dubbs wrote: configure.ac:176: required file `./config.rpath' not found The can be

Re: autogen.sh warnings

2009-12-09 Thread Bruce Dubbs
Felix Zielcke wrote: Am Mittwoch, den 09.12.2009, 16:19 -0600 schrieb Bruce Dubbs: config.guess, config.sub, missing, mkinstalldirs, and install-sh are only copied from /usr/share/automake- as a part of automake. AFAICT, they are not used in GRUB. I'm pretty sure they are the same on all arch

Re: autogen.sh warnings

2009-12-09 Thread Felix Zielcke
Am Mittwoch, den 09.12.2009, 17:28 -0600 schrieb Bruce Dubbs: > Felix Zielcke wrote: > > Am Mittwoch, den 09.12.2009, 16:19 -0600 schrieb Bruce Dubbs: > >> config.guess, config.sub, missing, mkinstalldirs, and install-sh > are > >> only copied from /usr/share/automake- as a part of > automake. >

Re: autogen.sh warnings

2009-12-09 Thread Robert Millan
On Wed, Dec 09, 2009 at 05:28:21PM -0600, Bruce Dubbs wrote: > Felix Zielcke wrote: >> Am Mittwoch, den 09.12.2009, 16:19 -0600 schrieb Bruce Dubbs: >>> config.guess, config.sub, missing, mkinstalldirs, and install-sh are >>> only copied from /usr/share/automake- as a part of automake. >>> AFAIC

Re: autogen.sh warnings

2009-12-09 Thread Bruce Dubbs
Felix Zielcke wrote: Am Mittwoch, den 09.12.2009, 17:28 -0600 schrieb Bruce Dubbs: Felix Zielcke wrote: Am Mittwoch, den 09.12.2009, 16:19 -0600 schrieb Bruce Dubbs: config.guess and config.sub are used by configure. Called yes, and it will give errors if not present, but is the output used

Re: autogen.sh warnings

2009-12-10 Thread Felix Zielcke
Am Donnerstag, den 10.12.2009, 00:05 -0600 schrieb Bruce Dubbs: > On the other hand, config.guess is used to get build_cpu and build_os > and I don't see that being used at all right now by grub. Well just after the part you quoted from me, I thought I made it clear that the output of config.gue

Re: autogen.sh warnings

2009-12-10 Thread Bruce Dubbs
Felix Zielcke wrote: Am Donnerstag, den 10.12.2009, 00:05 -0600 schrieb Bruce Dubbs: On the other hand, config.guess is used to get build_cpu and build_os and I don't see that being used at all right now by grub. Well just after the part you quoted from me, I thought I made it clear that the

Re: autogen.sh warnings

2009-12-24 Thread Robert Millan
On Thu, Dec 10, 2009 at 10:20:21AM -0600, Bruce Dubbs wrote: > Felix Zielcke wrote: >> Am Donnerstag, den 10.12.2009, 00:05 -0600 schrieb Bruce Dubbs: >>> On the other hand, config.guess is used to get build_cpu and build_os >>> and I don't see that being used at all right now by grub. >> >> Well

Re: autogen.sh warnings

2009-12-28 Thread Bruce Dubbs
Robert Millan wrote: On Thu, Dec 10, 2009 at 10:20:21AM -0600, Bruce Dubbs wrote: Felix Zielcke wrote: Am Donnerstag, den 10.12.2009, 00:05 -0600 schrieb Bruce Dubbs: On the other hand, config.guess is used to get build_cpu and build_os and I don't see that being used at all right now by grub.

Re: autogen.sh warnings

2010-01-01 Thread Robert Millan
On Mon, Dec 28, 2009 at 09:50:47PM -0600, Bruce Dubbs wrote: > Robert Millan wrote: >> >> What is exactly the problem? > > Using automake without Makefile.am is non-standard and not provided for > within automake. The only thing we use automake for is to copy > config.{guess,sub} to the root

Re: autogen.sh warnings

2010-01-01 Thread Bruce Dubbs
Robert Millan wrote: On Mon, Dec 28, 2009 at 09:50:47PM -0600, Bruce Dubbs wrote: Robert Millan wrote: What is exactly the problem? Using automake without Makefile.am is non-standard and not provided for within automake. The only thing we use automake for is to copy config.{guess,sub} to

Re: autogen.sh warnings

2010-01-03 Thread Robert Millan
On Fri, Jan 01, 2010 at 10:57:08AM -0600, Bruce Dubbs wrote: > > I thought about it, but I really don't have much experience writing for > autotools. AFAICT, it would require getting rid of all the ruby and > gen*.sh scripts and generally be very invasive. Well, yes. But it's something we ca

Re: autogen.sh warnings

2010-01-07 Thread Robert Millan
On Mon, Dec 07, 2009 at 06:13:33PM -0600, Bruce Dubbs wrote: > Vladimir 'φ-coder/phcoder' Serbinenko wrote: > >> Why can't Makefile.in moved to Makefile.am and then just let automake >> mostly copy Makefile.am to Makefile.in ? (I'm automake newbie), just an idea > > I've been invoking automake for

Building system (Re: autogen.sh warnings)

2009-12-07 Thread Vladimir 'φ-coder/phcoder' Serbinenko
Colin Watson wrote: > I wouldn't recommend it. The syntax looks similar, but there are some > slight differences, and Automake has its own ideas of what rules and > variables you are and aren't allowed to override. Besides, there's quite > a lot of stuff that Automake will output even with an entir

Re: Building system (Re: autogen.sh warnings)

2009-12-07 Thread Bruce Dubbs
Vladimir 'φ-coder/phcoder' Serbinenko wrote: Colin Watson wrote: I wouldn't recommend it. The syntax looks similar, but there are some slight differences, and Automake has its own ideas of what rules and variables you are and aren't allowed to override. Besides, there's quite a lot of stuff that