Vorbis dev - Jul 2002 - cvs: debian updates and autogen.sh trouble

Hello,

I couldn't help noticing that the debian build system in cvs was
changed. As I used to compile and install from cvs, I discovered
a small problem regarding autogen.sh. It's called in debian/rules,
before the obj-dir is created (and changed into and ../configure is
started). At least on my system autogen.sh implicitly runs
./configure, so the original source path is already configured and
the following ../configure fails with a hint, to run "make distclean"
in the source path first. Simply changing ../configure into
../autogen.sh didn't help either, because configure looks for
./ltool rather than ../ltool (or something like that).
Changing the call of "./autogen.sh" to "./autogen.sh --help"
did it
for me, because then it just creates configure, prints a help message
and then exits so ../configure can be run without complaining about
an already configured source path.
Of course this wouldn't be a problem in the release version because
it already has configure and autogen.sh isn't needed at all; but
maybe the debian/ maintainer would like to look into it. :)

Regards, Stefan.

--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to
'vorbis-dev-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.

On Wed, Jul 10, 2002 at 03:02:28PM +0200, Stefan Bender
wrote:
> Hello,
> 
> I couldn't help noticing that the debian build system in cvs was
> changed. As I used to compile and install from cvs, I discovered
> a small problem regarding autogen.sh. It's called in debian/rules,
> before the obj-dir is created (and changed into and ../configure is
> started). At least on my system autogen.sh implicitly runs
> ./configure, so the original source path is already configured and
> the following ../configure fails with a hint, to run "make
distclean"
> in the source path first. Simply changing ../configure into
> ../autogen.sh didn't help either, because configure looks for
> ./ltool rather than ../ltool (or something like that).
> Changing the call of "./autogen.sh" to "./autogen.sh
--help" did it
> for me, because then it just creates configure, prints a help message
> and then exits so ../configure can be run without complaining about
> an already configured source path.
> Of course this wouldn't be a problem in the release version because
> it already has configure and autogen.sh isn't needed at all; but
> maybe the debian/ maintainer would like to look into it. :)
> 
Here:

<p>f:/home/cvs/vorbis # ./autogen.sh
I am going to run ./configure with no arguments - if you wish
to pass any to it, please specify them on the ./autogen.sh command line.
Generating configuration files for vorbis, please wait....
  aclocal
  libtoolize --automake
  automake --add-missing
automake: configure.in: installing ./install-sh'
automake: configure.in: installing ./mkinstalldirs'
automake: configure.in: installing ./missing'
configure.in: 42: required file ./ltconfig' not found
  autoconf
configure.in:48: warning: AC_CANONICAL_HOST invoked multiple times
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for ranlib... ranlib
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
./ltconfig: ./ltconfig: No such file or directory
configure: error: libtool configure failed
f:/home/cvs/vorbis #

<p>I tried it on several systems (two SuSE, a Redhat, a home brew system).
May be Ogg Vorbis is Debian only?


-- 
Frank Klemm

<p>--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to
'vorbis-dev-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.

Simple solution is to either:

1. run autogen.sh before dpkg-buildpackage (or however you build the
debs)

2. add make distclean after the line running autogen.sh in debian/rules

I am looking into what to do for a permanent fix.

Chris

--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to
'vorbis-dev-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.