Re: Persistant egcs-1.1.x build failures (cc1 signal 11)

Re: Persistant egcs-1.1.x build failures (cc1 signal 11)

[Rene Janssen]

I agree that one should know what they are doing when updating manually to
glibc2. 
Why do you advice to build glibc2 with egcs-1.0.3? Is that safe enough? 
Maybe you should make your step by step guide also available through the
Glibc2 homepage, so we can
verify & track problems that occur when installing glibc manually.

Thanks.


At 11:07 AM 11/30/98 -0800, H.J. Lu wrote:
>
>Personally, I won't do it that way. It has so many problems. You have
>to know what you are doing. I suggest you get a new glibc 2 based system
>instead. I am running RedHat 5.2 now. I have no serious problem.
>
>I don't have the time to write things down in details. If you want to
>install glibc 2 under /usr, you can try
>
>1. Install my egcs-1.0.3-libc5.x86.tar.bz2.
>2. Configre glibc 2 with --prefix=/usr.
>3. Build/install glibc 2.
>4. Install my egcs-1.0.3-glibc.x86.tar.bz2.
>5. Remove all header files which are not overwritten by the
>header files from glibc 2.
>6. Add /usr/i486-linux-libc5/lib to /etc/ld.so.conf.
>7. Copy all the old shared libraries to /usr/i486-linux-libc5/lib,
>excluding those in /lib. 
>8. Run ldconfig.
>9. Remove all the old libraries, except for those in
>/usr/i486-linux-libc5/lib and /lib, with "rm -f".
>10. Remove the old lib*.so in /lib.
>11. Do
># sync
># sync
># sync
># sync
>and then push the reset button.
>12. Configure egcs as
># ...../configure --enable-shared --enable-threads --prefix=/usr
--with-local-prefix=/usr/local
>13. Build/install egcs.
>14. Recompile any libraries you want to use to build programs.
>
>Now you are done. You can recompile any programs to link against glibc 2.
>
>As I said, it is very tricky. You have to know what you are
>doing.
>
>
>H.J.
>
>

Re: Persistant egcs-1.1.x build failures (cc1 signal 11)

[H.J. Lu]

> 
> 
> I agree that one should know what they are doing when updating manually to
> glibc2. 
> Why do you advice to build glibc2 with egcs-1.0.3? Is that safe enough? 

Good question. I don't know for sure about answer. Maybe you should
build egcs 1.1.1 instead of installing my egcs-1.0.3 binary and use
it to build glibc 2.

> Maybe you should make your step by step guide also available through the
> Glibc2 homepage, so we can
> verify & track problems that occur when installing glibc manually.
> 

The problem is it is not the only way to do it and it may not be
the best way. I have never verified it. Feel free to document the
procedure.

-- 
H.J. Lu (hjl@gnu.org)

Re: Persistant egcs-1.1.x build failures (cc1 signal 11)

[Horst von Brand]

Rene Janssen <rjanssen@ns.oke.nl> said:
> I agree that one should know what they are doing when updating manually to
> glibc2. 

Better fetch a distribution based on glibc2, it hurts much less ;-)

> Why do you advice to build glibc2 with egcs-1.0.3? Is that safe enough? 

egcs _is_ safe. glibc-2.1 snapshots should _not_ be built with gcc-2.7.2.3
or earlier, gcc-2.8.1 is said to have problems. That linux-2.0.xx should
not be built with egcs on intel is because the kernel depends on (broken)
gcc-2.7.2.3 behaviour, or assumes certain optimizations won't be done,
etc. OTOH, I've been compiling linux-2.1 versions with egcs for ages (since
january or so), the problems have mostly been fixed by now as I'm not
exactly the only one to do so ;-)
-- 
Dr. Horst H. von Brand                       mailto:vonbrand@inf.utfsm.cl
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513

Re: Persistant egcs-1.1.x build failures (cc1 signal 11)

[H.J. Lu]

