error when compiling gcc
Andrew Haley
aph@redhat.com
Fri Jul 31 09:11:00 GMT 2015
On 31/07/15 01:24, 纪æ wrote:
> Here is the output:
>
> gcc -v
>
> Using built-in specs.
> Target: x86_64-redhat-linux
> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> --infodir=/usr/share/info
> --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap
> --enable-shared --enable-threads=posix --enable-checking=release
> --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions
> --enable-gnu-unique-object
> --enable-languages=c,c++,objc,obj-c++,java,fortran,ada
> --enable-java-awt=gtk --disable-dssi
> --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre
> --enable-libgcj-multifile --enable-java-maintainer-mode
> --with-ecj-jar=/usr/share/java/eclipse-ecj.jar
> --disable-libjava-multilib --with-ppl --with-cloog --with-tune=generic
> --with-arch_32=i686 --build=x86_64-redhat-linux
> Thread model: posix
> gcc version 4.4.7 20120313 (Red Hat 4.4.7-11) (GCC)
>
>
> å¨ 2015/07/30 17:31, Andrew Haley åé:
>> On 30/07/15 10:16, 纪æ wrote:
>>> I downloaded gcc-4.9.3, and wanted to compile it on my Centos 6.5
>>> box. I first intalled the prerequisites, isl-0.14, mpc-0.8.1, gmp-4.3.2,
>>> mpfr-2.4.2, and cloog-0.18.3, then I ran configure and specified the
>>> directory of the above packages. When I ran make, I got the following
>>> errors:
>>>
>>> ../../../libitm/config/linux/rwlock.cc: In member function âbool
>>> GTM::gtm_rwlock::write_lock_generic(GTM::gtm_thread*)â:
>>> ../../../libitm/config/linux/rwlock.cc:160:16: error: âtypeofâ was not
>>> declared in this scope
>>> != ~(typeof it->shared_state)0)
>>> ^
>>> ../../../libitm/config/linux/rwlock.cc:160:23: error: expected â)â
>>> before âitâ
>>> != ~(typeof it->shared_state)0)
>>> ^
>>> ../../../libitm/config/linux/rwlock.cc:176:5: error: expected â)â before
>>> â}â token
>>> }
>>> ^
>>>
>>>
>>> Anyone can help me out on this?
This is extremely odd. I don't know why this doesn't work for you.
It may be possible for someone to help if you provide full details
about how you configured and built GCC.
Andrew.
More information about the Gcc-help
mailing list