SliTaz Forum
You are not logged in.
... hang-up on boot:
/etc/init.d/rcS: line 9: can't open /usr/bin/gettext.sh
... because gettext.sh doesn't exist. I also noticed that the 'rolling' ISO is still significantly larger than the 'rolling-core' ISO. They used to be similar if not identical in size.
Offline
P.S.:
Is there a place on the Mirror where I can still find the slitaz-rolling ISO from late October? This was the last ISO that worked flawlessly for me. Ever since the 01.Nov and 08.Nov. ISOs came out I cannot compile any more because I get strange error messages from config that I've seen never before ...
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for GTK... no
checking for GTK... no
checking for GTK... no
configure: error: Package requirements (gtk+-2.0 >= 2.18.0 gthread-2.0 gobject-2.0) were not met:
Package 'zlib', required by 'freetype2', not found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables GTK_CFLAGS
and GTK_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
Offline
> gettext.sh doesn't exist
since tazpkg-862...
> checking for GTK... no
> Package 'zlib', required by 'freetype2', not found
Did you tried:
[c]tazpkg -gi gtk+-dev --forced[/c]
[c]tazpkg -gi zlib-dev --forced[/c]
?
> Is there a place on the Mirror where I can still find the slitaz-rolling ISO from late October?
I found only older slitaz-rolling-loram.iso 2015-Sep-20 11:17:41
Offline
works for me, booting into "slitaz-rolling-core.iso":
1. did you check if your download is correct ? e.g. compare md5sum
mine has: 8f3237d32f3d5bd7fde649c79daba23d slitaz-rolling-core.iso
2. if same: can you describe your system more?
3. I will try also the other 2 isos (core64, normal rolling)
Offline
I can also boot into these (e.g. desktop loads fine):
dffee362f5f3be50cfb8738bae419273 slitaz-rolling.iso
c96f76d8f5e97e4804348def1e8aa7ed slitaz-rolling-core64.iso
though, the core64 had some gui artefact on the top bar
Offline
@Erkan_Yilmaz
You are using old ISO from unsynced mirror.
build with tazpkg-861
[c]slitaz-rolling.iso 2015-Nov-16 01:13:57 59.0M[/c]
[c]slitaz-rolling-core.iso 2015-Nov-16 01:22:55 42.0M[/c]
build with tazpkg-862 in a ~ 1-and-half hour
[c]slitaz-rolling.iso 2015-Nov-16 02:50:34 48.0M[/c]
[c]slitaz-rolling-core.iso 2015-Nov-16 02:57:23 38.0M[/c]
with missing depends
Offline
Right. Sorry for confusion :-(
(Since they had also today's date, I gave it a try)
Offline
Thanks for your replies, guys.
> gettext.sh doesn't exist since tazpkg-862...
... ahh! So, why is /etc/init.d/rcS still calling the script from line 9 and, stranger still, why doesn't rcS in the repo contain this line?
ftp://cook.slitaz.org/slitaz-boot-scripts/taz/slitaz-boot-scripts-415/fs/etc/init.d/rcS
I wonder what is the basis of these latest ISOs ?
> Did you tried:
> tazpkg -gi gtk+-dev
> tazpkg -gi zlib-dev
... that bit of my SpaceFM build script looks like this:
# install dev environment
n | tazpkg -gi bash
tazpkg -gi zlib
tazpkg -gi gtk+-dev
tazpkg -gi udev-dev
tazpkg -gi intltool
tazpkg -gi slitaz-toolchain
... and indeed, zlib-dev is missing. But as I have never seen this error msg before and since github-master hasn't changed for over a month, some change in recent SliTaz rolling releases must have triggered it. Anyways ... I will include zlib-dev and try out again as soon as I can get a working rolling ISO.
> I found only older slitaz-rolling-loram.iso 2015-Sep-20 11:17:41
... shame, the standard rolling from late October is no longer available. But I have learned from this experience. In the future I will maintain my own little repository of 2-3 rolling ISOs that actually do work.
> 1. did you check if your download is correct ? e.g. compare md5sum
> mine has: 8f3237d32f3d5bd7fde649c79daba23d slitaz-rolling-core.iso
... I did check and it was ok. But from your md5 I can see that we're not talking about the same rolling release as the check sums of the current release (2015-Nov-16) are:
a8d4bf00f5c2f6f95739b569b1a42758 slitaz-rolling.iso
15fe7632381fcfe4aa9d3f7dce4499ed slitaz-rolling-core.iso
Offline
> slitaz-rolling ISO from late October?
> This was the last ISO that worked flawlessly for me.
> Ever since the 01.Nov and 08.Nov. ISOs came out I cannot compile
There was no any updates at this period, that can brake compilation.
Ok, maybe something about tazpkg with bash installed.
> that bit of my SpaceFM build script looks like this
Is THIS ever worked? Try reverse order.
slitaz-toolchain should be first, look at /etc/slitaz/cook.conf bash should be last.
[c]tazpkg -gi zlib[/c] - useless iten, you already have zlib installed, it's impossible to boot without zlib.
Offline
> Is THIS ever worked? Try reverse order.
You're soo right, az_ua! Strangely, the script worked perfectly for quite some time, since SpaceFM 1.0.1 I think it was. But, as I was not replacing Busybox /bin/sh with Bash, does it actually matter? Still, I'm going to install Bash last and the toolchain first. I will also include zlib-dev although the Guru no longer mentions it as a requirement in his latest Readme ...
https://raw.githubusercontent.com/IgnorantGuru/spacefm/next/README
But the main issue for me is to get hold of a rolling release that works. I'm also wondering what went wrong with the current rolling?
Offline
> https://raw.githubusercontent.com/IgnorantGuru/spacefm/next/README
So, you tried to build spacefm-next using script. It's "next", every time your script downloads DIFFERENT sources archive, if there was commit in github repo. I'm 100% sure, you'll get same errors in ANY iso because "Guru" breaks something here: https://github.com/IgnorantGuru/spacefm/commits/next
You can try this one: http://people.slitaz.org/~az_ua/slitaz-rolling.iso
Build date: 2015-Oct-04
Or you can run old RC3, install http://people.slitaz.org/~az_ua/tazlito-390.tazpkg
And build latest rolling ISO by tazlito-wiz.
Offline
Hi there,
For all, I uploaded to the mirror server all the ISO dated November 8, 2015.
Files are available for downloading right now: http://mirror1.slitaz.org/iso/rolling/
Please be patient and constructive.
Offline
> So, you tried to build spacefm-next using script. It's "next", every time your
> script downloads DIFFERENT sources archive, if there was commit in github repo.
You are right, most of the time I actually did use "next" and it has been working well since ... dunno ... sometime in spring this year, maybe March/April. But in order to test the 01.Nov and 08.Nov rolling releases I have always used SpaceFM "master" because this has been unchanged for over one month. And since you don't seem to believe me, here's how the script begins ...
[c]#!/bin/sh
#
if [ "$(whoami)" != "root" ]; then
echo "You must be root!"
echo ""
exit 1
fi
if [ $# -eq 0 ]; then
echo "Enter either 'next' or 'master' ..."
echo ""
exit 1
elif [ "$1" != "next" ] && [ "$1" != "master" ]; then
echo "Enter either 'next' or 'master' ..."
echo ""
exit 1
fi
# --- download, build and install spacefm --------------------------------------------------
rm -fr /tmp/spacefm-build
mkdir /tmp/spacefm-build
cd /tmp/spacefm-build
wget https://github.com/IgnorantGuru/spacefm/archive/$1.zip --no-check-certificate
if [ ! -f /tmp/spacefm-build/$1.zip ]; then
echo "Can't download $1.zip... ERROR"
exit 1
fi
# install dev environment
cd /
tazpkg -gi slitaz-toolchain
tazpkg -gi intltool
tazpkg -gi gtk+-dev
tazpkg -gi udev-dev
tazpkg -gi zlib-dev
n | tazpkg -gi bash
etc. etc. etc. ...[/c]
... maybe not very elegant, but it worked well with all pre- 01.Nov./08.Nov. rolling releases.
> You can try this one: http://people.slitaz.org/~az_ua/slitaz-rolling.iso
> Build date: 2015-Oct-04
... I did try your ISO. It's got:
- tazlito VERSION=386 (17.09.2015)
- tazpanel VERSION=529 (17.09.2015)
For some reason it didn't have openssl installed, which is needed to run wget https, even if the '--no-check-certificate' parameter is passed. But once I had installed openssl and ran my script ... WOAH! YEAH! ... it worked, as it had been working before the 01.Nov./08.Nov. rolling releases spoiled it for me. Great! And in case you still don't believe me, I can post the log file. But it's rather long and probably not a good idea.
So where do we go from here? Is it possible for one of the specialists here to figure out which change in the 01.Nov. rolling release prevents me from compiling SpaceFM?
P.S.:
Sometimes (not always!) I'm an imbecile. I just noticed that when I was using your ISO I wrote down the version number of tazpanel instead of the much more relevant tazpkg. Hmm ...
Offline
I've just compiled SpaceFM again with my script, this time from the ISO that Aleksej has uploaded last night. It worked. Thanks a lot for your help, Alexander and Aleksey!
Offline
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.57 MiB (Peak: 1.77 MiB) ]