Add missing bootstrap file

[Jan Engelhardt-3]

Hi,


in the automake tarballs, the 'bootstrap' script is missing, but it
would be needed when modifying any of the automake files in a tarball.
In other words, when used in an rpm build script:

Source: automake-1.11.tar.bz2
Patch1: foobar.diff modifying m4/init.m4

Not running bootstrap after applying Patch1 causes configure/make to fail:

+ ./configure
[...]
+ make
CDPATH="${ZSH_VERSION+.}:" && cd . &&
perllibdir="/usr/src/packages/BUILD/automake-1.11/lib:./lib"
"/usr/src/packages/BUILD/automake-1.11/aclocal" --acdir=m4 -I m4
/bin/sh: /usr/src/packages/BUILD/automake-1.11/aclocal: No such file or
directory
make: *** [aclocal.m4] Error 127
error: Bad exit status from /var/tmp/rpm-tmp.CEw4fJ (%build)

Please provide the bootstrap script in the next release tarballs instead
of just the git tree.

Thanks,
Jan

[Ralf Wildenhues]

Hi Jan,

* Jan Engelhardt wrote on Mon, Nov 09, 2009 at 02:09:14AM CET:
> in the automake tarballs, the 'bootstrap' script is missing, but it
> would be needed when modifying any of the automake files in a tarball.

Sounds reasonable to me, esp. since it doesn't even use git in any way
(yet).

> In other words, when used in an rpm build script:
>
> Source: automake-1.11.tar.bz2
> Patch1: foobar.diff modifying m4/init.m4

BTW, what's in that patch?

Thanks,
Ralf

[Gaetan Nadon-2]

On Sat, 2009-11-14 at 14:06 +0100, Ralf Wildenhues wrote:

> Hi Jan,
>
> * Jan Engelhardt wrote on Mon, Nov 09, 2009 at 02:09:14AM CET:
> > in the automake tarballs, the 'bootstrap' script is missing, but it
> > would be needed when modifying any of the automake files in a tarball.
>
> Sounds reasonable to me, esp. since it doesn't even use git in any way
> (yet).
>

I have recently downloaded from the GNU site various versions of
automake. I did what the INSTALL file tells me to do. Run ./configure
and then make. I had no other automake version installed. It worked
right away in all cases. I don't see why any file would be missing in
the automake traball. At first, I did not have autoconf installed, so
automake told me it was missing. The INSTALL file is not talking about
any boostrap file.

If you want to modify files in automake, then you are doing development,
rather than just installing the software. Given that automake requires
itself, there may be special things to do. In any case, nothing should
be added to the tarball that isn't required for installation.

I hope it helps.

> > In other words, when used in an rpm build script:
> >
> > Source: automake-1.11.tar.bz2
> > Patch1: foobar.diff modifying m4/init.m4
>
> BTW, what's in that patch?
>
> Thanks,
> Ralf
>
>

[Peter Johansson-7]

Gaetan Nadon wrote:
>
> If you want to modify files in automake, then you are doing development,
> rather than just installing the software. Given that automake requires
> itself, there may be special things to do. In any case, nothing should
> be added to the tarball that isn't required for installation.
>
>  
 From where did you get that rule? It doesn't go very well with the fact
that automake by default adds Makefile.am, configure.ac and other .m4
files to the tarball. Those files will never be useful for a pure
./configure; make; make install, but as soon as you wanna fix a bug or
just modify the package you'll be happy those files are around.

Peter

[Gaetan Nadon-2]

On Sat, 2009-11-14 at 09:35 -0500, Peter Johansson wrote:

> Gaetan Nadon wrote:
> >
> > If you want to modify files in automake, then you are doing development,
> > rather than just installing the software. Given that automake requires
> > itself, there may be special things to do. In any case, nothing should
> > be added to the tarball that isn't required for installation.
> >
> >  
>  From where did you get that rule? It doesn't go very well with the fact
> that automake by default adds Makefile.am, configure.ac and other .m4
> files to the tarball. Those files will never be useful for a pure
> ./configure; make; make install, but as soon as you wanna fix a bug or
> just modify the package you'll be happy those files are around.
>

I messed up my point, sorry. Based on my experience, there is nothing
missing, but I cannot prove it.


