Summary: | Segmentation fault in gettext-0.14.4 during bootstrap | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Heinrich Götzger <goetzger> |
Component: | [OLD] GCC Porting | Assignee: | Please assign to toolchain <gcc-porting> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2005.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Heinrich Götzger
2006-01-18 07:57:43 UTC
when you say "reproducible" do you mean it fails at the same spot everytime ? the fact that WinXP isnt stable makes it sound like the hardware is flaky also, i'm pretty sure using -march=pentium3 for a pentium m is incorrect ... you should be using -march=pentiumm (In reply to comment #1) > when you say "reproducible" do you mean it fails at the same spot everytime ? It's been in the gettext package, I'm not sure if it is at the same peace of code, or even at the same line. > > the fact that WinXP isnt stable makes it sound like the hardware is flaky Yes, that's what I want to make sure, I have ten identical pieces of these boxes and they rebooting once in a while (more or less daily, with and without user influence)and we have no idea why. That's why I choose my favorite linux to catch that problem. > > also, i'm pretty sure using -march=pentium3 for a pentium m is incorrect ... > you should be using -march=pentiumm I followed this guide: http://gentoo-wiki.com/Safe_Cflags#Pentium-M_.2F_Centrino_.28Intel.29 and I have a gcc (GCC) 3.3.5-20050130 from the boot-CD. So I'll try with pentium-m as well, if you recommend (using scripts/bootstrap.sh -r). Cheers (In reply to comment #2) > (In reply to comment #1) > > when you say "reproducible" do you mean it fails at the same spot everytime ? > It's been in the gettext package, I'm not sure if it is at the same peace of > code, or even at the same line. No it's on different spots. (binutils, gcc) So it definitely has nothing to do with either gcc, gettext or bootstrap. I think you can close this bug. It's most likely the Hardware itself. Sorry for the noise. > > > > also, i'm pretty sure using -march=pentium3 for a pentium m is incorrect ... > > you should be using -march=pentiumm > > I followed this guide: > http://gentoo-wiki.com/Safe_Cflags#Pentium-M_.2F_Centrino_.28Intel.29 > and I have a gcc (GCC) 3.3.5-20050130 from the boot-CD. > So I'll try with pentium-m as well, if you recommend (using > scripts/bootstrap.sh -r). just to note this here as well: pentium-m is not working for me reproducible. Thanks and Cheers (In reply to comment #3) > No it's on different spots. (binutils, gcc) > > So it definitely has nothing to do with either gcc, gettext or bootstrap. > I think you can close this bug. > > It's most likely the Hardware itself. sounds like it > just to note this here as well: > pentium-m is not working for me reproducible. side note ... gcc-3.3.x support of pentium m seems to be flaky, so i wouldnt use -march=pentiumm with 3.3.x compilers ... 3.4.x+ seems to be fine though *** This bug has been marked as a duplicate of 20600 *** |