** Changed in: llvm-toolchain-3.4 (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: llvm-toolchain-3.4 (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
How can this patch (or the backport) apply for a SRU update, how it is
possible to add a SRU maintainer to this thread?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to llvm-toolchain-3.4 in
Ubuntu.
The package needs to be build with gcc5.2 to have the correct (dualabi)
symbols in the library.
Therefore the back port to 15.10 is definitely needed! Otherwise 3th
parity libs cannot link against the clang compiler (what we definitely
need)
In generall all librarys on a dualabi system
Debian testing is not affected i use it too
On 10.11.2015 17:57, Sebastien Bacher wrote:
> Debian as well, could you report the bug to the Debian BTS as well?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The rexexp checks for availible compiler versions.
Theregexp checks for X.X.X i changed the regexpt to X.X
The fallback was to use gcc 4.9 which was availible on ubuntu.
The new gcc is 5.2, therefore now the new regexpt matches.
I do not checked the originial debian rules from the debian
On 10.11.2015 18:17, Sebastien Bacher wrote:
> Could you also maybe explain what you changed in the regexp and why and
> how that resolves the issue?
>
additon:
By changing the regexpt the package got now compiled with gcc5.2 instead
of 4.9
--
You received this bug notification because you are
Just checked debian testing does a simliar change with a slighly
different reg-exp:
old:
http://http.debian.net/debian/pool/main/l/llvm-toolchain-3.4/llvm-toolchain-3.4_3.4.2-13.debian.tar.xz
new:
mitko: it seems the i386 does not finish because the build-servers are too
slow, however the x64 build is finished.
I have no clue howto tell the buildserver to wait longer for the result for the
i386 build. of the llvm-3.7. But i recomment we move this 3.7 discussion to the
other bugreport
--
I just uploaded a patched version of the 3.7 to my personal PPA, the 3.7 has
the same issue than this 3.4.
Please try the llvm-toolchain-3.7 1:3.7-2ubuntu2 from my rock-ppa if this helps
you create a bug report on the 3.7 and i will add the patch there also,
hopefully the package maintainer
If i added this somehow wrong please let me know. i provided a solution which
should be correct to add it to mainstream.
This patch really complicates our development or our projects on a Ubuntu 15.10
target.
Moreover the proposed patch should be review able by any Ubuntu
maintainer, the
mitko: i created a issue on the llvm-3.7 and attached the patch:
https://bugs.launchpad.net/ubuntu/+source/llvm-
toolchain-3.7/+bug/1511128
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to llvm-toolchain-3.4 in
Ubuntu.
Is there anywhere a maintainer around who can give some recommendations
or review the patch?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to llvm-toolchain-3.4 in
Ubuntu.
https://bugs.launchpad.net/bugs/1501300
Title:
Wily
I just created a patch which solved the problem.
** Patch added: "wily-using-right-gcc.patch"
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1501300/+attachment/4495448/+files/wily-using-right-gcc.patch
--
You received this bug notification because you are a member of
I just created a patch which solved the problem.
** Patch added: "wily-using-right-gcc.patch"
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1501300/+attachment/4495447/+files/wily-using-right-gcc.patch
--
You received this bug notification because you are a member of
I created a PPA package which builds on launchpad and successfully got
linked in my case:
https://launchpad.net/~matthias-l/+archive/ubuntu/rock-ppa/+packages
The most relevant change was that i changed the default compiler to
gcc-5 instead of a autodetection.
--
You received this bug
Public bug reported:
This packages does not contain any __cxx11 symbols when installed. This causes
the problem that user-space applications cannot link successfully to it.
Recompile the (untouched) dpkg source package on the same machine and
installing it solved the problem.
There seems
16 matches
Mail list logo
