Glenn Enright wrote:
On Fri, 22 Jul 2005 08:32, Richard Fish wrote:
actually turns out that I had an old version of gzip living in /usr/bin for
some odd reason. Now that I've removed it and added symlinks to /bin, all my
problems have gone away! Sorry for all the hassle guys. My system has bee
On Fri, 22 Jul 2005 08:32, Richard Fish wrote:
actually turns out that I had an old version of gzip living in /usr/bin for
some odd reason. Now that I've removed it and added symlinks to /bin, all my
problems have gone away! Sorry for all the hassle guys. My system has been
installed for since
Glenn Enright wrote:
On Thu, 21 Jul 2005 17:45, Zac Medico wrote:
Richard Fish wrote:
I will take a look through the gzip source and see if anything
interesting shows up.
Richard, you are a saint ;-). But remember, he said that gunzip only
segfaults with files that he compress
On Thu, 21 Jul 2005 17:45, Zac Medico wrote:
> Richard Fish wrote:
> > I will take a look through the gzip source and see if anything
> > interesting shows up.
>
> Richard, you are a saint ;-). But remember, he said that gunzip only
> segfaults with files that he compressed himself which suggests
On Thu, 21 Jul 2005 10:02, Zac Medico wrote:
> Glenn Enright wrote:
> > 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
Richard Fish wrote:
I will take a look through the gzip source and see if anything interesting shows up.
Richard, you are a saint ;-). But remember, he said that gunzip only segfaults
with files that he compressed himself which suggests that the files are being
corrupted when he compresses
Glenn Enright wrote:
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 se
Glenn Enright wrote:
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...
My system is mostly ~x86 stuff and I've never
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
> dep
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
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?
--
Seeing is believing. You wouldn't have seen it if you hadn't believed it.
--
gentoo-user@gentoo.org mailing list
Glenn Enright wrote:
Ok did this
CFLAGS="-pipe -march=pentium4 -O2" emerge -avD zlib gzip
and still getting the same errors. normal CFLAGS are as follows
CFLAGS="-pipe -w -march=pentium4 -O2 -mfpmath=sse -fomit-frame-pointer -fweb"
Does busybox gzip work any better?
Zac
--
gentoo-user@gento
Glenn Enright wrote:
Not that I wouldve picked, trying with some basic ones now. It would seem that
because emerge is still working, that the problems are from when I *make* gz
files, rather than outside files from such as portage. The files I make unzip
to a zero length file and deliver a se
On Wed, 20 Jul 2005 19:33, Zac Medico wrote:
> Glenn Enright wrote:
> > On Wed, 20 Jul 2005 00:32, Glenn Enright wrote:
> >>On Tue, 19 Jul 2005 16:56, Zac Medico wrote:
> >>>That could be a hardware problem. Maybe your cpu is overheating or
> >>>there's something wrong with your ram. You can use
On Wed, 20 Jul 2005 19:33, Zac Medico wrote:
> Glenn Enright wrote:
> > On Wed, 20 Jul 2005 00:32, Glenn Enright wrote:
> >>On Tue, 19 Jul 2005 16:56, Zac Medico wrote:
> >>>That could be a hardware problem. Maybe your cpu is overheating or
> >>>there's something wrong with your ram. You can use
Glenn Enright wrote:
On Wed, 20 Jul 2005 00:32, Glenn Enright wrote:
On Tue, 19 Jul 2005 16:56, Zac Medico wrote:
That could be a hardware problem. Maybe your cpu is overheating or
there's something wrong with your ram. You can use a livecd with
memtest86+ to test the ram.
Zac
Seems odd
On Wed, 20 Jul 2005 00:32, Glenn Enright wrote:
> On Tue, 19 Jul 2005 16:56, Zac Medico wrote:
> > That could be a hardware problem. Maybe your cpu is overheating or
> > there's something wrong with your ram. You can use a livecd with
> > memtest86+ to test the ram.
> >
> > Zac
>
> Seems odd cons
On Tue, 19 Jul 2005 16:56, Zac Medico wrote:
> Glenn Enright wrote:
> > gzip seg faults when uncompressing. Man and info pages work fine as do
> > emerges, and after recompiling zlib, glibc and some other stuff, I still
> > have no clue what the problem is.
> >
> > Before you ask I'm not running yp
Glenn Enright wrote:
gzip seg faults when uncompressing. Man and info pages work fine as do
emerges, and after recompiling zlib, glibc and some other stuff, I still have
no clue what the problem is.
Before you ask I'm not running ypbind, and have a P4 2.6. Any ideas peoples?
That could be a
gzip seg faults when uncompressing. Man and info pages work fine as do
emerges, and after recompiling zlib, glibc and some other stuff, I still have
no clue what the problem is.
Before you ask I'm not running ypbind, and have a P4 2.6. Any ideas peoples?
--
SUBSTITUTE TEACHERS ARE NOT SCABS
SU
20 matches
Mail list logo
