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

Bug#694595: marked as done (gcc-4.7: Starting with 4.7.2-10 breaks building LLVM/Clang Trunk)

Your message dated Wed, 08 May 2013 14:54:35 +0200
with message-id <518A4B0B.2010006@debian.org>
and subject line Re: Bug#694595: gcc-4.7: Starting with 4.7.2-10 breaks building LLVM/Clang Trunk
has caused the Debian Bug report #694595,
regarding gcc-4.7: Starting with 4.7.2-10 breaks building LLVM/Clang Trunk
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
694595: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694595
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: gcc-4.7
Version: 4.7.2-12
Severity: normal

Dear Maintainer,

Starting with 4.7.2-10 breaks building LLVM/Clang Trunk.

Building LLVM/Clang whether with a previous trunk build clang or using gcc to build clang now stands broken for the simple fact:

In file included from /home/mdriftmeyer/DeveloperProjects/LLVMProject/trunk/llvm/projects/compiler-rt/lib/asan/tests/asan_benchmarks_test.cc:15:
In file included from /home/mdriftmeyer/DeveloperProjects/LLVMProject/trunk/llvm/projects/compiler-rt/lib/asan/tests/asan_test_utils.h:19:
In file included from /home/mdriftmeyer/DeveloperProjects/LLVMProject/trunk/llvm/projects/compiler-rt/lib/asan/tests/asan_test_config.h:20:
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../include/c++/4.7/vector:60:
/usr/lib/gcc/x86_64-linux-gnu/4.7/../../../../include/c++/4.7/bits/stl_algobase.h:60:10: fatal error: 
      'bits/c++config.h' file not found
#include <bits/c++config.h>
         ^
In file included from /home/mdriftmeyer/DeveloperProjects/LLVMProject/trunk/llvm/projects/compiler-rt/lib/asan/tests/asan_test.cc:27:


This has been going on since 4.7.2-10 was introduced into Experimental. This breakage has occasionally occured since LLVM 2.9 trunk and I'm just making everyone aware that they need to make some updates either to both Debian's end and LLVM's reference end to the mappings where the project needs to look in Debian for the c++config.h file.

Since c++config.h is managed by gccxml-0.9 perhaps an update to this package can fix it?

/usr/share/gccxml-0.9/GCC/4.7/bits/c++config.h

Sincerely,

Marc J. Driftmeyer

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-rt-amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gcc-4.7 depends on:
pn  binutils        <none>
ii  cpp-4.7         4.7.2-12
ii  gcc-4.7-base    4.7.2-12
ii  libc6           2.16-0experimental1
ii  libgcc-4.7-dev  4.7.2-12
ii  libgmp10        2:5.0.5+dfsg-2
ii  libmpc2         0.9-4
ii  libmpfr4        3.1.0-5
ii  zlib1g          1:1.2.7.dfsg-13

Versions of packages gcc-4.7 recommends:
ii  libc6-dev  2.16-0experimental1

Versions of packages gcc-4.7 suggests:
pn  binutils-gold        <none>
pn  gcc-4.7-doc          <none>
ii  gcc-4.7-locales      4.7.2-12
pn  gcc-4.7-multilib     <none>
ii  libcloog-ppl0        0.15.11-4
pn  libgcc1-dbg          <none>
pn  libgomp1-dbg         <none>
pn  libitm1-dbg          <none>
pn  libmudflap0-4.7-dev  <none>
pn  libmudflap0-dbg      <none>
pn  libppl-c2            <none>
pn  libppl7              <none>
pn  libquadmath0-dbg     <none>

-- no debconf information

--- End Message ---
--- Begin Message --- 
tags 694595 + wontfix
thanks

Am 28.11.2012 08:21, schrieb Matthias Klose:
> nothing to do with gccxml, see #693240 for the background.

closing, newer llvm releases are aware of the multiarch location.

--- End Message ---
Reply to: