On Thu, 21 Jul 2005 05:09, Zac Medico wrote:
> Glenn Enright wrote:
> > On Wed, 20 Jul 2005 21:26, Zac Medico wrote:
> >>Does busybox gzip work any better?
> >>
> >>Zac
> >
> > Yes works just fine. What does that tell you?
>
> You have a workaround ;-). The problem seems to be in glibc (only
> dependency of gzip, verified by "ldd `which gzip`") or your toolchain. You
> might be able to get some clues from gdb or strace, but whatever the cause,
> you probably need to replace glibc and/or your toolchain.
>
> I wonder if static linking would help gzip?
>
> USE=static emerge gzip
>
> Zac
Bugger. was afraid of that. Ive been running gcc3.4 for a while which needs
some ~x86 stuff (glibc). Umm... static doesnt change.
Strace on gzip isnt very interesting, gunzip gives me a stat64 file error
towards the end...
open("trampoline.gz", O_RDONLY|O_LARGEFILE) = 3
read(3, "\37\213\10\0109\306\336B\0\3trampoline\0\313\316\316\316"..., 32768)
= 53
read(3, "", 32715) = 0
stat64("trampoline", 0xbfffe880) = -1 ENOENT (No such file or
directory)
open("trampoline", O_WRONLY|O_CREAT|O_EXCL|O_LARGEFILE, 0600) = 4
fstat64(4, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
stat64("trampolin", 0xbfffe880) = -1 ENOENT (No such file or
directory)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
--
There are times when truth is stranger than fiction and lunch time is one
of them.
--
gentoo-user@gentoo.org mailing list
