SliTaz Forum
You are not logged in.
Pages: 1
Greetings all. I have been trying to get a live USB to boot on my HP laptop, without success.
I believe it is due to the U3 firmware embedded in Sandisk USB sticks, so I downloaded the u3-tool from Sourceforge, which removes the offending U3 firmware.
The problem is, when I cd to /home/tux/Desktop/u3-tool-0.3 and run ./configure, xterm returns an
error message, citing "no acceptable C compiler found in $PATH"
So I figure, no problem, just get-install the gcc package from the Tazpkg repository. Everything
seems to run just fine in xterm - no errors - ends the install with " gcc (4.5.2) is installed "
Now, how do I get u3-tool, which resides in /home/tux/Desktop, to recognize that gcc IS in fact
installed? Because it continues to insist "no acceptable C compiler" can be found. In fact,
(and I'm sure I'm missing something pretty basic here) I have been unable to get ANY new package
to properly install. I get a spinning curser, as if the program is installing...then...nothing.
What am I doing wrong?
EBL
ADDENDUM: and yes, I'm logging into xterm with root priveleges before performing the installs...
Offline
Hmmm, seems you're missing several things. First try installing the slitaz-toolchain package. It comes with most things you'll need to compile something that runs on the command line (while slitaz-dev-pkgs comes with most of the packages you'll need to compile for a graphical enviroment). Then it seems you need libusb's dev package, so install libusb-dev to get that.
Then it should simply be:
./configure --prefix=/usr
make
and make install as root.
I just compiled it to check myself and it worked.
Offline
Awesome - thank you, Trixar_za. I'll give that a shot momentarily.
Appreciate the help.
EBL
Offline
well, something is definitely not right. Installed everything you mentioned - which went without
a hitch - but still can't get past ./configure without the error "no acceptable C compiler found
in $PATH"
guess it's keep on trouble-shooting :\
But thank you again for the help.
Offline
Does it matter where I'm installing u3-tools from? That is, I dowloaded the package from
Sourceforge directly to my Desktop. Does it need to be placed in a different directory, or...?
Offline
Well, mine was downloaded to my Downloads directory, which is were I uncompressed and compiled it. You could probably try using tazpkg get-install gcc --forced and tazpkg get-install gcc-lib-base --forced to reinstall gcc. Maybe it helps.
Offline
Hi,
No when you download a source package you can keep it where you want to build it. That said you must have something missing because I just compiled u3-tool succefully. 2 way to go now:
1. What slitaz version do you use ? If cooking, let me 15 min and I do a package for you.
2 Past here the detailled error and we will tell you what missing packages you need
Offline
Looks like SliTaz Cooking because he has a newer version of GCC installed than me (I'm on Stable)
Offline
@ pansko - actually I'm using an older version, as I burned this SliTaz CD a while ago.
It's v2.6.29.3 (when it was still a "cooking" version....)
Offline
This next question is going to expose my inexperience with Linux, so please be kind 
Okay... I'm running SliTaz from a read-only CD. Everything loads into RAM, and runs from there.
I can download a new package & all necessary dependencies - I just can't get them up & running.
My assumption was newly installed packages, or even upgrades to existing packages, would also
load into RAM and run from there. Am I completely off-base in thinking this?
(I've installed packages using TazPkg, and xterm has indicated the installations were successful.
So how do I get them to run?)
EBL
Offline
I think I see the problem now.
You're using an older SliTaz 2's cooking copy and you're installing the current most packages that was made for the latest cooking. This is probably why things aren't work since the time difference between the two is over 2 years now.
Maybe try getting the SliTaz 2 packages @ http://pkgs.slitaz.org and installing them with tazpkg install ?
Offline
Pages: 1
[ Generated in 0.015 seconds, 10 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]