From: Glenn Enright <elinar@ihug.co.nz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gzip segmentation fault
Date: Wed, 20 Jul 2005 20:18:25 +1200 [thread overview]
Message-ID: <200507202018.25203.elinar@ihug.co.nz> (raw)
In-Reply-To: <42DDFE41.6010206@gmail.com>
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 a livecd with
> >>>memtest86+ to test the ram.
> >>>
> >>>Zac
> >>
> >>Seems odd considering I am able to do major emerges with no apparent
> >>errors, including glibc, mplayer, etc. Still its worth checking out, so
> >>will give it a go tonight.
> >
> > Ok memtest been running for a few hours, but gave up nothing. stranger
> > and stranger... might try a ~x86 version
>
> You're not using any abnormal CFLAGS, are you?
>
> Zac
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"
--
fortune: No such file or directory
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-20 8:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 4:34 [gentoo-user] gzip segmentation fault Glenn Enright
2005-07-19 4:56 ` Zac Medico
2005-07-19 12:32 ` Glenn Enright
2005-07-20 7:36 ` Glenn Enright
2005-07-20 7:33 ` Zac Medico
2005-07-20 8:08 ` Glenn Enright
2005-07-20 8:02 ` Zac Medico
2005-07-20 8:18 ` Glenn Enright [this message]
2005-07-20 9:26 ` Zac Medico
2005-07-20 10:28 ` Glenn Enright
2005-07-20 17:09 ` Zac Medico
2005-07-20 21:54 ` Glenn Enright
2005-07-20 22:02 ` Zac Medico
2005-07-21 6:24 ` Glenn Enright
2005-07-21 5:33 ` Richard Fish
2005-07-21 5:45 ` Zac Medico
2005-07-21 11:47 ` Glenn Enright
2005-07-21 20:32 ` Richard Fish
2005-07-22 4:00 ` Glenn Enright
2005-07-22 4:41 ` Zac Medico
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200507202018.25203.elinar@ihug.co.nz \
--to=elinar@ihug.co.nz \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox