Re: [gentoo-user] shoutcast problem 64bit gentoo
Saphirus Sage wrote: > Have you emerged emul-linux-x86-baselibs or other precompiled 32-bit > libraries? > > YES: * app-emulation/emul-linux-x86-baselibs Latest version available: 20080316 Latest version installed: 20080316 app-emulation/emul-linux-x86-compat Latest version available: 20071125-r1 Latest version installed: 20071125-r1 app-emulation/emul-linux-x86-glibc-errno-compat Latest version available: 2.5 Latest version installed: 2.5 other emul-linux..libs are masked... w.d.
Re: [gentoo-user] shoutcast problem 64bit gentoo
Arttu V. wrote: > On 1/23/09, Xav' wrote: >> This is a joke, isn't it ??? the error message coming from rc script is a >> bit clear IMHO... > > Well, the error message is clear and that listing from someone's home > directory has me really puzzled -- what's the connection, why present > it? It's not a joke. I'm really not that fresh about installing gentoo and shoutcast. I've got two production servers (using 32 bit architecture) and this is my first 64 bit gentoo instalation. This error is really not caused by a missing sc_serv file When using debian, the solution is to install ia-32libs and when using gentoo it simply doesn't work for me. That's why I ask here. Wojtek
[gentoo-user] shoutcast problem 64bit gentoo
Hi,
I've just installed 64bit gentoo on one of these machines:
http://www.ovh.pl/produkty/eg_best_of.xml
Everything seens to be fine. I use hardened profile but I've got problem
with ...running a shoutcast server.
I didn't find answer on winamp.com forum and google.
It's exactly the same problem like here:
http://forums.winamp.com/printthread.php?s=48cd69919741579a3c1e4a8b0ac3e38b&threadid=229419
At my server it fails this way:
gentoo shoutcast # pwd
/home/something/shoutcast
gentoo shoutcast # file *
logs: directory
sc_serv: ELF 32-bit LSB executable, Intel 80386, version 1
(SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), stripped
sc_serv8002.conf: ASCII English text, with CRLF, LF line terminators
gentoo shoutcast # strace ./sc_serv
execve("./sc_serv", ["./sc_serv"], [/* 26 vars */]) = -1 ENOENT (No such
file or directory)
dup(2) = 3
fcntl(3, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
fstat(3, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x708341026000
lseek(3, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(3, "strace: exec: No such file or dir"..., 40strace: exec: No such
file or directory
) = 40
close(3)= 0
munmap(0x708341026000, 4096)= 0
exit_group(1) = ?
gentoo shoutcast # /etc/init.d/shoutcast start
* Starting Shoutcast Server ...[ ok ]
gentoo shoutcast # /sbin/start-stop-daemon: Unable to start
/opt/shoutcast/sc_serv: No such file or directory (No such file or
directory)
The problem is that shoutcast is 32 bit and system is 64 bit (and I
think it should be 64 @ this machine).
I've tried to follow these tips from the forum but it didn't help me.
Can you help me?
Wojtek
[gentoo-user] shoutcast problem 64bit gentoo
Hi,
I've just installed 64bit gentoo on one of these machines:
http://www.ovh.pl/produkty/eg_best_of.xml
Everything is fine. I use hardened profile, Pax, firewall ect, but I've
got problem with ...running a shoutcast server.
I didn't find answer on winamp.com forum and google.
It's exactly the same problem like here:
http://forums.winamp.com/printthread.php?s=48cd69919741579a3c1e4a8b0ac3e38b&threadid=229419
At my server it goes this way:
gentoo shoutcast # pwd
/home/something/shoutcast
gentoo shoutcast # file *
logs: directory
sc_serv: ELF 32-bit LSB executable, Intel 80386, version 1
(SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), stripped
sc_serv8002.conf: ASCII English text, with CRLF, LF line terminators
gentoo shoutcast # strace ./sc_serv
execve("./sc_serv", ["./sc_serv"], [/* 26 vars */]) = -1 ENOENT (No such
file or directory)
dup(2) = 3
fcntl(3, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
fstat(3, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x708341026000
lseek(3, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(3, "strace: exec: No such file or dir"..., 40strace: exec: No such
file or directory
) = 40
close(3)= 0
munmap(0x708341026000, 4096)= 0
exit_group(1) = ?
gentoo shoutcast # /etc/init.d/shoutcast start
* Starting Shoutcast Server ...
[ ok ]
gentoo shoutcast # /sbin/start-stop-daemon: Unable to start
/opt/shoutcast/sc_serv: No such file or directory (No such file or
directory)
The problem is that shoutcast is 32 bit and system is 64 bit (and I
think it should be 64 @ this machine).
I've tried to follow these tips from the forum but it didn't help me.
Can you help me?
Wojtek
Re: [gentoo-user] Avahi Keeps failing on Emerge - Maybe a Python Error?
Alan McKinnon wrote: On Sunday 18 January 2009 06:38:15 Richard Watson wrote: I'm sorry about the delay in closing this. I finally figured out if I remove "-pipe" from my /etc/make.conf CFLAGS that all my compile errors go away. Looking at the reference on the subject this option tells GCC not to create temporary files when compiling but to turn this off if low on RAM. Not sure why this happens as I have a 1GB Ram. Maybe this is not enough these days. Anyway problem solved. That's an interesting result, but I can't help thinking it's the wrong solution to the wrong problem. One of my machines has had merely 1G for 2 years, before that it had 512M for 3 years and it has never shown this symptom. I have servers at work with 512M - same thing, even when building current packages. Gut feel is telling me that removing -pipe is simply revealing a deeper symptom somewhere - 1G is actually an enormous amount of memory for compilation purposes. If you feel like digging deeper, I'd be very interested to see where this one leads. I would like to write my first post here just to inform you that I also had this problem with avahi and pygtk. Avahi failed to emerge and I had to remove pygtk from my use flags, than it compiled OK. I was just interested if removing "-pipe" from CFLAGS makes any difference, and I tried remove it and emerge avahi with pygtk, but it does not compile. For me it compiles only without pygtk and changing -pipe doesn't work at all. I checked this because I have 512M. I don't know why I might need avahi with pygtk...disabling pygtk use flag for avahi works fine and other packages compile well. Wojtek
