Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 210873 - media-sound/gogo-3.10-r1: cannot compile code by required nasm
Summary: media-sound/gogo-3.10-r1: cannot compile code by required nasm
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Sound Team
URL:
Whiteboard: Pending removal: When dev-lang/nasm-2...
Keywords: PMASKED
Depends on:
Blocks:
 
Reported: 2008-02-20 12:41 UTC by Martin Mokrejš
Modified: 2008-10-09 20:23 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Mokrejš 2008-02-20 12:41:20 UTC
>>> Compiling source in /var/tmp/portage/media-sound/gogo-3.10-r1/work/petit310pl3 ...
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --enable-shared --enable-nasm --enable-extopt=full --without-vorbis --enable-debug=no --build=i686-pc-linux-gnu
creating cache ./config.cache
checking for gcc... gcc
checking whether the C compiler (gcc -O2 -march=pentium4 -mmmx -msse -msse2 -fomit-frame-pointer -pipe ) works... yes
checking whether the C compiler (gcc -O2 -march=pentium4 -mmmx -msse -msse2 -fomit-frame-pointer -pipe ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for nasm... nasm
[cut]
nasm -i./engine/i386/ -f elf -D__unix__  engine/i386/fftsse.nas -o fftsse.o
engine/i386/fftsse.nas:23: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:23: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:23: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:23: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:24: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:24: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:24: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:24: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:25: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:25: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:25: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:25: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:26: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:26: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:26: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:26: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:27: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:27: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:27: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:27: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:28: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:28: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:28: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:28: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:29: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:29: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:29: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:29: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:30: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:30: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:30: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:30: error: invalid character in floating-point constant exponent: 'F'
engine/i386/fftsse.nas:562: warning: label alone on a line without a colon might be in error
make: *** [fftsse.o] Error 1
 * 
 * ERROR: media-sound/gogo-3.10-r1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2030:  Called die
# nasm -v
NASM version 2.01 compiled on Jan 22 2008
#
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2008-02-20 13:02:23 UTC
Wonderful, broken, homepage redirecting to some Japanese junk, hasn't seen a new version since 2002. Similar cruft in the tree plain sucks, please remove this.
Comment 2 Samuli Suominen (RETIRED) gentoo-dev 2008-07-05 09:06:20 UTC
someone with x86, please verify it cannot be built anymore

treecleaners (or sound) can mask it if so, seems rather useless because we have *lame*
Comment 3 Samuli Suominen (RETIRED) gentoo-dev 2008-07-05 09:08:18 UTC
ah well.. I guess one of the treeclaners has x86
Comment 4 Hans de Graaff gentoo-dev Security 2008-07-06 06:04:47 UTC
media-sound/gogo-3.10-r1 compiles fine for me on stable x86 (with nasm0.98.39-r3).

The bug report mentions nasm 2.0, so perhaps that is the cause of the problem (but that is still marked ~x86).
Comment 5 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2008-07-06 18:13:30 UTC
(In reply to comment #4)
> The bug report mentions nasm 2.0, so perhaps that is the cause of the problem
> (but that is still marked ~x86).

Confirmed. When nasm goes stable, this package should probably be masked/removed.
Comment 6 Mr. Bones. (RETIRED) gentoo-dev 2008-08-31 05:13:44 UTC
Well, I want to get nasm-2 stable so I masked media-sound/gogo for removal.
Comment 7 bluescream 2008-09-04 21:51:20 UTC
Sorry to read that gogo is removed because of nasm-2.
gogo has a main advantage against lame and twolame: that's speed and speed!

Just made a simple test with a wav-file of 64MB (6:18 min) and encoding with 192kb:

time | command
12s  | twolame -b 192 cdda.wav lame.mp3
4.5s | gogo -b 192 cdda.wav gogo.mp3
31s  | lame -b 192 cdda.wav lame.mp3

Filesizes:
9067610 2lame.mp3
9081835 gogo.mp3
9083088 lame.mp3

The sound quality is equivalent between all three encoders. But the speed of gogo is incredible!

Regarding the homepage:
I have to admit, that I don't know (or remember) what was on the homepage which is mentioned in the ebuild, but if you check gogo's help message you'll find a different homepage:

http://homepage1.nifty.com/herumi/gogo_e.html

There you'll find a link to 

http://homepage2.nifty.com/kei-i/
Comment 8 bluescream 2008-09-04 22:20:59 UTC
Well, I think, never mind...

I tested some encodings with lower bitrates (64k) and unfortunately (but as expected) the best quality was now when using lame...
I think I will get used to encode with lame ;)

Thanks for reading and sorry for bothering.

Comment 9 Mr. Bones. (RETIRED) gentoo-dev 2008-10-09 20:23:21 UTC
media-sound/gogo was removed.