Re: [SoX-users] building sox 14.3.1 from source on ubuntu jaunty

[Chris B. <ch...@cn...>]

On Tue, May 25, 2010 at 6:08 PM, Arturo Rinaldi <art...@gm...> wrote:

>  Il 25/05/2010 20:30, Chris Bagwell ha scritto:
>
>
>
> On Tue, May 25, 2010 at 1:17 PM, Pascal Giard <evi...@gm...> wrote:
>
>> On Tue, May 25, 2010 at 1:50 PM, Arturo Rinaldi <art...@gm...>
>> wrote:
>> > i'm trying to build sox 14.3.1 from source on ubuntu jaunty 9.04 but i
>> get
>> > this error in the "make"
>> >
>> > mp3.c: In function ‘startwrite’:
>> > mp3.c:740: error: ‘id3tag_set_pad’ undeclared (first use in this
>> function)
>> > mp3.c:740: error: (Each undeclared identifier is reported only once
>> > mp3.c:740: error: for each function it appears in.)
>> > make[1]: *** [libsox_la-mp3.lo] Errore 1
>> > make[1]: uscita dalla directory «/home/artynet/Scrivania/sox-14.3.1/src»
>> > make: *** [all-recursive] Errore 1
>> >
>> > i satisfied all the dependencies by
>> >
>> > sudo apt-get build-dep sox
>> >
>> > and the ./configure goes smoothly
>>  [...]
>>
>> Hmm... that's weird... I didn't have any issue building SoX myself nor
>> did Debian's buildd [1] or even Ubuntu's maverick [2]...
>>
>> I doubt it's a cpu architecture issue as all of them are supported (13
>> Linux, 1 hurd, 2 kFreeBSD) besides m68k, powerpcspe and sparc64.
>> (By forcing me to have a look at the buildd logs, you made me realize
>> that i should disable libltdl for powerpcspe but that's off topic).
>>
>>
> Can you let me know what version of lame you have installed?  Your hitting
> a part of the code were it attempts to handle id3tag_set_pad being an
> optional symbol but seems not working on your system correctly.
>
> Perhaps the background on Pascal saying disabling litltdl is related to
> this topic?  Is something special about powerpcspe and dynamic linking?
>
> Chris
>
>
> ------------------------------------------------------------------------------
>
>
>
>
> _______________________________________________
> Sox-users mailing lis...@li...://lists.sourceforge.net/lists/listinfo/sox-users
>
>  my lame version is 3.98. *libmp3lame0* and *libmp3lame-dev* version 3.98
> . My architecture is a standard i386. The build process was successful
> without any problems on karmic and lucid !  !  ! I don't explain to myself
> why it isn't so on jaunty.....
>
> i attach my build log
>
> http://www.box.net/shared/4k4lcripsg
>
> thx in advance....:D
>
>
I don't know how to decode debian/ubuntu release names but its probably
jaunty is an older release and has lame 3.98 and the others 3.98.1?  3.98.1
contains the symbol thats giving you errors... but SoX is supposed to handle
this gracefully.

Or perhaps jaunty is more strict  on linking to unresolved symbols.  Just
wild guesses.

Could you also send me your config.log and your src/soxconfig.h that was
generated from running configure on the platform failing?  Thats probably
enough to tell me what the bug is.

Thanks,
Chris