Brian, I switched to the gnu linker, the error now looks like: [ -f amd64/libgcc_s.so.1 ]; then mv -f amd64/libgcc_s.so.1 amd64/libgcc_s.so.1.backup; else true; fi && mv amd64/libgcc_s.so.1.tmp amd64/libgcc_s.so.1 && ln -s libgcc_s.so.1 amd64/libgcc_s.so /usr/sfw/bin/gld: cannot open linker script file ldscripts/elf_x86_64.xsc: No such file or directory I searched ( find / -name elf_x86_64.xsc -print) without success for that file "elf_x86_64.xsc" in my Solaris 10 distribution. Any advise were to go for it? By the way, Brian, as I understand, the workaround you mentioned below, which is formally listed at: http://gcc.gnu.org/ml/gcc-patches/2008-10/msg00441.html should be included in the "gcc/config.gcc". At what level in the script should one includes the suggested lines? Sergio ----- Original Message ----- From: "Brian Dessent" To: "Sergio Rojas" Cc: gcc-help@xxxxxxxxxxx Subject: Re: How overcome error installing GCC-4.3.2 Date: Fri, 05 Dec 2008 15:12:07 -0800 Sergio Rojas wrote: > I though that "--with-mpfr=$MPFRDIR and --with-gmp=$GMPDIR" > were taken care of that. Well, now the error is as follows Those options tell the compiler and link editor where to find the files during compilation and linking. They don't tell the operating system's dynamic loader where to find the libraries at runtime. > (after setting LD_LIBRARY_PATH to the respectives libraries dir > and also LDFLAGS="-L$MPFRDIR -R$MPFRDIR -L$GMPDIR -R$GMPDIR"): You really shouldn't have to set LDFLAGS. Just the --with options alone should take care of it. > & if [ -f amd64/libgcc_s.so.1 ]; then mv -f amd64/libgcc_s.so.1 > amd64/libgcc_s.so.1.backup; else true; fi && mv > amd64/libgcc_s.so.1.tmp amd64/libgcc_s.so.1 && ln -s > libgcc_s.so.1 amd64/libgcc_s.so > ld: fatal: unwind table: file > /home/srojas/MySoftware/my_install/./gcc/amd64/crtend.o: section > .eh_frame: bad cie version 0: offset 0xfffffd7fffdfa200 This is a bug in Sun's linker, see which includes a workaround (which will be in 4.3.3.) > By the way, is there a way to track at which stage of the > compilation the script is stopping? If you watch the build messages you'll regularly see e.g. "Configuring stage 1 in i386-pc-solaris2.10/libgcc" scroll by, so just scroll up from the error to the first such line. (It helps to log the output and then you can grep instead.) You can also 'cat stage_current' which should tell you the current state of the tree at any given time. Brian -- Be Yourself @ mail.com! Choose From 200+ Email Addresses Get a Free Account at www.mail.com
