** Description changed:
+ [Impact]
+
+ * with gcc-5 default, and llvm-3.4 built with the gcc-4.9, people can't
+ link programs using cxx11 support
+
+ [Test Case]
+
+ * compile a program using cxx11 e.g. using boost libraries
+
+ [Regression Potential]
+
+ * llvm-3.4 is a compiler, and the ch
** Changed in: llvm-toolchain-3.4 (Ubuntu Wily)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501300
Title:
Wily (15.10) this package got not compiled with __cxx1
backported + uploaded the mentioned commit - this bug probably needs SRU
information per comment #26 before it'll be accepted though.
thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501300
Tit
looks ok for a SRU
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501300
Title:
Wily (15.10) this package got not compiled with __cxx11 support
To manage notifications about this bug go to:
https:/
** Also affects: llvm-toolchain-3.4 (Ubuntu Wily)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501300
Title:
Wily (15.10) this package got not compiled
In order for this to be SRUed to Wily, you need to make the bug
compliant with https://wiki.ubuntu.com/StableReleaseUpdates (Please add
a rational, test case, and regression potential to the description of
this bug.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Patch removed: "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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** 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
Bugs, which is subscribed to Ubuntu.
https://bug
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501300
Title:
Wily (15.10) this
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 (>=gcc5.2)
debdiff to backport if you want to SRU the change
http://anonscm.debian.org/viewvc/pkg-llvm/llvm-toolchain/branches/3.4/debian/rules?r1=1456&r2=1610
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/150130
oh, right, thanks for the details
-16 from Debian has been synced to current Ubuntu
https://launchpad.net/ubuntu/+source/llvm-toolchain-3.4/1:3.4.2-16
Unsure what to do about 15.10, the current package is built with gcc 4.9
and I'm unsure what's the impact of building with gcc5 and if that's
fine
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:
http://http.debian.net/debian/pool/main/l/llvm-toolchain-3.4/llvm-toolchain-3.4_3.4.2-16.debian.tar.x
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 project.
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 a
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Could you also maybe explain what you changed in the regexp and why and
how that resolves the issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501300
Title:
Wily (15.10) this package got not co
Thank you for your bug report. it seems like the change could apply to
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501300
Title:
Alright, I'll post there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501300
Title:
Wily (15.10) this package got not compiled with __cxx11 support
To manage notifications about this bug go to:
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
--
Thanks, Matthias. Your PPA still hasn't compiled the package. Once its
done I will try it and let you know. I'm fairly confident it will work
just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501300
Title
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 will
I might be hitting the same or at least a related bug: I am using clang
3.7 to compile an application that itself uses libclang3.7 to do some
C++ parsing. I get unresolved symbol errors from the linker. Namely this
one single error, many times:
undefined reference to `clang::NamedDecl::getQualifie
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 problem
** Changed in: llvm-toolchain-3.4 (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501300
Title:
Wily (15.10) this package got not compiled with __cxx11 sup
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501300
Title:
Wily (15.10) this package got not compiled w
The attachment "wily-using-right-gcc.patch" seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag,
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 Ubu
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 Ubu
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 notificat
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: llvm-toolchain-3.4 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501300
Same here. Would be nice to get a fix for this before the release
happens...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501300
Title:
Wily (15.10) this package got not compiled with __cxx11 supp
33 matches
Mail list logo
