I am sorry Brian. You should have spent your time in a more knowledgeable profitable task, instead of dealing with a SUN MYCROSYSTEM SOLARIS BUG. I see now the reasonable blaming people make because so many SUN-SOLARIS bugs. I am wondering, why AMD did not go to a better company? I mean too many bugs in SUN SOLARIS!!!. Either the managers at SUN did not care about the damage they are making to the developer community or they are too stubborn to realize such amount of damage and be aware of the clear amount of mistakes SUN MICROSYSTEM intentionally have made around the world.\ It is clear, after searching the internet, that SUN MYCROSYSTEM have intentionally made available a buggy system. Why AMD is following so desastrous company is a mistery. This is thel ast HPF AMD processor on my part!!!! My boss could fire me, but I will not val any purchae of AMD pocessors under SOLARIS !!! egio ----- 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
