Hi,
I'm getting this problem building sndinfo. I guess it has to do with my
older version of libsndfile...
Can any one help?

Cheers,
Andrés

gcc -Wall -g -gstabs -O2 -DLINUX -DPIPES -fPIC -DBETA -DHAVE_FCNTL_H
-DHAVE_UNIS
TD_H -DHAVE_STDINT_H -DHAVE_SYS_TIME_H -DHAVE_SYS_TYPES_H
-DHAVE_TERMIOS_H -DHAV
E_DIRENT_H -I. -IH -I/usr/local/include -I/usr/include
-I/usr/X11R6/include -c -
o util/sndinfo.os util/sndinfo.c
util/sndinfo.c: In function 'sndinfo':
util/sndinfo.c:116: error: 'SF_INSTRUMENT' has no member named
'velocity_lo'
util/sndinfo.c:116: error: 'SF_INSTRUMENT' has no member named
'velocity_hi'
util/sndinfo.c:118: error: 'SF_INSTRUMENT' has no member named 'key_lo'
util/sndinfo.c:118: error: 'SF_INSTRUMENT' has no member named 'key_hi'
util/sndinfo.c:119: error: 'SF_INSTRUMENT' has no member named
'loop_count'
util/sndinfo.c:121: error: 'SF_INSTRUMENT' has no member named
'loop_count'
util/sndinfo.c:126: error: 'SF_INSTRUMENT' has no member named 'loops'
util/sndinfo.c:127: error: 'SF_INSTRUMENT' has no member named 'loops'
util/sndinfo.c:128: error: 'SF_INSTRUMENT' has no member named 'loops'
util/sndinfo.c:129: error: 'SF_INSTRUMENT' has no member named 'loops'
util/sndinfo.c:130: error: 'SF_INSTRUMENT' has no member named 'loops'
util/sndinfo.c:130: error: 'SF_INSTRUMENT' has no member named 'loops'
util/sndinfo.c:131: error: 'SF_INSTRUMENT' has no member named 'loops'
util/sndinfo.c:135: error: 'SF_BROADCAST_INFO' undeclared (first use in
this fun                 ction)
util/sndinfo.c:135: error: (Each undeclared identifier is reported only
once
util/sndinfo.c:135: error: for each function it appears in.)
util/sndinfo.c:135: error: syntax error before 'bext'
util/sndinfo.c:136: error: 'SFC_GET_BROADCAST_INFO' undeclared (first
use in thi                 s function)
util/sndinfo.c:136: error: 'bext' undeclared (first use in this
function)




_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-dev

Andres Cabrera wrote:

> Hi,I'm getting this problem building sndinfo. I guess it has to do
> with myolder version of libsndfile

Correct.

> ...Can any one help?

You can help yourself by upgrading your version of libsndfile :-).
The current verison, 1.0.16, is known to work.

Erik
-- 
+-----------------------------------------------------------+
  Erik de Castro Lopo
+-----------------------------------------------------------+
"The lusers I know are so clueless, that if they were dipped in
 clue musk and dropped in the middle of pack of horny clues, on
 clue prom night during clue happy hour, they still couldn't get
 a clue."   --Michael Girdwood, in the monastery


_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Erik,
Since I'm on planetCCRMA, and may things depend on libsndfile, I'm
hesitant to manually upgrade.... Nothing should break if I do right?

Here's a question, is libsndfile statically linked in csound (or can it
be?)? If so, is just building the latest libsndfile and setting the
directories in custom.py enough?

Cheers,
Andrés



On Thu, 2006-06-01 at 13:20 +1000, Erik de Castro Lopo wrote:
> Andres Cabrera wrote:
> 
> > Hi,I'm getting this problem building sndinfo. I guess it has to do
> > with myolder version of libsndfile
> 
> Correct.
> 
> > ...Can any one help?
> 
> You can help yourself by upgrading your version of libsndfile :-).
> The current verison, 1.0.16, is known to work.
> 
> Erik



_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/li

Andres Cabrera wrote:

> Hi Erik,Since I'm on planetCCRMA, and may things depend on libsndfile, I'm
> hesitant to manually upgrade.... Nothing should break if I do right?

When updating libsndfile I take great care not to break brackwards
compatibility and hence the version number goes from 1.0.X to 1.0.Y.
If I ever do need to break backwards compatibility, the A or B in
the A.B.C number system will change.

Thats said I usually recommend against replacing distribution supplied
libraries with one you compile yourself because it can screw up the
package management. However, if you know how to make an quasi official 
package for your system then that is OK.

> Here's a question, is libsndfile statically linked in csound (or can it
> be?)? If so, is just building the latest libsndfile and setting the
> directories in custom.py enough?

This is definitely possible. If you get libsndfile and do:

    ./configure --disable-shared --prefix=/tmp/lsf
    make
    make check
    make install

you can then tell SCONS to find libsndfile in /tmp/lsf and since it
will only find the static version of the library, it should be fine.

Erik
-- 
+-----------------------------------------------------------+
  Erik de Castro Lopo
+-----------------------------------------------------------+
I'd rather not work with people who aren't careful. It's darwinism in
software development.
	Linus Torvalds on the linux-kernel list


_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net