Vorbis - Jan 2001 - A Top Level README for the nightly CVS snapshot

I ran into a dependency problem while compiling the CVS snapshot which
did not occur while compiling the beta 3 tarballs. For some missing 
resources, autogen.sh echoes very helpful messages (such as if automake 
is not present), but there was no indication that the kdelibs-devel 
package was required for ao (in order to get artsc.h into /usr/include - 
I'm sure it is possible to edit the configure file to get around this 
for those not using vorbis with arts).

Perhaps it would be useful to include a README in the top level of the
.tgz file (which currently expands into 5 directories with README's under
each directory) which explains the system requirements (for Linux - 
automake, libtool, etc.) needed to get the whole thing working and simple
instructions (type autogen.sh, make, make install in the directories
ao/, ogg/ vorbis/ vorbis-tools/ and optionally, vorbis-plugins/).

- Dara Parsavand

p.s. it was libao, libogg, and libvorbis in the beta, but the CVS drops 
the lib from these names - which is preferred?

--- >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-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.

At 03:53 AM 1/7/01 EST, you wrote:
>I ran into a dependency problem while compiling the CVS snapshot which
>did not occur while compiling the beta 3 tarballs. For some missing 
>resources, autogen.sh echoes very helpful messages (such as if automake 
>is not present), but there was no indication that the kdelibs-devel 
>package was required for ao (in order to get artsc.h into /usr/include - 
>I'm sure it is possible to edit the configure file to get around this 
>for those not using vorbis with arts).
I'm not sure what you mean - did configure fail because of this? 
If it did fail, then that's a bug (and a pretty serious one).

If it didn't (and it shouldn't - I added this, and it worked for me even
though I don't have the relevent kde headers present), then that's fine
-
that's only required for the kde aRTs (I probably got the capitalisation
wrong there, but I don't care) plugin. 

If that isn't present, then it doesn't get compiled - as intended.
>p.s. it was libao, libogg, and libvorbis in the beta, but the CVS drops 
>the lib from these names - which is preferred?
The cvs modules are called ao, ogg, and vorbis. The compiled libraries are
libao, libogg, etc. This is independent of whether you have a beta dist
tarball, or a cvs checkout. Neither is 'preferred' - they're for
different
things.

Michael

--- >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-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 my Mandrake 7.2 system, without the kdelibs-devel package installed,
I get the following output from autogen.sh related to arts:

checking for artsc-config... /usr/bin/artsc-config 

I don't know enough about KDE to know if this file is supposed to be
there without any of the kde-devel packages installed (if not, then I 
have a Mandrake bug). If I move this file so it can't be found, make 
and make install work. If not, I get the following output from make:

make[3]: Entering directory `/root/ogg/ao/src/plugins/arts'
/bin/sh ../../../libtool --mode=compile gcc -DPACKAGE=\"libao\"
-DVERSION=\"0.6.0\" -DSIZEOF_SHORT=2 -DSIZEOF_INT=4 -DSIZEOF_LONG=4
-DHAVE_SYS_SOUNDCARD_H=1  -I. -I.  -I../../.. -I../../../include
-I/usr/include/artsc -c ao_arts.c gcc -DPACKAGE=\"libao\"
-DVERSION=\"0.6.0\" -DSIZEOF_SHORT=2 -DSIZEOF_INT=4 -DSIZEOF_LONG=4
-DHAVE_SYS_SOUNDCARD_H=1 -I. -I. -I../../.. -I../../../include
-I/usr/include/artsc -Wp,-MD,.deps/ao_arts.pp -c  -fPIC -DPIC ao_arts.c
-o ao_arts.loao_arts.c:29: artsc.h: No such file or directory make[3]:
*** [ao_arts.lo] Error 1

modules ogg and vorbis then seem to compile ok and then when running 
autogen.sh for vorbis-tools, I get:

checking for ao... no
*** Could not run ao test program, checking why...
*** The test program failed to compile or link. See the file config.log for
the
*** exact error that occured. This usually means ao was incorrectly installed
*** or that you have moved ao since it was installed.
configure: error: libao needed! 

If I look in /usr/local/lib, the only files related to ao are:

ao/liboss.la*  and ao/liboss.so*, apparently not enough to work with 
vorbis-tools

Sorry, I should have figured this all out before my first posting.

- Dara Parsavand

p.s. out of curiosity, I get warnings when running autogen.sh such as:

configure.in:84,85,86: 
warning: AC_TRY_RUN called without default to allow cross compiling

what is this caused by?       

--- >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-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.