I was looking to try out samba for a slackware installation I have. The latest binaries I have seen for Slackware... http://us1.samba.org/samba/ftp/Binary_Packages/Slackware/ samba-1.9.18p8-Slackware3.4.tgz ... seemed to me to be corrupt. I tried all 3 us mirrors and got the same result when doing a tar xvzf samba-1.9.18p8-Slackware3.4.tgz gzip: stdin: invalid compressed data--format violated tar: Child returned status 1 tar: Error exit delayed from previous errors I am either blowing it pulling it down, or the mirror is bad. I am more likely to belive I am blowing it, but wonder if anyone has checked it? It's an older build and not samba 2.0.2 anyway... so I didn't know if there really is a problem or not. -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ -+-+ Some stats... uname -a Linux testm1 2.2.1 #15 Fri Feb 12 12:16:58 EST 1999 i586 unknown gcc --version 2.7.2.3 My libs scare me and I am not sure what you might want from there... -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ -+-+ Here's my problem when I build samba 2.0.2 I do a configure and that seems to go ok. I do a make and it sits for a while and then I get a Compiling passdb/passdb.c gcc: Internal compiler error: program cc1 got fatal signal 6 make: *** [passdb/passdb.o] Error 1 If I delete 90% of it and leave just the headers and re-compile to find if there are any other problems, the next hold up seems to be with.. gcc: Internal compiler error: program cc1 got fatal signal 6 make: *** [lib/util_str.o] Error 1 If I back it up and delete 90% of it (leaving header and maybe the first function) then I think I am just getting link errors when everything gets linked. ---------------------------- I have been looking at the DIGESTS and the closet comment I saw was a mention of a sig11 faq. I read it, and while it said that memory sometimes will cause a signal 6 error, I just don't see how I could cleanly compile my 2.2.1 kernel and suddenly develope problems with samba 2.0.2. (I remain open minded though) My early thoughts would be to track the source carefully and see if like some macro was blowing up somewhere. But, yea, I am lazy, and thought I would ask the SAMBA body if there was a 2.0.2 slackware binary, and or (preferably) if anyone else had seen something like this. Would Really appreciate it. -Tom Hamilton