> 
> At 07:48 AM 11/29/98 -0800, H.J. Lu wrote:
> >> Ps, I upgraded to libc6 with this pointer :
> http://huizen.dds.nl/~frodol/glibc/ .
> >> No problems , works fine. Build KDE on it. The find_solib error in gdb=
>  was
> >> because I didnt switched the environment (libc5), so thats not the poi=
> nt.
> >>=20
> >
> >How did you upgrade to libc6? It is not recommended to everyone since
> >it can lead to a broken system very easily if you don't know what you
> >are doing. Under which directory you install libc6?
> >
> 
> I upgraded just like said in Frodol's step by step guide. I installed it =
> in
> /usr/i586-linux-libc6/lib. I havent noticed any problems except compiling
> egcs.
> The trick in this guide is that you can switch between your primary libc5=
>  and
> libc6 very easily. If you see any flaws please tell me.=20
> =20

Personally, I won't do it that way. It has so many problems. You have
to know what you are doing. I suggest you get a new glibc 2 based system
instead. I am running RedHat 5.2 now. I have no serious problem.

I don't have the time to write things down in details. If you want to
install glibc 2 under /usr, you can try

1. Install my egcs-1.0.3-libc5.x86.tar.bz2.
2. Configre glibc 2 with --prefix=/usr.
3. Build/install glibc 2.
4. Install my egcs-1.0.3-glibc.x86.tar.bz2.
5. Remove all header files which are not overwritten by the
header files from glibc 2.
6. Add /usr/i486-linux-libc5/lib to /etc/ld.so.conf.
7. Copy all the old shared libraries to /usr/i486-linux-libc5/lib,
excluding those in /lib. 
8. Run ldconfig.
9. Remove all the old libraries, except for those in
/usr/i486-linux-libc5/lib and /lib, with "rm -f".
10. Remove the old lib*.so in /lib.
11. Do
# sync
# sync
# sync
# sync
and then push the reset button.
12. Configure egcs as
# ...../configure --enable-shared --enable-threads --prefix=/usr --with-local-prefix=/usr/local
13. Build/install egcs.
14. Recompile any libraries you want to use to build programs.

Now you are done. You can recompile any programs to link against glibc 2.

As I said, it is very tricky. You have to know what you are
doing.


H.J.

Re: Persistant egcs-1.1.x build failures (cc1 signal 11)

[Rene Janssen]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1447 bytes --]

At 07:48 AM 11/29/98 -0800, H.J. Lu wrote:
>> Ps, I upgraded to libc6 with this pointer :
http://huizen.dds.nl/~frodol/glibc/ .
>> No problems , works fine. Build KDE on it. The find_solib error in gdb was
>> because I didnt switched the environment (libc5), so thats not the point.
>> 
>
>How did you upgrade to libc6? It is not recommended to everyone since
>it can lead to a broken system very easily if you don't know what you
>are doing. Under which directory you install libc6?
>

I upgraded just like said in Frodol's step by step guide. I installed it in
/usr/i586-linux-libc6/lib. I havent noticed any problems except compiling
egcs.
The trick in this guide is that you can switch between your primary libc5 and
libc6 very easily. If you see any flaws please tell me. 
 
Btw. I checked egcs-1.0.3 yesterday again. It didnt compile either. My
first successfull build was for libc5.
It failes on enquire.c (cc1 signal 11) this time. This problem is also
reported by others on frodol's 
problem page. There is an advice to try it without optimizing but it doesnt
work.

I debugged both egcs-1.0.3 & 1.1.1-prerelease-3, and they both crash at the
end of output_constant_pool() in varasm.c for no good reason. My guess is
that cc1 is miscompiled yes, but I cant trace the cause. Maybe its a glibc
thing , maybe not.

I think this error is reproduceable if you've got time to check out
Frodol's step by step guide. 

Regards,

René Janssen

Re: Persistant egcs-1.1.x build failures (cc1 signal 11)

[H.J. Lu]

