Re: How overcome error installing GCC-4.3.2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



OK. I now switched gcc-4.2.2 and gcc-4.2.3 In both cases the compilations seems
to have been succesful (gmake ended without errors). I am wondering whether one 
could  make a full test of the compilation without installing DejaGnu, Tcl, and Expect. 

The installation seems to have been OK. The Expect installation is
given this error

usr/sfw/bin/gcc -c  -I. -I. -I/home/srojas/MySoftware/tcl8.5.5/generic   -DEXP_VERSION=\"5.43.0\" -DSCRIPTDIR=\"/home/srojas/My_prog/expect-5.43/lib/expect5.43\" -DEXECSCRIPTDIR=\"/home/srojas/My_prog/expect-5.43/lib/expect5.43\" -DTCL_DEBUGGER -DUSE_NON_CONST -DSTTY_BIN=\"/bin/stty\" -I/home/srojas/MySoftware/tcl8.5.5/unix   -pipe  -DDFLT_STTY="\"sane\""  exp_inter.c
exp_inter.c: In function `intMatch':
exp_inter.c:294: error: `TCL_REG_BOSONLY' undeclared (first use in this function)


Sergio

----- Original Message -----
From: "Brian Dessent" 
To: "Sergio Rojas" 
Cc: gcc-help@xxxxxxxxxxx
Subject: Re: How overcome error installing GCC-4.3.2
Date: Sun, 07 Dec 2008 12:57:23 -0800


Sergio Rojas wrote:

> Brian, I switched  to the gnu linker, the error now looks like:

Note that the target-specific install notes recommend the opposite for
Solaris 10, the GNU assembler and Sun linker:


>  [ -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?

It's trying to link a 64 bit library, but apparently your gld doesn't
have 64 bit support installed.  You could build the linker yourself
(from binutils), but given the above I don't think it would be the best
use of time.

> 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?

It's a diff that's meant to be applied with the patch program.  It uses
the line number hints (@@) as well as the surrounding context to make
the intended changes.  Alternatively since this patch has already been
applied to the gcc-4_3-branch in svn you could just use that (or a
recent 4.3 snapshot tarball.)

Brian


-- 
Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux