#7 ultrastar-ng does not start at all.
hello!
when i launch ultrastarng i get, as soon as a black window appears, hte message "illegal instruction" on the terminal and it quits.
gdb says only :
Program received signal SIGILL, Illegal instruction.
0x00002ba9f2e47faa in ?? () from /usr/lib/libfftw3f.so.3
and the backtrace is :
#0 0x00002ba9f2e47faa in ?? () from /usr/lib/libfftw3f.so.3
#1 0x00002ba9f2d96392 in ?? () from /usr/lib/libfftw3f.so.3
#2 0x00002ba9f2d929a3 in fftwf_measure_execution_time ()
from /usr/lib/libfftw3f.so.3
#3 0x00002ba9f2d8fa3b in ?? () from /usr/lib/libfftw3f.so.3
#4 0x00002ba9f2d8ffde in ?? () from /usr/lib/libfftw3f.so.3
#5 0x00002ba9f2d8ea87 in fftwf_mkplan_d () from /usr/lib/libfftw3f.so.3
#6 0x00002ba9f2dcf972 in ?? () from /usr/lib/libfftw3f.so.3
#7 0x00002ba9f2d8f90e in ?? () from /usr/lib/libfftw3f.so.3
#8 0x00002ba9f2d8ffde in ?? () from /usr/lib/libfftw3f.so.3
#9 0x00002ba9f2e1a1f4 in ?? () from /usr/lib/libfftw3f.so.3
#10 0x00002ba9f2e1a40c in fftwf_mkapiplan () from /usr/lib/libfftw3f.so.3
#11 0x00002ba9f2e1da5b in fftwf_plan_many_dft_r2c ()
from /usr/lib/libfftw3f.so.3
#12 0x00002ba9f2e1ce54 in fftwf_plan_dft_r2c () from /usr/lib/libfftw3f.so.3
#13 0x00002ba9f2e1cdb3 in fftwf_plan_dft_r2c_1d () from /usr/lib/libfftw3f.so.3
#14 0x00000000004063f0 in ?? ()
#15 0x0000000000406498 in ?? ()
#16 0x0000000000404ec1 in ?? ()
#17 0x0000003d6be1d374 in __libc_start_main () from /lib/libc.so.6
#18 0x0000000000404899 in ?? ()
#19 0x00007fffb7d72708 in ?? ()
#20 0x0000000000000000 in ?? ()
I have recompiled fftw (from sci-libs/fftw-3.1.2 USE="sse sse2 (-altivec) -test") just in case but the problem is the same. I have tried versions 1.2, 1.3 and from cvs.
I use gentoo and compiled it with flags :
USE="gstreamer opengl xine -deprecated_cairo_svg -novideo"
the main charateristics of my system are :
Portage 2.1.2.2 (default-linux/amd64/dev/2007.0, gcc-4.1.2, glibc-2.5-r1, 2.6.20-gentoo-r2 x86_64)
=================================================================
System uname: 2.6.20-gentoo-r2 x86_64 AMD Athlon(tm) 64 Processor 3500+
Gentoo Base System version 1.12.9
Timestamp of tree: Wed, 21 Mar 2007 08:20:01 +0000
ccache version 2.4 [enabled]
dev-java/java-config: 1.3.7, 2.0.31-r5
dev-lang/python: 2.3.6, 2.4.4
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache: 2.4-r6
sys-apps/sandbox: 1.2.18.1
sys-devel/autoconf: 2.13, 2.61
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils: 2.17
sys-devel/gcc-config: 1.3.15-r1
sys-devel/libtool: 1.5.23b
virtual/os-headers: 2.6.20-r2
ACCEPT_KEYWORDS="amd64 ~amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-mtune=athlon64 -march=athlon64 -O3 -pipe -msse3"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/php/apache1-php5/ext-active/ /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/splash /etc/terminfo"
CXXFLAGS="-mtune=athlon64 -march=athlon64 -O3 -pipe -msse3"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig candy ccache distlocks metadata-transfer parallel-fetch sandbox sfperms"
GENTOO_MIRRORS="ftp://mirror.ovh.net/gentoo-distfiles/ http://gentoo.modulix.net/gentoo/ ftp://ftp.belnet.be/miror/rsync.gentoo.org/gentoo/ http://gentoo.osuosl.org http://gentoo.modulix.net/gentoo/"
LANG="fr_FR.UTF-8"
LC_ALL="fr_FR.UTF-8"
LDFLAGS="-Wl,-O1 -Wl,--enable-new-dtags -Wl,--sort-common -s -Wl,-z,now"
LINGUAS="fr_FR en_GB fr en"
MAKEOPTS="-j2"
what do you think about this ?
thank you
brice b.
Logged In: YES
user_id=1319653
Originator: NO
Hi,
This seems to be a gentoo or fftw problem. Possible fixe could be to lower your CFLAGS CXXFLAGS and LDFLAGS.
Also have you recompile your whole system when upgrading to >=gcc-4 and glibc-2.5 ?
Vincent
Logged In: YES
user_id=1417745
Originator: YES
yes, sorry, it was a cflag/ldflag problem from fftw, i recompiled it with common cflags and empty ldflags. Now ultrastar-ng starts well. one problem now is that most *.txt «lyrics» files "cannot be opened" (and this is not a permission problem)
thanks
Logged In: YES
user_id=1319653
Originator: NO
The txt files should have the same name as the directory where it belongs (example in the directory "My Artist - My song" the txt file should be named "My Artist - My song.txt".
Could you confirm that it is your bug so I could close this one :)
Logged In: YES
user_id=1417745
Originator: YES
Ok, now everything works, thank you very much :-)
By the way, a wish for a next release would be :
when you have a "Something" directory and inside a "something resembling.txt" saying it is the txt for the "song.mp3" which is next to it, since ultrastar looks for Something.txt and fails to open it, couldn't it then look for another (and only) existing .txt inside the directory and look if there is a #MP3:song.mp3 in its header ?
(Besides, ultrastar does not search recursively in the "songs" directory.)
thanks for your help !!
Logged In: YES
user_id=1319653
Originator: NO
Oki thanks for feedbacking.
.txt issue has been discussed