Re: [SoX-users] SoX v14.0.0 WAV file issues...

[Michael C. <ch...@mc...>]

On Thursday 08 November 2007 8:04 pm, Daniel Taylor wrote:
> Chris Bagwell wrote:
> > That clearly shows that our new usage of fseeko() has problems.
> > I've done some searching on the internet and I'm not finding
> > any links that say fseeko() has been problematic on some
> > Distributions.  I'll keep looking though.
> >
> > Not sure what options we would have other then stop using fseeko.
> >
> > If you feel like testing this theory, you could edit the file
> > src/misc.c.  Look for any referenes to fseeko and replace with just
> > fseek().  Probably WAV files will work after that.
>
> Some thoughts, might help, might not:
>
> Taking a quick look, I note that fseeko()/ftello() is a part of the
> glibc package only since 2.1, current Slackware seems to be using
> glibc2.6 or 2.7. The initial error would seem to indicate a non-glibc
> <stdio.h> was being used on the target systems.
>
> Possibly the header files for the wrong libc are being accessed? That
> would explain both the initial compiler errors and the later execution
> inconsistencies.

This problem occurs on "Mandrake 9.2" but _not_ on "Mandriva 2007 Spring".

1) A diff on soxconfig.h only gives differences in "HAVE_*"s

2) stdio.h's are:
 5003 Aug 29  2003 /usr/include/bits/stdio.h
27777 Aug 29  2003 /usr/include/stdio.h
and
 5277 Mar  7  2007 /usr/include/bits/stdio.h
28559 Mar  7  2007 /usr/include/stdio.h

The five lines in each of the /usr/include/stdio.h's that contain "fseeko" 
are the same in both files

If version numbers of anything would be useful do say (along with suggestions 
of where to look for them ;-)>

Not sure if this helps ...

	Michael