> Ps, I upgraded to libc6 with this pointer : http://huizen.dds.nl/~frodol/glibc/ .
> No problems , works fine. Build KDE on it. The find_solib error in gdb was
> because I didnt switched the environment (libc5), so thats not the point.
> 

How did you upgrade to libc6? It is not recommended to everyone since
it can lead to a broken system very easily if you don't know what you
are doing. Under which directory you install libc6?

-- 
H.J. Lu (hjl@gnu.org)

Re: Persistant egcs-1.1.x build failures (cc1 signal 11)

[Rene Janssen]

 
> Can anybody give me a clue whats going on? 
> 
> Thanks,

>Let me guess, do you happen to run Slackware? As far as I know, it
i>s broken.

Its indeed Slackware 3.4 , but I upgraded almost everything by hand. 
What is supposed to be broken then ?

Ps, I upgraded to libc6 with this pointer : http://huizen.dds.nl/~frodol/glibc/ .
No problems , works fine. Build KDE on it. The find_solib error in gdb was
because I didnt switched the environment (libc5), so thats not the point.

Thanks for more advice,

Rene Janssen.

(please cc me)

Feel free to ask more information.
 

Re: Persistant egcs-1.1.x build failures (cc1 signal 11)

[H.J. Lu]

> 
> 
> Hello,
> 
> I have a continuing annoying problem with building egcs. During building of stage1/libgcc2.a cc1 crashes with
> signal 11. Its _not_ a hardware problem, because it always crashes at the same spot. (see below)
> I havent had this problem with egcs-1.0.3 , but since egcs-1.1b I cant compile it anymore.
> 
> I tried building it with the -static flag but with the same result. Tried also -nfp because 
> it appears to be something with floats or a math thing. No success. Tried also with gcc -V 2.7.2.3.
> 
> Can anybody give me a clue whats going on? 
> 
> Thanks,

Let me guess, do you happen to run Slackware? As far as I know, it
is broken.



H.J.

Persistant egcs-1.1.x build failures (cc1 signal 11)

[Rene Janssen]

Hello,

I have a continuing annoying problem with building egcs. During building of stage1/libgcc2.a cc1 crashes with
signal 11. Its _not_ a hardware problem, because it always crashes at the same spot. (see below)
I havent had this problem with egcs-1.0.3 , but since egcs-1.1b I cant compile it anymore.

I tried building it with the -static flag but with the same result. Tried also -nfp because 
it appears to be something with floats or a math thing. No success. Tried also with gcc -V 2.7.2.3.

Can anybody give me a clue whats going on? 

Thanks,

Rene Janssen.

Last words, version and configuration information :

  echo ${name}; \
  ./xgcc -B./ -O2   -DIN_GCC    -g -I./include  -fPIC -g1 -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED   -I. -I../../src/egcs/gcc -I../../src/egcs/gcc/config -c -DL${name} \
      ../../src/egcs/gcc/libgcc2.c -o ${name}.o; \
  if [ $? -eq 0 ] ; then true; else exit 1; fi; \
  ` if [ -f /hda5/usr/local/gcc/../binutils/ar ] ; then echo /hda5/usr/local/gcc/../binutils/ar ; else if [ "i586-pc-linux-gnu" = "i586-pc-linux-gnu" ] ; then echo ar; else t='s,x,x,'; echo ar | sed -e $t ; fi; fi` rc tmplibgcc2.a ${name}.o; \
  rm -f ${name}.o; \
done
_muldi3
_divdi3
_moddi3
_udivdi3
_umoddi3
_negdi2
_lshrdi3
_ashldi3
_ashrdi3
_ffsdi2
_udiv_w_sdiv
_udivmoddi4
_cmpdi2
_ucmpdi2
_floatdidf
xgcc: Internal compiler error: program cc1 got fatal signal 11
make[2]: *** [libgcc2.a] Error 1
make[2]: Leaving directory `/hda5/usr/local/gcc'
make[1]: *** [bootstrap-lean] Error 2
make[1]: Leaving directory `/hda5/usr/local/gcc'
make: *** [bootstrap-lean] Error 2

