Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
I just tried cross compiling firefly following the instructions on the wiki (both with and without flac / ogg-vorbis support). At this point, however, I'm stuck with unresolved symbols once I install the tarball on the DNS-323.
I'm not sure whether this is only the case with firefly - see my post http://dns323.kood.org/forum/t722-Firef … mbols.html .
At this point I have the suspicion that the toolchain might have changed, but then again, I might just be missing obvious steps. I'd really appreciate any pointers!
Last edited by ischg (2007-07-08 15:16:09)
Offline
ridewithstyle wrote:
has anybody found a solution to get flac going so far? I haven't had much luck in one yet. All I get is gargling sound in amarok and silence in itunes so far. The tracks show, without tags though
I just arrived at a similar point. I was able to compile firefly with flac support,, and all tracks show including tags. However, when firefly starts transcoding, flac complains about an illegal instruction.
I was able to isolate the problem by transcoding from the command line (ron from the firefly forum pointed me to this):
/mnt/HD_a2/shared/Mp3test # flac --silent --decode --stdout frog.flac Illegal instruction
I googled around and found that this usually happens when you run something on a CPU different than the one it was compiled/optimized for.
However, I don't know where to go from here. How can I get to more detailed information? I cross-compiled firefly using fonz's toolchain, so I'm not sure whether debugging symbols are of any help ... (i.e. I don't think I can debug on the DNS itself - right?)
I'm by no means a specialist in picking the right configuration flags, so it would be really awesome if anyone could give me feedback on my configuration ... for flac I used:
./configure --prefix=/opt/dns323/firefly/build/lnx_bin --host=arm-linux --with-ogg=/opt/dns323/firefly/build/lnx_bin LDFLAGS=-L/opt/dns323/firefly/build/lnx_bin/lib CPPFLAGS=-I/opt/dns323/firefly/build/lnx_bin/include CFLAGS=-Os -mtune=arm9e -march=armv5te
Firefly itself is compiled with Apskaft's configuration.
Thanks a lot!
Last edited by ischg (2007-07-11 18:42:56)
Offline
ischg wrote:
Code:
./configure --prefix=/opt/dns323/firefly/build/lnx_bin --host=arm-linux --with-ogg=/opt/dns323/firefly/build/lnx_bin LDFLAGS=-L/opt/dns323/firefly/build/lnx_bin/lib CPPFLAGS=-I/opt/dns323/firefly/build/lnx_bin/include CFLAGS=-Os -mtune=arm9e -march=armv5te
What happened to all the quotation marks and backslashes?
Try again without "-mtune=arm9e -march=armv5te" or try a more generic arch.
PS: And it should probably be "CFLAGS" instead of "CPPFLAGS" (or at least a CFLAGS with the same content?)
Last edited by fonz (2007-07-11 18:15:52)
Offline
fonz wrote:
What happened to all the quotation marks and backslashes?
... they're there - I just manually split a single line into multiple lines (and forgot to put in the backslashes)
fonz wrote:
Try again without "-mtune=arm9e -march=armv5te" or try a more generic arch.
Tried that - to no avail.
fonz wrote:
PS: And it should probably be "CFLAGS" instead of "CPPFLAGS" (or at least a CFLAGS with the same content?)
I never know where to put what. Aren't CFLAGS compiler flags and CPPFLAGS the C/C++ preprocessor flags?
One thing that's different for compiling flac (I'm using flac-1.1.4) is that I have to give a different host type (arm-linux-uclibc won't work). I dug around some and found that there's obviously a different config.sub file that uses a changed naming convention. Do I have to use arm-uclinux now?
BTW: keep up the great work! Your fun_plug (and other hints) has worked really great so far!
Offline
Ok, I did some more poking around.
The CPU has armv5te architecture with an arm926ej-s core. The GCC-3.3.3 used for cross-compilation doesn't support this CPU type directly, and perhaps issuing -mtune=arm9e causes some trouble.
As GCC-3.4 includes support, is there a way to build a cross-toolchain based on GCC-3.4??
Or, probably simpler: how do I specify a generic arm processor on the current toolchain?
Last edited by ischg (2007-07-11 21:26:43)
Offline
I just downgraded flac to 1.1.2 - and it worked! Flac is decoding happily using about 6% of CPU.
Obviously there was some change in both 1.1.3 and 1.1.4 that I'm unable to figure out. At this point I'm happy that I can listen to flac that's transcoded by the NAS. I'll add some instructions to the wiki later on ...
What's left to do now is to figure out how to build ivorbis-tools - the vorbis-tools package runs too slow to decode ogg files in real-time.
Offline