Tiny Core Linux
Tiny Core Extensions => TCE Talk => Topic started by: Scampada on July 04, 2016, 05:51:20 PM
-
Hi,
I've lost my brain (that part of it that was still there after Coca-Cola and shooter games) while trying to build this wannabe-cool stuff:
https://github.com/karlstav/cava
Got some kind of errors in the automake step, then did some dirty magic and it worked but then my Perl refused to find its strict.pl (when it was in its place).
I gave up (at least for time). Maybe there will appear a good person that would build it in his not-so-crappy environment, or, applying his not-so-clumsy hands, and commit the resulting .tcz?
I hate these auto-don't-know-what things, why don't people provide their sources with pre-built configure scripts and all?
-
Your problem was perhaps this:
cp: invalid option -- 'n'
BusyBox v1.24.2 (2016-05-16 13:28:30 UTC) multi-call binary.
..which can be cured by using the coreutils extension.
The configure script is generated without errors using this: $ tce-load -i compiletc git automake libtool-dev gettext-dev intltool coreutils
$ git clone https://github.com/karlstav/cava
$ cd cava
$ ./autogen.sh
-
I'm using coreutils, maybe the path variable does the dirty trick. What if I try to remove /usr/bin: before configuring...
-
I didn't touch $PATH and /usr/local/bin is before /bin in $PATH anyway.
You could remove the /bin/cp -> /bin/busybox symlink, but that shouldn't be needed.
-
Ah yes. There it is what it looks like. Hmm... it's a generic Linux issue I guess...) ??? Googling around...
(https://pp.vk.me/c630824/v630824354/37d82/Q8HGmBaNQTU.jpg)
PS Is there some kind of [spoiler] \ [more] tag?
[spoiler]test[/spoiler]
[more]test[/more]
UPD: uhm... I've been messing around with my $PATH... But yes, /local goes first.
-
Did you load all of the extensions I mentioned in the previous post (libtool.m4 is in libtool-dev)?
-
Yep, I forgot the dev package. Now it's processing... something..., it's way better, not regarding to results.
-
Made it. Thank you very much.