[cfe-dev] http://llvm.org/apt/ with 'old' gcc: Request for comments
Arnaud Allard de Grandmaison
arnaud.adegm at gmail.com
Thu Dec 26 11:36:17 PST 2013
Wouldn't it be possible to fetch some binaries for the 3.4 compiler ? I
agree this is not as-elegant as you may want it, but this is all about
seeding the very first build. This inelegant step can be dropped as soon as
you have a shiny new clang-3.5 which you would be using to bootstrap later
snapshots / releases.
On Thu, Dec 26, 2013 at 3:59 PM, Sylvestre Ledru <sylvestre at debian.org>wrote:
> After some thinking on this idea, it would not work because I need / want
> to use Debian/Ubuntu package to do the build and clang 3.4 is not built on
> these architecture :(
> So, if I bootstrap clang 3.4, I will have a dependency on libstdc++ 4.8...
> On 25/12/2013 22:23, Arnaud Allard de Grandmaison wrote:
> Hi Sylvestre,
> The easiest is probably to have a dependency to (and use) clang-3.4 to
> On Wed, Dec 25, 2013 at 4:06 PM, Sylvestre Ledru <sylvestre at debian.org>wrote:
>> Just a quick refresh, on llvm.org/apt/ , I am rebuilding the sources
>> of LLVM to create snapshot packages for the stable branches
>> and development branches (currently, 3.4, in the hope of point releases
>> and 3.5). This currently targets 2 releases of Debian and 4 of Ubuntu
>>  and the llvm
>> toolchain is built using the compiler shipped with the distribution.
>> Following the recent discussions on the usage of C+11, we have now/soon
>> a requirement on having a recent and C++11 compiler. 
>> That requires a recent version of gcc (for example, 4.6 is not working).
>> Unfortunately, more recent versions are not available in Debian wheezy
>> (current stable) or Ubuntu precise (an Ubuntu LTS).
>> The usage of a backported version of gcc is not really feasible because
>> it would trigger a dependency on libstdc++ 4.8  and the installation
>> by the user
>> of the backported gcc.
>> For now, the obvious solution would be to drop the support of these
>> releases but there are still many users of these distributions.
>> Any suggestions? Static linkage of libstdc++? Usage of libc++? Usage of
>> clang 3.4 to bootstrap them?
>>  http://llvm.org/apt/
>>  http://llvm-jenkins.debian.net/
>>  For example, currently, lldb fails to build with
>> sorry, unimplemented: non-static data member initializers
>> error: 'constexpr' needed for in-class initialization of static data
>> member 'm_mutex' of non-integral type
>> or fails to link with:
>>  http://llvm.org/bugs/show_bug.cgi?id=18272
>> cfe-dev mailing list
>> cfe-dev at cs.uiuc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev