Bug 61639 - GCC 4.7.4 can't longer compile clang
Summary: GCC 4.7.4 can't longer compile clang
Status: RESOLVED INVALID
Alias: None
Product: gcc
Classification: Unclassified
Component: c++ (show other bugs)
Version: 4.7.4
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-28 15:53 UTC by Alexander Pyhalov
Modified: 2017-08-03 03:31 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed: 2015-03-25 00:00:00


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Pyhalov 2014-06-28 15:53:34 UTC
After updating GCC from 4.7.3 to 4.7.4 I can't longer compile Clang 3.3 (or 3.4.1) on OpenIndiana (illumos distribution).

While linking clang-check I receive the following error:

llvm[5]: Compiling CIndexCodeCompletion.cpp for Release+Asserts build (PIC)
llvm[5]: Linking Release+Asserts executable clang-check (without symbols)
Undefined                       first referenced
 symbol                             in file
vtable for clang::tooling::FrontendActionFactory* clang::tooling::newFrontendActionFactory<clang_check::ClangCheckActionFactory>(clang_check::ClangCheckActionFactory*, clang::tooling::SourceFileCallbacks*)::FrontendActionFactoryAdapter::ConsumerFactoryAdaptor /export/home/alp/srcs/oi-userland/components/clang/build/i86/tools/clang/tools/clang-check/Release+Asserts/ClangCheck.o
ld: fatal: symbol referencing errors. No output written to /export/home/alp/srcs/oi-userland/components/clang/build/i86/Release+Asserts/bin/clang-check
collect2: error: ld returned 1 exit status
make[5]: *** [/export/home/alp/srcs/oi-userland/components/clang/build/i86/Release+Asserts/bin/clang-check] Error 1
make[5]: Leaving directory `/export/home/alp/srcs/oi-userland/components/clang/build/i86/tools/clang/tools/clang-check'
make[4]: *** [clang-check/.makeall] Error 2

Everything works with GCC 4.7.3


$ gcc -v 
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/gcc/4.7/lib/gcc/i386-pc-solaris2.11/4.7.4/lto-wrapper
Target: i386-pc-solaris2.11
Configured with: /export/home/alp/srcs/oi-userland/components/gcc47/gcc-4.7.4/configure CC=/usr/gcc/4.7/bin/gcc CXX=/usr/gcc/4.7/bin/g++ F77=/usr/gcc/4.7/bin/gfortran FC=/usr/gcc/4.7/bin/gfortran CFLAGS='-g -O2' CXXFLAGS=' ' FFLAGS=' ' FCFLAGS= LDFLAGS=-m32 PKG_CONFIG_PATH=/usr/lib/pkgconfig --prefix=/usr/gcc/4.7 --mandir=/usr/gcc/4.7/share/man --bindir=/usr/gcc/4.7/bin --libdir=/usr/gcc/4.7/lib --sbindir=/usr/gcc/4.7/sbin --sbindir=/usr/gcc/4.7/bin --libdir=/usr/gcc/4.7/lib --libexecdir=/usr/gcc/4.7/lib --host i386-pc-solaris2.11 --build i386-pc-solaris2.11 --target i386-pc-solaris2.11 --with-boot-ldflags=-R/usr/gcc/4.7/lib --enable-plugins --enable-objc-gc --enable-languages=c,c++,fortran,lto,objc --enable-ld=no --with-build-time-tools=/usr/gnu/i386-pc-solaris2.11/bin --disable-libitm --with-gnu-as --with-as=/usr/bin/gas LDFLAGS=-R/usr/gcc/4.7/lib
Thread model: posix
gcc version 4.7.4 (GCC)
Comment 1 Alexander Pyhalov 2014-06-28 16:41:30 UTC
LLVM developers confirmed the issue exists on OSX whith gcc 4.7.4 (but not 4.8/4.9).
Comment 2 David Kredba 2014-06-29 07:12:25 UTC
The same affects Gentoo Gcc-4.7.4 and llvm-3.4.2.
Comment 3 Jakub Jelinek 2014-06-30 13:23:17 UTC
4.7.x is not supported anymore, so even if this was a bug in 4.7.4, it is not going to be fixed.
Comment 4 John Feltz 2014-07-30 13:55:30 UTC
This bug needs to be redefined as it also occurs with gcc-4.9.1 as well, but may not actually be a fault of gcc (on a Debian squeeze system with compiled gcc-4.9.1).
Comment 5 Marek Polacek 2015-03-25 15:43:03 UTC
Without a testcase there's nothing to do.
Comment 6 Eric Gallager 2017-08-03 03:31:56 UTC
(In reply to Marek Polacek from comment #5)
> Without a testcase there's nothing to do.

...besides close it, that is.