Let's wontfix at least for now, build-deps can be from universe these
days
** Changed in: libclc (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libclc in Ubuntu.
https://bugs.launchpad.net/bugs/141
any update on this?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libclc in Ubuntu.
https://bugs.launchpad.net/bugs/1412441
Title:
[MIR] libclc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+
no, clang is not going to main before it supports the same libstdc++ ABI
as g++
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libclc in Ubuntu.
https://bugs.launchpad.net/bugs/1412441
Title:
[MIR] libclc
To manage notifications about this b
Any news? Today is xenial feature freeze.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libclc in Ubuntu.
https://bugs.launchpad.net/bugs/1412441
Title:
[MIR] libclc
To manage notifications about this bug go to:
https://bugs.launchpad.net/u
OK, so we need to both update to llvm-3.8 in xenial and switch libclc to
llvm-3.8.
I'll assign this MIR to doko, because he understands the intricacies of
the toolkits better than me.
** Changed in: libclc (Ubuntu)
Assignee: Timo Aaltonen (tjaalton) => Matthias Klose (doko)
--
You received
We've decided (separately) on 3.8 as the default in 16.04.
And libclc doesn't build with g++, needs clang.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libclc in Ubuntu.
https://bugs.launchpad.net/bugs/1412441
Title:
[MIR] libclc
To manag
No, llvm-3.8 doesn't help here. I'm trying to avoid xenial having two
llvms in main. Right now our default, supported llvm is llvm-3.6. So
either we switch libclc to use our supported version, or we switch our
supported version to be the one libclc uses.
--
You received this bug notification b
libclc builds fine with llvm-3.8, is that sufficient?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libclc in Ubuntu.
https://bugs.launchpad.net/bugs/1412441
Title:
[MIR] libclc
To manage notifications about this bug go to:
https://bugs.lau
from my point of view having a c++ compiler in main which currently does
not support the new libstdc++ ABI is not wanted. Could you investigate
to build using g++? At least there is a configure option --with-cxx-
compiler
--
You received this bug notification because you are a member of Ubuntu-X,
llvm 3.8 is in xenial proposed and builds fine everywhere now.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libclc in Ubuntu.
https://bugs.launchpad.net/bugs/1412441
Title:
[MIR] libclc
To manage notifications about this bug go to:
https:/
llvm-3.7 is not our default in xenial yet. So either libclc should be
switched to use 3.6 or our default should be updated to 3.7.
Also, looks like clang isn't technically in main yet. It's source
package (llvm-toolchain-3.6) is. But it hasn't been promoted yet. I'd
have to go see if that was
The fixed llvm is on proposed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libclc in Ubuntu.
https://bugs.launchpad.net/bugs/1412441
Title:
[MIR] libclc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
I would appreciate to wait a little bit, I asked to Sylvestre (the
Debian Developer and Maintainer of llvm) an ack about my changes.
Please hold on.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libclc in Ubuntu.
https://bugs.launchpad.net/bug
llvm 3.7 now builds fine on all architectures, libclc can be moved to
main with no changes.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libclc in Ubuntu.
https://bugs.launchpad.net/bugs/1412441
Title:
[MIR] libclc
To manage notifications
I don't see llvm3.8 in proposed.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libclc in Ubuntu.
https://bugs.launchpad.net/bugs/1412441
Title:
[MIR] libclc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+so
llvm3.7 doesn't build on all architectures. please ensure that it builds
with llvm3.8 (currently only in -proposed). but llvm3.6 should be fine
ok for now, if it will build with 3.8.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libclc in Ubun
Xenial has an updated libclc, synced with the current Debian package and
built with llvm 3.7. What is still missing here? Moving libclc from
universe to main?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libclc in Ubuntu.
https://bugs.launchpa
builds fine with llvm-3.5 but not our default which is 3.6, probably
needs updates to libclc..
** Changed in: libclc (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: libclc (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: libclc (Ubuntu)
Assignee: Maarten Lankhorst
Looks mostly fine. But it doesn't re-build on current vivid?
/usr/lib/llvm-3.6/bin/llvm-as: ./generic/lib/shared/vload_impl.ll:124:6: error:
unexpected type in metadata definition
!1 = metadata !{metadata !"char", metadata !5}
^
Makefile:244: recipe for target 'nvptx--nvidiacl/lib/shared/vl
19 matches
Mail list logo
