help-gplusplus
[Top][All Lists]
Advanced

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

RE: glibc-2.7 and gcc-4.2.2 install on redhat 3 u 9 - x86_64


From: Lamont, Brian-p3354c
Subject: RE: glibc-2.7 and gcc-4.2.2 install on redhat 3 u 9 - x86_64
Date: Thu, 17 Apr 2008 07:59:47 -0700

This install appeared to complete successfully, however, compiling a simple 
"hello world" doesn't produce any output.   The engineer testing his source 
code is getting errors and I've asked for them, and will send upon receiving 
them.  I did NOT set env CC=cc (syntax ??).  The readme talks of settings the 
CC variable.  Will not doing this allow a successful configure, but bad 
compilation?

Are there any special configure options building gcc on redhat linux?  
Comparing mine with a  Redhat 4 system below.  I've been browsing through the 
options but really unsure if any of them are needed, but some do raise concern.


This is the configure from the problem system -- redhat 3 updt 9.
-----------------------------------------------------------------
<sys-root> gcc -v
Target: x86_64-redhat-linux
../gcc-4.2.2/configure --host=x86_64-redhat-linux --enable-shared 
--disable-multilib
Thread_model: posix


This gcc is from the Redhat 4 system used as comparison
--------------------------------------------------------
[root@sys ~]# gcc -v
Reading specs from /usr/lib/gcc/x86_64-redhat-linux/3.4.6/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man 
--infodir=/usr/share/info --enable-shared --enable-threads=posix 
--disable-checking --with-system-zlib --enable-__cxa_atexit 
--disable-libunwind-exceptions --enable-java-awt=gtk --host=x86_64-redhat-linux
Thread model: posix
gcc version 3.4.6 20060404 (Red Hat 3.4.6-8)


-----Original Message-----
From: FÖLDY Lajos [mailto:foldy@rmki.kfki.hu] 
Sent: Tuesday, April 15, 2008 12:48 PM
To: Lamont, Brian-p3354c
Subject: RE: glibc-2.7 and gcc-4.2.2 install on redhat 3 u 9 - x86_64


OK, make sure that the --prefix=... dir. does not point into the source tree. I 
usually use /usr/local/gcc-4.2.2.

good luck,
lajos



On Tue, 15 Apr 2008, Lamont, Brian-p3354c wrote:

> I don't believe I did.  I was in a different dir building glibc, which 
> failed, but not gcc.   Will try it now.
>
> -----Original Message-----
> From: FÖLDY Lajos [mailto:foldy@rmki.kfki.hu]
> Sent: Tuesday, April 15, 2008 12:28 PM
> To: Lamont, Brian-p3354c
> Subject: RE: glibc-2.7 and gcc-4.2.2 install on redhat 3 u 9 - x86_64
>
>
>
> On Tue, 15 Apr 2008, Lamont, Brian-p3354c wrote:
>
>>
>> gcc -v
>> ---------
>> Using built-in specs.
>> Target: x86_64-unknown-linux-gnu
>>
>> Configured with: /prj/dbptools/pkgs/gcc-4.2.2/configure
>> --with-gcc-version-trigger=/prj/dbptools/pkgs/gcc-4.2.2/gcc/
>> --host=x86_64-unknown-linux-gnu
>> --bindir=/prj/dbptools/pkgs/gcc-4.2.2/bin
>> --libdir=/prj/dbptools/pkgs/gcc-4.2.2/gcc --disable-multilib 
>> --enable-shared Thread model: posix gcc version 4.2.2
>>
>>
>
> Have you built GCC in the source directory? That is not supported and 
> ususally will not work. One builds GCC as:
>
> - mkdir /tmp/build  # somewhere out of the source tree
> - cd /tmp/build
> - /source/gcc-4.2.2/configure --prefix=/prj/dbptools/pkgs/gcc-4.2.2
>   --host=x86_64-unknown-linux-gnu --disable-multilib --enable-shared
>
> regards,
> lajos
>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]