From rmottola at opencsw.org Mon Aug 24 15:27:54 2020 From: rmottola at opencsw.org (Riccardo Mottola) Date: Mon, 24 Aug 2020 15:27:54 +0200 Subject: rebuilding gcc 4.8 on solaris 9 In-Reply-To: References: Message-ID: Hi! On 21/06/2020 18:26, Dagobert Michelsen wrote: > Am 20.06.2020 um 16:02 schrieb Riccardo Mottola via maintainers: >> I am attempting to rebuild gcc 4.8.4 on solaris 9 (we have a branch for that) with the goal to get it to 4.8.5 then... > This is probably due to sparcv8plus vs. sparcv8 but this is only guesswork from me. > Getting gcc to compile is actually pretty hard. It is.. but e.g. in MacPorts things go quite smoothly. So it can be done :) it is tedious, but I think it is worth. I found this ih the current gcc4 (that is 4.9.3) makefile: # We're not building GCC-4.7 on Solaris 9, because GCC-4.7 requires the # sparcv8+ architecture. # PACKAGING_PLATFORMS = solaris9-sparc solaris9-i386 PACKAGING_PLATFORMS += solaris10-sparc solaris10-i386 ISA_DEFAULT_sparc-5.9 = sparcv8plus ISA_DEFAULT_i386-5.9? = pentium_pro So indeed we need sparcv8+ But why can't we enable it on solaris9? If I remember correctly Solaris9 only runs on UltraSparc, thus v9 (and its 32bit v8+) and Solaris 8 was the last OS with pure 32bit support. Can't we just built it then? In the 4.6.x build I see this instead: # there could be some abstractions in gar.conf.mk, but at the moment there # aren't so let's specify architectures by hand. # # This avoids the sparcv8+ binaries. CPU_sparc_32 = v8 CPU_sparc_64 = v9 CPU_i386_32 = i386 CPU_i386_64 = x86-64 where it seems explicit to avoid v8+ ! Riccardo -------------- next part -------------- An HTML attachment was scrubbed... URL: From rmottola at opencsw.org Mon Aug 24 15:35:24 2020 From: rmottola at opencsw.org (Riccardo Mottola) Date: Mon, 24 Aug 2020 15:35:24 +0200 Subject: off-topic - broken T2000 - cpu error message Message-ID: Hi all! I have a Netra T2000 which I use little (darn noisy, prefer my T1s...) but I extra got to do some more in-house for BigEndian and SPARC support! I got it working some months ago and I used it little (no big compilations yet, I just familiarized and installed and tested OpenCSW packages). Suddenly, it doesn't boot anymore! Powers on, powers off... attaching a serial console I see this error: ERROR: No functional CPUs available FATAL: No cpus in bootset FATAL: The HOST Processor has a configuration error, forcing a power-down Is my CPU really fried? I did not stress the system that much. I hope that maybe the error is spurious. At first, I thought the PROM battery died (it was loosing time lately) so I replaced it, without gain. I tried reseating the CPU (the contacts look slightly oxidyzed) without a change. The CPU comes off with the whole heatsink, they look molded together :) I guess the thermal paste dried like glue! Riccardo From rmottola at opencsw.org Mon Aug 24 23:18:58 2020 From: rmottola at opencsw.org (Riccardo Mottola) Date: Mon, 24 Aug 2020 23:18:58 +0200 Subject: rebuilding gcc 4.8 on solaris 9 In-Reply-To: References: Message-ID: Hi, On 21/06/2020 18:26, Dagobert Michelsen wrote: > This is probably due to sparcv8plus vs. sparcv8 but this is only guesswork from me. > Getting gcc to compile is actually pretty hard. I tried to build current gcc 4.x, from our repo, on solaris 9. it is 4.9.3, I of course did --enable-obsolete . It is set to build sparc v8+ I understand. Build fails with: libtool: link: /home/rmottola/opencsw/gcc4/trunk/work/solaris9-sparc/build-isa-sparcv8plus/objdir/./gcc/xgcc -shared-libgcc -B/home/rmottola/opencsw/gcc4/trunk/work/solaris9-sparc/build-isa-sparcv8plus/objdir/./gcc -nostdinc++ -L/home/rmottola/opencsw/gcc4/trunk/work/solaris9-sparc/build-isa-sparcv8plus/objdir/sparc-sun-solaris2.9/libstdc++-v3/src -L/home/rmottola/opencsw/gcc4/trunk/work/solaris9-sparc/build-isa-sparcv8plus/objdir/sparc-sun-solaris2.9/libstdc++-v3/src/.libs -L/home/rmottola/opencsw/gcc4/trunk/work/solaris9-sparc/build-isa-sparcv8plus/objdir/sparc-sun-solaris2.9/libstdc++-v3/libsupc++/.libs -B/opt/csw/sparc-sun-solaris2.9/bin/ -B/opt/csw/sparc-sun-solaris2.9/lib/ -isystem /opt/csw/sparc-sun-solaris2.9/include -isystem /opt/csw/sparc-sun-solaris2.9/sys-include??? -shared -nostdlib /home/rmottola/opencsw/gcc4/trunk/work/solaris9-sparc/build-isa-sparcv8plus/objdir/./gcc/crti.o /usr/ccs/lib/values-Xa.o /home/rmottola/opencsw/gcc4/trunk/work/solaris9-sparc/build-isa-sparcv8plus/objdir/./gcc/crtbegin.o .libs/compatibility.o .libs/compatibility-debug_list.o .libs/compatibility-debug_list-2.o .libs/compatibility-c++0x.o .libs/compatibility-atomic-c++0x.o .libs/compatibility-thread-c++0x.o .libs/compatibility-chrono.o .libs/compatibility-condvar.o? -Wl,-z -Wl,allextract ../libsupc++/.libs/libsupc++convenience.a ../src/c++98/.libs/libc++98convenience.a ../src/c++11/.libs/libc++11convenience.a -Wl,-z -Wl,defaultextract -L/home/rmottola/opencsw/gcc4/trunk/work/solaris9-sparc/build-isa-sparcv8plus/objdir/sparc-sun-solaris2.9/libstdc++-v3/libsupc++/.libs -L/home/rmottola/opencsw/gcc4/trunk/work/solaris9-sparc/build-isa-sparcv8plus/objdir/sparc-sun-solaris2.9/libstdc++-v3/src -L/home/rmottola/opencsw/gcc4/trunk/work/solaris9-sparc/build-isa-sparcv8plus/objdir/sparc-sun-solaris2.9/libstdc++-v3/src/.libs -lm -lrt -L/home/rmottola/opencsw/gcc4/trunk/work/solaris9-sparc/build-isa-sparcv8plus/objdir/./gcc -L/opt/csw/sparc-sun-solaris2.9/bin -L/opt/csw/sparc-sun-solaris2.9/lib -L/usr/ccs/lib -lgcc_s -lc -lgcc_s -lc /home/rmottola/opencsw/gcc4/trunk/work/solaris9-sparc/build-isa-sparcv8plus/objdir/./gcc/crtend.o /home/rmottola/opencsw/gcc4/trunk/work/solaris9-sparc/build-isa-sparcv8plus/objdir/./gcc/crtn.o -Wl,-M -Wl,libstdc++-symbols.ver-sun?? -Wl,-h -Wl,libstdc++.so.6 -o .libs/libstdc++.so.6.0.20 ld: fatal: relocation error: R_SPARC_32: file .libs/compatibility.o: symbol __gxx_personality_v0: offset 0xf9677 is non-aligned ld: fatal: relocation error: R_SPARC_32: file .libs/compatibility-chrono.o: symbol __gxx_personality_v0: offset 0xf98f7 is non-aligned ld: fatal: relocation error: R_SPARC_32: file ../libsupc++/.libs/libsupc++convenience.a(atexit_thread.o): symbol __gxx_personality_v0: offset 0xf99b3 is non-aligned ld: fatal: relocation error: R_SPARC_32: file ../libsupc++/.libs/libsupc++convenience.a(eh_alloc.o): symbol __gxx_personality_v0: offset 0xf9f1b is non-aligned ld: fatal: relocation error: R_SPARC_32: file ../libsupc++/.libs/libsupc++convenience.a(eh_globals.o): symbol __gxx_personality_v0: offset 0xfa247 is non-aligned ld: fatal: relocation error: R_SPARC_32: file ../libsupc++/.libs/libsupc++convenience.a(eh_personality.o): symbol __gxx_personality_v0: offset 0xfa39b is non-aligned ld: fatal: relocation error: R_SPARC_32: file ../libsupc++/.libs/libsupc++convenience.a(eh_ptr.o): symbol __gxx_personality_v0: offset 0xfa4a7 is non-aligned ld: fatal: relocation error: R_SPARC_32: file ../libsupc++/.libs/libsupc++convenience.a(eh_terminate.o): symbol __gxx_personality_v0: offset 0xfa5e3 is non-aligned ld: fatal: relocation error: R_SPARC_32: file ../libsupc++/.libs/libsupc++convenience.a(eh_tm.o): symbol __gxx_personality_v0: offset 0xfa and many more, all with relocation non-alignment issues. Riccardo From wilbury at opencsw.org Wed Aug 26 15:17:21 2020 From: wilbury at opencsw.org (Juraj Lutter) Date: Wed, 26 Aug 2020 15:17:21 +0200 Subject: off-topic - broken T2000 - cpu error message In-Reply-To: References: Message-ID: <497F7441-5A3F-4330-9956-1E46ED965D51@opencsw.org> Hi, Did you read https://support.oracle.com/knowledge/Sun%20Microsystems/1019720_1.html ? otis ? Juraj Lutter wilbury at opencsw.org > On 24 Aug 2020, at 15:35, Riccardo Mottola via maintainers wrote: > > Hi all! > > I have a Netra T2000 which I use little (darn noisy, prefer my T1s...) but I extra got to do some more in-house for BigEndian and SPARC support! > > I got it working some months ago and I used it little (no big compilations yet, I just familiarized and installed and tested OpenCSW packages). > > > Suddenly, it doesn't boot anymore! Powers on, powers off... attaching a serial console I see this error: > > ERROR: No functional CPUs available > FATAL: No cpus in bootset > FATAL: The HOST Processor has a configuration error, forcing a power-down > > > Is my CPU really fried? I did not stress the system that much. I hope that maybe the error is spurious. > > At first, I thought the PROM battery died (it was loosing time lately) so I replaced it, without gain. > > I tried reseating the CPU (the contacts look slightly oxidyzed) without a change. The CPU comes off with the whole heatsink, they look molded together :) I guess the thermal paste dried like glue! > > > Riccardo > -------------- next part -------------- An HTML attachment was scrubbed... URL: