'autorun.sh' won't run without '.bzr' directory

[chuan]

In release package or export directory where there is no .bzr directory, 'autorun.sh' will fail.

./config/autorun.sh: running `libtoolize --automake --copy --force'
./config/autorun.sh: running `aclocal-1.10 -I m4'
aclocal-1.10: configure.ac:6: file `m4/bzr_version.m4' does not exist
Can't execute aclocal

'autorun.sh' relies on '.bzr' to generate the macro 'bzr_versions.m4'.

[Elliot Murphy (statik)]

I guess this would be a problem if you are trying to build from a
tarball? Probably make dist (or whatever the command is that is used to
build the tarball) should use bzr version-info to generate the .m4 file
or a header file with version information in it. For example:

 bzr version-info --custom \
      --template="#define VERSION_INFO \"Project 1.2.3 (r{revno})\"\n"

--
Elliot Murphy | https://launchpad.net/~statik/

[Monty Taylor (mordred)]

chuan wrote:
> Public bug reported:
>
> In release package or export directory where there is no .bzr directory,
> 'autorun.sh' will fail.
>
> ./config/autorun.sh: running `libtoolize --automake --copy --force'
> ./config/autorun.sh: running `aclocal-1.10 -I m4'
> aclocal-1.10: configure.ac:6: file `m4/bzr_version.m4' does not exist
> Can't execute aclocal
>
>
> 'autorun.sh' relies on '.bzr' to generate the macro 'bzr_versions.m4'.

If you are running from a tarball, you should not need to run
autorun.sh. And, indeed, if you are doing something (like editing
configure.ac) that would require you to re-run autorun.sh... you should
really pull the code from bzr.

So perhaps we need new docs suggesting how things should be built if you
downloaded a tarball.

Monty

[Monty Taylor (mordred)]

Elliot Murphy wrote:
> I guess this would be a problem if you are trying to build from a
> tarball? Probably make dist (or whatever the command is that is used to
> build the tarball) should use bzr version-info to generate the .m4 file
> or a header file with version information in it. For example:
>
> bzr version-info --custom \
> --template="#define VERSION_INFO \"Project 1.2.3 (r{revno})\"\n"

We do something similar to this, although I like this...

Monty

[Lee Bieber (kalebral-deactivatedaccount)]

Closing this as not a bug, as Monty noted if you are building from a tarball you don't need to run this step. If you need to modify anything then you should pull from source.