[Asterisk-Users] mpg123 or asterisk

[Diamon]

	I can't imagine why Gnu's assembler compiler wouldn't work for i586 
instructions, but does mpg123 perhaps need NASM instead?

	No guarantees, but I was toying with installing a CentOS 4.3 box today 
anyway, maybe I'll see if I can get it to compile for me and let you 
know if and how.  I don't have a dual-core Pentium, but in a Google 
search I found folks with this same behavior on Athlon, Opteron, P3 and 
P4 architectures, so I'm thinking it's some kind of missing 
package/dependency/library or similar.

	Diamon


Erick Perez wrote:
> If someone here happens to have a mpg123 binary compiled for Centos 43
> in a Pentium Dual Core, let me know.
> Somehow mpg123 cant compile.
> 
> [root at centos mpg123-0.59r]# make linux
> make CC=gcc LDFLAGS= \
>        OBJECTS='decode_i386.o dct64_i386.o decode_i586.o \
>                audio_oss.o term.o' \
>        CFLAGS='-DI386_ASSEM -DPENTIUM_OPT -DREAL_IS_FLOAT -DLINUX \
>                -DREAD_MMAP -DOSS -DTERM_CONTROL\
>                -Wall -O2 -m486 \
>                -fomit-frame-pointer -funroll-all-loops \
>                -finline-functions -ffast-math' \
>        mpg123-make
> make[1]: Entering directory `/root/sources/mpg123/mpg123-0.59r'
> make[2]: Entering directory `/root/sources/mpg123/mpg123-0.59r'
> as   -o decode_i586.o decode_i586.s
> decode_i586.s: Assembler messages:
> decode_i586.s:44: Error: suffix or operands invalid for `push'
> decode_i586.s:45: Error: suffix or operands invalid for `push'
> decode_i586.s:46: Error: suffix or operands invalid for `push'
> decode_i586.s:47: Error: suffix or operands invalid for `push'
> decode_i586.s:67: Error: suffix or operands invalid for `push'
> decode_i586.s:70: Error: suffix or operands invalid for `push'
> decode_i586.s:81: Error: suffix or operands invalid for `push'
> decode_i586.s:83: Error: suffix or operands invalid for `push'
> decode_i586.s:86: Error: suffix or operands invalid for `push'
> decode_i586.s:161: Error: suffix or operands invalid for `pop'
> decode_i586.s:211: Error: suffix or operands invalid for `pop'
> decode_i586.s:296: Error: suffix or operands invalid for `pop'
> decode_i586.s:315: Error: suffix or operands invalid for `pop'
> decode_i586.s:316: Error: suffix or operands invalid for `pop'
> decode_i586.s:317: Error: suffix or operands invalid for `pop'
> decode_i586.s:318: Error: suffix or operands invalid for `pop'
> make[2]: *** [decode_i586.o] Error 1
> make[2]: Leaving directory `/root/sources/mpg123/mpg123-0.59r'
> make[1]: *** [mpg123-make] Error 2
> make[1]: Leaving directory `/root/sources/mpg123/mpg123-0.59r'
> make: *** [linux] Error 2
> [root at centos mpg123-0.59r]#
> 
> On 5/27/06, Steve Totaro <stotaro at asteriskhelpdesk.com> wrote:
>> Please let us know your results.  I cannot really test this in
>> production system since it is a $16,000/hr call center.  I was using
>> madplay but it was crashing and creating zombie processes, I figured
>> native was not the way to go since all of the different audio streams.
>> Mpg123 works perfectly for me under a load of sixty channels, I can
>> confirm that for sure.
>>
>> Thanks,
>> Steve
>>
>> Erick Perez wrote:
>> > Interesting.
>> > So, i will have to test then...
>> >
>> >
>> > On 5/27/06, Steve Totaro <stotaro at asteriskhelpdesk.com> wrote:
>> >> In my very limited testing of native, each channel was receiving a
>> >> different stream (each caller heard something different).  Under a 
>> high
>> >> volume of calls, which is going to hurt performance more?  Transcoding
>> >> MP3s but sending a single stream or separate streams per call under
>> >> native?
>> >>
>> >> When I say high, I mean 1,000+ calls.
>> >>
>> >> Thanks,
>> >> Steve
>> >>
>> >>
>> >> Erick Perez wrote:
>> >> > Thanks to all. Native format will be.
>> >> >
>> >> > On 5/27/06, Matt Riddell (IT) <matt.riddell at sineapps.com> wrote:
>> >> >> Vahan Yerkanian wrote:
>> >> >> > Erick Perez wrote:
>> >> >> >> should I use mpg123 with asterisk 1.2.7 or should i use the 
>> native
>> >> >> >> player asterisk has?
>> >> >> >> the target machine will receive heavy load.
>> >> >> >
>> >> >> > mpg123 was used back when asterisk didn't have native format
>> >> >> support. If
>> >> >> > you are expecting heavy load, the native format is the way to
>> >> go. You
>> >> >> > might decide not to use mp3 format at all, recompressing your MoH
>> >> >> files
>> >> >> > using sox to the formats you gonna use, such as .al, .ul, 
>> .gsm, or
>> >> >> leave
>> >> >> > it at .sln to cut the decoding leg only.
>> >> >>
>> >> >> Heh, damn this GPRS connection.  In order to pass the time while
>> >> >> downloading messages I reply before they are all in, and yet by
>> >> the time
>> >> >> I have received all the messages I note that your question has
>> >> already
>> >> >> been answered!
>> >> >>
>> >> >> :)
>> >> >>
>> >> >> --
>> >> >> Cheers,
>> >> >>
>> >> >> Matt Riddell
>> >> >> _______________________________________________
>> >> >>
>> >> >> http://www.sineapps.com/news.php (Daily Asterisk News - html)
>> >> >> http://freevoip.gedameurope.com (Free Asterisk Voip Community)
>> >> >> http://www.sineapps.com/rssfeed.php (Daily Asterisk News - rss)
>> >> >> _______________________________________________
>> >> >> --Bandwidth and Colocation provided by Easynews.com --
>> >> >>
>> >> >> Asterisk-Users mailing list
>> >> >> To UNSUBSCRIBE or update options visit:
>> >> >>    http://lists.digium.com/mailman/listinfo/asterisk-users
>> >> >>
>> >> >
>> >> >
>> >>
>> >> _______________________________________________
>> >> --Bandwidth and Colocation provided by Easynews.com --
>> >>
>> >> Asterisk-Users mailing list
>> >> To UNSUBSCRIBE or update options visit:
>> >>    http://lists.digium.com/mailman/listinfo/asterisk-users
>> >>
>> >
>> >
>>
>> _______________________________________________
>> --Bandwidth and Colocation provided by Easynews.com --
>>
>> Asterisk-Users mailing list
>> To UNSUBSCRIBE or update options visit:
>>    http://lists.digium.com/mailman/listinfo/asterisk-users
>>
> 
>