------- Comment #3 from dave at hiauly1 dot hia dot nrc dot ca 2007-08-08 18:11 ------- Subject: Re: Segmentation fault bootstrapping on HP-UX 11.11
> ------- Comment #2 from pda at freeshell dot org 2007-08-08 17:10 ------- > I tried configuring for HP ld as you suggested, but that didn't make a > difference. However what seems to have done the trick was bootstrapping with > HP's C compiler rather than gcc-3.3.6. My gcc-3.3.6 has been configured to > use > GNU ld, and generally seems to work quite well except for this usage. I assume that your gcc-3.3.6 was built configured to generate 64-bit code and binaries. gcc-3.3.6 -v will show how it was configured. Can you provide this info? This affects the behavior of configure. If this shows a hppa64 target, then this is a native build and make bootstrap should work. Otherwise, you are trying to do a 32 to 64-bit cross build. It would be nice if make bootstrap worked in this situation, but it's never tested. I only test native builds. In trying to reproduce your problem, I find that GNU ld is not going to work with recent GCC version. In particular, hidden support is broken in shared libraries. This causes a problem with the shared version of libstdc++. Also, GCC assumes gnu symbol versioning is available if you use GNU ld. This is not supported by the HP-UX dynamic loader. There is a configure option to turn symbol versioning off. However, configure should be fixed to turn it off on HP-UX by default. There's also another bug that you will hit if you try to build fortran. I tried to fix some of these problems last week but it's tricky. To make any progress on your bug, more information is needed. We need more details on your bootstrap compiler. Then, could you rerun the failing compilation adding "-v" to the command line that fails. This will provide more details as to which gcc component failed. If you can, rerun the failing command under gdb, provide a backtrace, a disassembly around the instruction that faults, and register information for the registers in the faulting instruction. This will give a better idea as to what's happening. Dave -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32894