# This directory was configured as follows:
../src/egcs/configure --with-gcc-version-trigger=/hda5/usr/src/egcs/gcc/version.c --host=i586-pc-linux-gnu 
--enable-threads --enable-shared --prefix=/hda5/usr/local 
--nfp --with-gnu-as --with-gnu-ld --enable-version-specific-runtime-libs --verbose --norecursion
# using "mh-frag" and "mt-frag"

jupiter:/hda5/usr/local# ld -v
GNU ld version 2.9.1 (with BFD 2.9.1.0.15)

gcc -v
Reading specs from /usr/lib/gcc-lib/i586-linux-libc6/2.8.1/specs
gcc version 2.8.1

 uname -a
Linux jupiter 2.1.130 #1 Fri Nov 27 11:30:06 CET 1998 i586 unknown

jupiter:/hda5/usr/local# cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 5
model           : 6
model name      : K6 (PR166 - PR266)
stepping        : 2
cpu MHz         : 200.457892
fdiv_bug        : no
hlt_bug         : no
sep_bug         : no
f00f_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr mce cx8 mmx
bogomips        : 399.77

jupiter:/hda5/usr/local/gcc/stage1# ldd cc1
        libc.so.6 => /usr/i586-linux-libc6/lib/libc.so.6 (0x40004000)
        /lib/ld-linux.so.2 => /usr/i586-linux-libc6/lib/ld-linux.so.2 (0x2aaaa000)

jupiter:/hda5/usr/local/gcc# ./xgcc -v
Using builtin specs.
gcc version egcs-2.91.59 19981124 (egcs-1.1.1 pre-release #3)

jupiter:/hda5/usr/local/gcc# ./xgcc --print-search-dirs
install: /hda5/usr/local/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.59/
programs: /hda5/usr/local/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.59/:/hda5/usr/local/lib/gcc-lib/i586-pc-linux-gnu/:/usr/lib/gcc/i586-pc-linux-gnu/egcs-2.91.59/:/usr/lib/gcc/i586-pc-linux-gnu/:/hda5/usr/local/i586-pc-linux-gnu/bin/i586-pc-linux-gnu/egcs-2.91.59/:/hda5/usr/local/i586-pc-linux-gnu/bin/
libraries: /hda5/usr/local/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.59/:/usr/lib/gcc/i586-pc-linux-gnu/egcs-2.91.59/:/hda5/usr/local/i586-pc-linux-gnu/lib/i586-pc-linux-gnu/egcs-2.91.59/:/hda5/usr/local/i586-pc-linux-gnu/lib/:/hda5/usr/local/lib/i586-pc-linux-gnu/egcs-2.91.59/:/hda5/usr/local/lib/:/lib/i586-pc-linux-gnu/egcs-2.91.59/:/lib/:/usr/lib/i586-pc-linux-gnu/egcs-2.91.59/:/usr/lib/

Re: Persistant egcs-1.1.x build failures (cc1 signal 11)

[Rene Janssen]

Here is the core file :


bash# gdb -c core cc1
GDB is free software and you are welcome to distribute copies of it
 under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.16 (i486-slackware-linux),
Copyright 1996 Free Software Foundation, Inc...
Core was generated by `./cc1 /tmp/ccnOKAEi.i -quiet -dumpbase libgcc2.c -g -g1 -
O2 -fPIC -o /tmp/ccvff'.
Program terminated with signal 11, Segmentation fault.
find_solib: Can't read pathname for load map: I/O error

#0  output_constant_pool (fnname=???, fndecl=???)
    at ../../src/egcs/gcc/varasm.c:3673
3673    }
Breakpoint 1 at 0x8048f00
Breakpoint 2 at 0x80490f0
Breakpoint 3 at 0x80647bf: file ../../src/egcs/gcc/toplev.c, line 2114.
(gdb) bt
#0  output_constant_pool (fnname=???, fndecl=???)
    at ../../src/egcs/gcc/varasm.c:3673
(gdb)