> Peter

[Jan Engelhardt-3]

On Saturday 2009-11-14 14:06, Ralf Wildenhues wrote:

>Hi Jan,
>
>* Jan Engelhardt wrote on Mon, Nov 09, 2009 at 02:09:14AM CET:
>> in the automake tarballs, the 'bootstrap' script is missing, but it
>> would be needed when modifying any of the automake files in a tarball.
>
>Sounds reasonable to me, esp. since it doesn't even use git in any way
>(yet).
>
>> In other words, when used in an rpm build script:
>>
>> Source: automake-1.11.tar.bz2
>> Patch1: foobar.diff modifying m4/init.m4
>
>BTW, what's in that patch?

You sure don't want to have it.

---
 m4/init.m4 |    1 +
 1 file changed, 1 insertion(+)

Index: automake/m4/init.m4
===================================================================
--- automake.orig/m4/init.m4
+++ automake/m4/init.m4
@@ -107,6 +107,7 @@ dnl is hooked onto _AC_COMPILER_EXEEXT e
 AC_CONFIG_COMMANDS_PRE(dnl
 [m4_provide_if([_AM_COMPILER_EXEEXT],
   [AM_CONDITIONAL([am__EXEEXT], [test -n "$EXEEXT"])])])dnl
+AM_SILENT_RULES([yes])
 ])
 
 dnl Hook into `_AC_COMPILER_EXEEXT' early to learn its expansion.  Do not

[Bob Friesenhahn]

On Sat, 14 Nov 2009, Peter Johansson wrote:
>>
> From where did you get that rule? It doesn't go very well with the fact that
> automake by default adds Makefile.am, configure.ac and other .m4 files to the
> tarball. Those files will never be useful for a pure ./configure; make; make
> install, but as soon as you wanna fix a bug or just modify the package you'll
> be happy those files are around.

Yes, and these added files assist with assuring compliance with the
GPL, which requires that all original source files and scripts that
the developer needs to build and install the software are included, or
otherwise formally made available.

Bob
--
Bob Friesenhahn
bfriesen@..., http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

[Alfred M. Szmidt]

   Index: automake/m4/init.m4
   ===================================================================
   --- automake.orig/m4/init.m4
   +++ automake/m4/init.m4
   @@ -107,6 +107,7 @@ dnl is hooked onto _AC_COMPILER_EXEEXT e
    AC_CONFIG_COMMANDS_PRE(dnl
    [m4_provide_if([_AM_COMPILER_EXEEXT],
      [AM_CONDITIONAL([am__EXEEXT], [test -n "$EXEEXT"])])])dnl
   +AM_SILENT_RULES([yes])
    ])

Why is this needed?  Maybe the problem can be solved in a better way.

[Jan Engelhardt-3]

[Note that this has nothing to do with the bootstrap file]


On Sunday 2009-11-15 17:44, Alfred M. Szmidt wrote:

>   Index: automake/m4/init.m4
>   ===================================================================
>   --- automake.orig/m4/init.m4
>   +++ automake/m4/init.m4
>   @@ -107,6 +107,7 @@ dnl is hooked onto _AC_COMPILER_EXEEXT e
>    AC_CONFIG_COMMANDS_PRE(dnl
>    [m4_provide_if([_AM_COMPILER_EXEEXT],
>      [AM_CONDITIONAL([am__EXEEXT], [test -n "$EXEEXT"])])])dnl
>   +AM_SILENT_RULES([yes])
>    ])
>
>Why is this needed?  Maybe the problem can be solved in a better way.
>

Because I want it for everything that I run autoreconf on, regardless of
whether a package added enough goo to enable it or not. It is thus
needed in init.m4, because a previously-existing configure may not have
included the verbosity messages at all.

[Alfred M. Szmidt]

You didn't answer why you need this switch, only that you want it.

[Ralf Wildenhues]

Hi Alfred,

* Alfred M. Szmidt wrote on Mon, Nov 16, 2009 at 08:33:10PM CET:
> You didn't answer why you need this switch, only that you want it.

Various threads on this list during the last months document this,
I would say.  It otherwise isn't even hard to guess.  ;-)

Cheers,
Ralf