Of Eric Botcazou
Sent: Monday, November 21, 2005 4:25 PM
To: [EMAIL PROTECTED]
Cc: gcc@gcc.gnu.org
Subject: Re: compiling gcc-4.0.2 on solaris 9
CC to cc only. So, now the script is:
CC=cc
export CC
../gcc-4.0.2/configure
gmake bootstrap
Do not export CC and do not use a relative path:
CC=cc
Ok, here is my script (note I am in a directory with only the
script below when I execute the script below):
CC=cc /export/home/src/net/gnu/gcc-4.0.2/configure
gmake bootstrapmake_err 21
I get the exact same errors (at least as far as I see).
The target libiberty is not supposed to be
: Tuesday, November 22, 2005 12:42 PM
To: [EMAIL PROTECTED]
Cc: gcc@gcc.gnu.org
Subject: Re: compiling gcc-4.0.2 on solaris 9
Ok, here is my script (note I am in a directory with only the
script below when I execute the script below):
CC=cc /export/home/src/net/gnu/gcc-4.0.2/configure
gmake
I put:
printenv CC
echo $CC
which cc
in the script and only got output for the which cmd as
/opt/SUNWspro/bin/cc. I even reran the script with CC not set, just to make
sure. Thanks!
Hum... let's try the basic checks then:
- what is your configure shell?
- what is your version of GNU
PROTECTED] On Behalf Of Eric Botcazou
Sent: Tuesday, November 22, 2005 1:25 PM
To: [EMAIL PROTECTED]
Cc: gcc@gcc.gnu.org
Subject: Re: compiling gcc-4.0.2 on solaris 9
I put:
printenv CC
echo $CC
which cc
in the script and only got output for the which cmd as
/opt/SUNWspro/bin/cc. I even reran
Although I had #!/bin/sh at the beginning, it was taking my
SHELL as tcsh. I have stuck in (via notes) SHELL=/bin/ksh;export SHELL
and I am rebuilding it right now. Thanks!
Could you post the config.log file of the target libiberty?
--
Eric Botcazou
gcc-4.0.2 on solaris 9
Although I had #!/bin/sh at the beginning, it was taking my
SHELL as tcsh. I have stuck in (via notes) SHELL=/bin/ksh;export SHELL
and I am rebuilding it right now. Thanks!
Could you post the config.log file of the target libiberty?
--
Eric Botcazou
It is 4325 lines, should I just email it to you instead
of the whole group?
Yes, compressed.
--
Eric Botcazou
-4.0.2 on solaris 9
Although the compiler's executable is composed of 32-bit code, it can
generate 32 or 64 bit code, which is what I meant by both compilers.
Ah! Indeed, but you're going to further confuse the readers. :-)
I think the best terminology is 32-bit multilib compiler for
sparc-sun
CC to cc only. So, now the script is:
CC=cc
export CC
../gcc-4.0.2/configure
gmake bootstrap
Do not export CC and do not use a relative path:
CC=cc $absolute_path/configure ...
Also, the ask why I was using the flags I was. The only reference I found
to sparc where the
(NOTE: I originally posted this to gcc-help, but only got
one response that the sender said they had posted a similar
posting a while back and got no responses. So, I am reposting
the below to gcc in hopes that this might be a better place
to post this question.)
I am on:
SunOS hostname 5.9
On Fri, Nov 18, 2005 at 01:48:57PM -0500, Douglas B. Jones wrote:
I am on:
SunOS hostname 5.9 Generic_118558-14 sun4u sparc SUNW,Sun-Blade-1500.
I try to do a bootstrap with the following using gnu make 3.80:
mkdir objectdir;cd objectdir
CC=cc -xildoff -xarch=v9
export CC
Why are you
mkdir objectdir;cd objectdir
CC=cc -xildoff -xarch=v9
export CC
Why are you choosing those flags?
Probably because they are advertised on:
http://gcc.gnu.org/install/specific.html#sparc64-x-solaris2
Just do CC=cc, you will get both a 32-bit and a 64-bit compiler. What
seems to be
On Fri, Nov 18, 2005 at 09:17:11PM +0100, Eric Botcazou wrote:
mkdir objectdir;cd objectdir
CC=cc -xildoff -xarch=v9
export CC
Why are you choosing those flags?
Probably because they are advertised on:
http://gcc.gnu.org/install/specific.html#sparc64-x-solaris2
Just do CC=cc,
Also, sparc-sun-solaris2.9 doesn't mean 32-bit compiler, it means
build both compilers, defaulting to 32 bits.
No, the compiler is purely 32-bit, only the libraries are of both flavors.
--
Eric Botcazou
On Fri, Nov 18, 2005 at 09:35:28PM +0100, Eric Botcazou wrote:
Also, sparc-sun-solaris2.9 doesn't mean 32-bit compiler, it means
build both compilers, defaulting to 32 bits.
No, the compiler is purely 32-bit, only the libraries are of both flavors.
We are using the term in a differnent
Although the compiler's executable is composed of 32-bit code, it can
generate 32 or 64 bit code, which is what I meant by both compilers.
Ah! Indeed, but you're going to further confuse the readers. :-)
I think the best terminology is 32-bit multilib compiler for
sparc-sun-solaris and
17 matches
Mail list logo
