llvm dev - Dec 2013 - [LLVMdev] [lldb-dev] [cfe-dev] http://llvm.org/apt/ with 'old' gcc: Request for comments

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
> bootstrap.
>
> Cheers,
> --
> Arnaud
>
>
>
> On Wed, Dec 25, 2013 at 4:06 PM, Sylvestre Ledru <sylvestre at
debian.org
> <mailto:sylvestre at debian.org>> wrote:
>
>     Hello,
>
>     Just a quick refresh, on llvm.org/apt/ <http://llvm.org/apt/>
[1],
>     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
>     [2] 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. [3]
>     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 [4] 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?
>
>     Thanks,
>     Sylvestre
>
>     [1] http://llvm.org/apt/
>     [2] http://llvm-jenkins.debian.net/
>     [3] For example, currently, lldb fails to build with
>    
/tmp/buildd/llvm-toolchain-snapshot-3.5~svn197872/tools/lldb/source/../include/lldb/Utility/Iterable.h:197:22:
>     sorry, unimplemented: non-static data member initializers
>    
/tmp/buildd/llvm-toolchain-snapshot-3.5~svn197872/tools/lldb/source/../include/lldb/Utility/Iterable.h:197:22:
>     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=18077
>     [4] http://llvm.org/bugs/show_bug.cgi?id=18272
>
>     _______________________________________________
>     cfe-dev mailing list
>     cfe-dev at cs.uiuc.edu <mailto:cfe-dev at cs.uiuc.edu>
>     http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20131226/6467efd7/attachment.html>

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.

Cheers,
--
Arnaud


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
> bootstrap.
>
>    Cheers,
> --
> Arnaud
>
>
>
> On Wed, Dec 25, 2013 at 4:06 PM, Sylvestre Ledru <sylvestre at
debian.org>wrote:
>
>> Hello,
>>
>> Just a quick refresh, on llvm.org/apt/ [1], 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
>> [2] 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. [3]
>> 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 [4] 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?
>>
>> Thanks,
>> Sylvestre
>>
>> [1] http://llvm.org/apt/
>> [2] http://llvm-jenkins.debian.net/
>> [3] For example, currently, lldb fails to build with
>>
>>
/tmp/buildd/llvm-toolchain-snapshot-3.5~svn197872/tools/lldb/source/../include/lldb/Utility/Iterable.h:197:22:
>> sorry, unimplemented: non-static data member initializers
>>
>>
/tmp/buildd/llvm-toolchain-snapshot-3.5~svn197872/tools/lldb/source/../include/lldb/Utility/Iterable.h:197:22:
>> 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=18077
>> [4] http://llvm.org/bugs/show_bug.cgi?id=18272
>>
>> _______________________________________________
>> cfe-dev mailing list
>> cfe-dev at cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20131226/800f9aba/attachment.html>

On 12/27/13 02:36 AM, Arnaud Allard de Grandmaison
wrote:
> 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.
Seems dangerous and this isn't Windows - Distro and users should be able 
to reproduce the build from sources