Packages for Debian Wheezy
Norbert Lange
npl at chello.at
Mon Sep 29 21:27:57 UTC 2014
Am 29.09.2014, 21:54 Uhr, schrieb Sylvestre Ledru <sylvestre at debian.org>:
> On 29/09/2014 21:25, Norbert Lange wrote:
>> Hi,
>>
>> I wonder is there is anyone working on getting the Packages for Wheezy
>> updated?
>>
> Not that I am aware :)
Are there some magic chants to get this changed?
>> *) I tried a crude hack by fixing the problematic libstdc++ header
>> (trying to get it compiling on a clean Wheezy system) - but the
>> package only compiled llvm not clang. The changed rules from the 3.4.2
>> Jenkins job
>> (http://llvm-jenkins.debian.net/job/llvm-toolchain-wheezy-3.4-source/)
>> Since I havent figured out how to use multiple cores this is a rather
>> timeconsuming process
> export DEB_BUILD_OPTIONS=parallel=XX
Ok, thanks
>> *) I tried backporting gcc 4.7.4 but Id have to spend more time on on
>> it and I am not sure the result would be different to the above attempt.
> It would probably fix it but gcc on wheezy is hard to backport!
>
> S
>
isl and/or cloog are outdated aswell. Im just surprised that the package
only built llvm and dint say anything about an error for clang.
I managed to compile the gcc 4.7.4 package without much changes (except
removing x32 options), I think I would just have to fix the packages +
depencies.
If I manage to get gcc-4.7.4 backported (and thus hopefully clang built)
would this allow you to offer the llvm binaries on your site, or is using
a backported gcc against some rules?
I think there arent any ABI changes between 4.7.2 and 4.7.4, so the
compiled clang should still work with wheezy libraries
More information about the Pkg-llvm-team
mailing list