graphics/mtpaint: move to gtk+3, remove llvm-10 -fno-common workaround

2021-06-09 Thread Charlene Wendling
Hi, Recently, i brought an update for mtpaint, and fixing the build for a -fno-common patched llvm-10, that needs to be removed now [0]. I'm proposing to move mtpaint to gtk+3 while here, since we are encouraged to move to gtk+3 after the final gtk+2 update [1]. I totally missed that new fe

LLVM 10: build failures on amd64 2020-08-20

2020-08-21 Thread Christian Weisgerber
The remaining build failures on amd64 due to the LLVM 10 update: devel/py-llvmlite,python3 needs update to 0.34.0 productivity/aqbanking Logs: http://build-failures.rhaalovely.net/amd64/2020-08-07/ -- Christian "naddy" Weisgerber na...@mips.inka.de

Re: LLVM 10: build failures on amd64 2020-08-18

2020-08-19 Thread Aisha Tammy
On 8/19/20 4:07 PM, Christian Weisgerber wrote: > The remaining build failures on amd64 due to the LLVM 10 update: > > devel/py-llvmlite,python3 needs update to 0.34.0 fwiw llvmlite and numba(though its not in ports) have been a bit problematic on other systems too gentoo dis

Re: LLVM 10: build failures on amd64 2020-08-18

2020-08-19 Thread Stuart Henderson
On 2020/08/19 18:22, Aisha Tammy wrote: > On 8/19/20 4:07 PM, Christian Weisgerber wrote: > > The remaining build failures on amd64 due to the LLVM 10 update: > > > > devel/py-llvmlite,python3 needs update to 0.34.0 > > fwiw llvmlite and numba(though its no

LLVM 10: build failures on amd64 2020-08-18

2020-08-19 Thread Christian Weisgerber
The remaining build failures on amd64 due to the LLVM 10 update: devel/py-llvmlite,python3 needs update to 0.34.0 games/fs2open productivity/aqbanking Logs: http://build-failures.rhaalovely.net/amd64/2020-08-07/ -- Christian "naddy" Weisgerber na...@mips.inka.de

LLVM 10: build failures on amd64 2020-08-17

2020-08-18 Thread Christian Weisgerber
The remaining build failures on amd64 due to the LLVM 10 update: devel/py-llvmlite,python3 needs update to 0.34.0 games/fs2open print/scribus productivity/aqbanking Logs: http://build-failures.rhaalovely.net/amd64/2020-08-07/ -- Christian "naddy" Weisgerber

Re: LLVM 10: build failures on amd64 2020-08-13

2020-08-17 Thread Rafael Sadowski
On Mon Aug 17, 2020 at 04:01:28PM +0200, Christian Weisgerber wrote: > Rafael Sadowski: > > > > The remaining build failures on amd64 due to the LLVM 10 update: > > > devel/rttr > > > > fixed > > I still get the same build errors. I was too fast

Re: LLVM 10: build failures on amd64 2020-08-13

2020-08-17 Thread Christian Weisgerber
Rafael Sadowski: > > The remaining build failures on amd64 due to the LLVM 10 update: > > devel/rttr > > fixed I still get the same build errors. -- Christian "naddy" Weisgerber na...@mips.inka.de

Re: LLVM 10: build failures on amd64 2020-08-13

2020-08-16 Thread Rafael Sadowski
On Fri Aug 14, 2020 at 09:51:14PM +0200, Christian Weisgerber wrote: > The remaining build failures on amd64 due to the LLVM 10 update: > > devel/rttr fixed > games/fs2open > print/scribus OK? Index: Makefile ===

LLVM 10: build failures on amd64 2020-08-13

2020-08-14 Thread Christian Weisgerber
The remaining build failures on amd64 due to the LLVM 10 update: devel/py-llvmlite,python3 needs update to 0.34.0 devel/rttr games/fs2open print/scribus productivity/aqbanking x11/gnustep/back\ -fuse-ld=bfd not passed through x11/gnustep/renaissance / sebastia@ is

Re: missing ${COMPILER_LIBCXX} in WANTLIB exposed by llvm 10

2020-08-13 Thread Antoine Jacoutot
On Thu, Aug 13, 2020 at 05:43:19PM +0100, Stuart Henderson wrote: > On 2020/08/13 17:56, Antoine Jacoutot wrote: > > On Thu, Aug 13, 2020 at 05:45:18PM +0200, Matthieu Herrb wrote: > > > Hi, > > > > > > while moving my machines past the llvm10 upgrade, I've found that > > > some packages have not

Re: missing ${COMPILER_LIBCXX} in WANTLIB exposed by llvm 10

2020-08-13 Thread Stuart Henderson
On 2020/08/13 17:56, Antoine Jacoutot wrote: > On Thu, Aug 13, 2020 at 05:45:18PM +0200, Matthieu Herrb wrote: > > Hi, > > > > while moving my machines past the llvm10 upgrade, I've found that > > some packages have not been automatically upgraded and still need > > libc++abi.so.2.1 and libc++.so.

Re: missing ${COMPILER_LIBCXX} in WANTLIB exposed by llvm 10

2020-08-13 Thread Antoine Jacoutot
On Thu, Aug 13, 2020 at 05:45:18PM +0200, Matthieu Herrb wrote: > Hi, > > while moving my machines past the llvm10 upgrade, I've found that > some packages have not been automatically upgraded and still need > libc++abi.so.2.1 and libc++.so.4.0 even though they don't appear > anywhere in WANTLIB.

missing ${COMPILER_LIBCXX} in WANTLIB exposed by llvm 10

2020-08-13 Thread Matthieu Herrb
Hi, while moving my machines past the llvm10 upgrade, I've found that some packages have not been automatically upgraded and still need libc++abi.so.2.1 and libc++.so.4.0 even though they don't appear anywhere in WANTLIB. On my main machine I gave up after patching the 2 ports below and removed a

Re: i386/LLVM 10

2020-08-13 Thread Jeremie Courreges-Anglas
On Thu, Aug 13 2020, Christian Weisgerber wrote: > Jeremie Courreges-Anglas: > >> I don't have an i386 ports test rig. naddy, do you still run i386 test >> builds? Else I can just push it in the tree for sthen to pick up in >> the next bulk, it won't make things worse... > > I've installed i386

Re: i386/LLVM 10

2020-08-13 Thread Christian Weisgerber
Jeremie Courreges-Anglas: > I don't have an i386 ports test rig. naddy, do you still run i386 test > builds? Else I can just push it in the tree for sthen to pick up in > the next bulk, it won't make things worse... I've installed i386 on my spare APU2. I can't run full builds there, but I can

Re: i386/LLVM 10

2020-08-13 Thread Mark Kettenis
gt;>>>> ../../JavaScriptCore/release/libjscore.a > > > > We've seen that error before. That was in textproc/wkhtmltopdf, > > which builds its own included copy of Qt4 WebKit. Back then, removing > > -ffunction-sections from the compiler flags fixed it. > > >

Re: i386/LLVM 10

2020-08-13 Thread Jeremie Courreges-Anglas
t; which builds its own included copy of Qt4 WebKit. Back then, removing > -ffunction-sections from the compiler flags fixed it. > > Now the problem is back, in both wkhtmltopdf and qt4, without > -ffunction-sections. I thought maybe LLVM 10 had enabled this > option by default, but it

Re: i386/LLVM 10

2020-08-12 Thread Christian Weisgerber
flags fixed it. Now the problem is back, in both wkhtmltopdf and qt4, without -ffunction-sections. I thought maybe LLVM 10 had enabled this option by default, but it doesn't look like it. -fno-function-sections also has no effect. I don't understand what's going on. There is a s

Re: i386/LLVM 10

2020-08-12 Thread Christian Weisgerber
On 2020-08-12, Stuart Henderson wrote: >> print/scribus > /pobj/scribus-1.5.5/scribus-1.5.5/scribus/third_party/lib2geom/path.h:260:11: > error: no viable overloaded '=' This one is probably an easy fix for somebody who actually knows C++. The problem is in an ancient embedded copy of lib2geom

Re: i386/LLVM 10

2020-08-12 Thread Jonathan Gray
2020/08/10 "Don't use backtrace/backtrace_symbols, fixes the build with llvm10" > > > databases/pgadmin3 > ld: error: utils/sshTunnel.o: unable to find library from dependent library > specifier: Ws2_32.lib fixed by jca 2020/08/08 "Only link with Ws2_32.lib whe

Re: i386/LLVM 10

2020-08-12 Thread Stuart Henderson
On 2020/08/10 20:57, Stuart Henderson wrote: > > With MariaDB fixed (and maybe something else) we can reach more failures. > Build is still running, thought I would send this first batch now rather > than wait 14h until it finished plus however long it takes me to send > mail. Here's how it look

Re: LLVM 10: net/libtorrent-rasterbar

2020-08-10 Thread Nam Nguyen
Jeremie Courreges-Anglas writes: > On Thu, Aug 06 2020, Nam Nguyen wrote: > Done, I have committed your diff + a few other tweaks yesterday. I have > pointed this bug and your diff to the folks who handled the LLVM update > in base. There have been discussions about moving to llvm-10.0.1. > Th

Re: i386/LLVM 10

2020-08-10 Thread Stuart Henderson
On 2020/08/08 19:54, Christian Weisgerber wrote: > On 2020-08-08, Stuart Henderson wrote: > > > Updated failure logs. Many of these are broken on amd64 too, but > > some are not. > > # comments > > > built packages > > build failures: 23 > > databases/mariadb > > databases/pgadmin3 # a

Re: i386/LLVM 10

2020-08-08 Thread Charlene Wendling
On Sat, 08 Aug 2020 23:16:09 +0200 Jeremie Courreges-Anglas wrote: > > < sthen> ld.lld: > error: /pobj/webkitgtk4-2.28.4/build-i386/lib/libjavascriptcoregtk-4.0.so: > undefined reference to WTF::Optional > JSC::parse(char const*) > > cwen did hit this too on powerpc when it was switched to clang

Re: sysutils/xxhash (was: Re: i386/LLVM 10)

2020-08-08 Thread Bjorn Ketelaars
On Sun 09/08/2020 00:10, Jeremie Courreges-Anglas wrote: > > ==> failures/sysutils/xxhash.log <== > > Hunk #1 succeeded at 447. > > done > > ===> Compiler link: clang -> /usr/bin/clang > > ===> Compiler link: clang++ -> /usr/bin/clang++ > > ===> Compiler link: cc -> /usr/bin/cc > > ===> Compile

Re: LLVM 10: net/libtorrent-rasterbar

2020-08-08 Thread Jeremie Courreges-Anglas
On Thu, Aug 06 2020, Nam Nguyen wrote: > This diff backports a 10.0.1 fix for an llvm crash while compiling > net/libtorrent-rasterbar web_connection-base.cpp and > bt_peer_connection.cpp. > > I compiled an earlier version of jca@'s update to devel/llvm 10 with > de

sysutils/xxhash (was: Re: i386/LLVM 10)

2020-08-08 Thread Jeremie Courreges-Anglas
> ==> failures/sysutils/xxhash.log <== > Hunk #1 succeeded at 447. > done > ===> Compiler link: clang -> /usr/bin/clang > ===> Compiler link: clang++ -> /usr/bin/clang++ > ===> Compiler link: cc -> /usr/bin/cc > ===> Compiler link: c++ -> /usr/bin/c++ > ===> Generating configure for xxhash-0.8

Re: i386/LLVM 10

2020-08-08 Thread Jeremie Courreges-Anglas
< sthen> ld.lld: error: /pobj/webkitgtk4-2.28.4/build-i386/lib/libjavascriptcoregtk-4.0.so: undefined reference to WTF::Optional JSC::parse(char const*) cwen did hit this too on powerpc when it was switched to clang, I propose to extend the workaround to all archs. Disclaimer: diff not tested

Re: i386/LLVM 10

2020-08-08 Thread Christian Weisgerber
On 2020-08-08, Stuart Henderson wrote: > Updated failure logs. Many of these are broken on amd64 too, but > some are not. # comments > built packages > build failures: 23 > databases/mariadb > databases/pgadmin3# amd64 > devel/geany > devel/py-llvmlite # amd64 > devel/rt

Re: i386/LLVM 10

2020-08-06 Thread Jonathan Gray
On Thu, Aug 06, 2020 at 01:00:04PM +0100, Stuart Henderson wrote: > On 2020/08/06 03:22, Jonathan Gray wrote: > > On Tue, Aug 04, 2020 at 07:40:45PM -0400, George Koehler wrote: > > > On Tue, 4 Aug 2020 23:22:14 +0100 > > > Stuart Henderson wrote: > > > > > > > ld.lld: error: undefined symbol: __

Re: i386/LLVM 10

2020-08-06 Thread Stuart Henderson
On 2020/08/06 03:22, Jonathan Gray wrote: > On Tue, Aug 04, 2020 at 07:40:45PM -0400, George Koehler wrote: > > On Tue, 4 Aug 2020 23:22:14 +0100 > > Stuart Henderson wrote: > > > > > ld.lld: error: undefined symbol: __atomic_is_lock_free > > > > kettenis wrote an __atomic_is_lock_free for macpp

Re: Switch to LLVM 10 imminent

2020-08-06 Thread Timo Myyrä
Ok then, I got black screen with daisy's head cursor and it stuck there. I recall I was testing some soundfonts last time so it might be my local issue. So, ok from me on the gzdoom. Timo On Thu, Aug 6, 2020, at 13:40, Edd Barrett wrote: > On Thu, Aug 06, 2020 at 01:33:33PM +0300, Timo Myyrä w

Re: Switch to LLVM 10 imminent

2020-08-06 Thread Edd Barrett
On Thu, Aug 06, 2020 at 01:33:33PM +0300, Timo Myyrä wrote: > Did you play test? I quickly tried to check it and got just black > screen. I didn't have time to debug it so it might be something else. I killed a couple of zombies on the first level of Doom 2. I'm an idiot though, because I forgot

Re: Switch to LLVM 10 imminent

2020-08-06 Thread Timo Myyrä
Did you play test? I quickly tried to check it and got just black screen. I didn't have time to debug it so it might be something else. Timo On Thu, Aug 6, 2020, at 13:23, Edd Barrett wrote: > On Tue, Aug 04, 2020 at 10:34:59PM -0400, Daniel Dickman wrote: > > > emulators/dolphin > > > games/gz

Re: Switch to LLVM 10 imminent

2020-08-06 Thread Edd Barrett
On Tue, Aug 04, 2020 at 10:34:59PM -0400, Daniel Dickman wrote: > > emulators/dolphin > > games/gzdoom > > These two should be 1-liner fixes. See: > > https://github.com/KhronosGroup/glslang/pull/2010/commits/24b3e8384e93f3e73b6aa14ea00a30574112f9ba Works fine for gzdoom. Diff below (no bump nee

Re: Ports LLVM-10's CMake files trying to use macOS os/signpost.h during configure time

2020-08-06 Thread Brian Callahan
This issue went away when I removed llvm's WRKSRC. Sorry for the noise. ~Brian

LLVM 10: net/libtorrent-rasterbar

2020-08-06 Thread Nam Nguyen
This diff backports a 10.0.1 fix for an llvm crash while compiling net/libtorrent-rasterbar web_connection-base.cpp and bt_peer_connection.cpp. I compiled an earlier version of jca@'s update to devel/llvm 10 with debug symbols to get this backtrace: https://namtsui.com/public/libtorrent-rast

Ports LLVM-10's CMake files trying to use macOS os/signpost.h during configure time

2020-08-05 Thread Brian Callahan
Hi ports -- I am trying to update flang to llvm-10. When I try to configure flang, I get this error: Call Stack (most recent call first): /usr/local/lib/cmake/llvm/LLVMProcessSources.cmake:69 (find_all_header_files) /usr/local/lib/cmake/llvm/AddLLVM.cmake:419 (llvm_process_sources) /usr

Re: Switch to LLVM 10 imminent

2020-08-05 Thread Christian Weisgerber
Christian Weisgerber: > > > http://build-failures.rhaalovely.net/amd64/2020-08-03/ > > > > > > emulators/dolphin > > > games/gzdoom > > > > These two should be 1-liner fixes. See: > > > > https://github.com/KhronosGroup/glslang/pull/2010/commits/24b3e8384e93f3e73b6aa14ea00a30574112f9ba > > Yup,

Re: i386/LLVM 10

2020-08-05 Thread Jonathan Gray
On Tue, Aug 04, 2020 at 07:40:45PM -0400, George Koehler wrote: > On Tue, 4 Aug 2020 23:22:14 +0100 > Stuart Henderson wrote: > > > ld.lld: error: undefined symbol: __atomic_is_lock_free > > kettenis wrote an __atomic_is_lock_free for macppc when it switched to > base-clang: /usr/src/lib/libcomp

Re: Switch to LLVM 10 imminent

2020-08-05 Thread Christian Weisgerber
Daniel Dickman: > > http://build-failures.rhaalovely.net/amd64/2020-08-03/ > > > > emulators/dolphin > > games/gzdoom > > These two should be 1-liner fixes. See: > > https://github.com/KhronosGroup/glslang/pull/2010/commits/24b3e8384e93f3e73b6aa14ea00a30574112f9ba Yup, and this one, too: emula

Re: Switch to LLVM 10 imminent

2020-08-04 Thread Daniel Dickman
On Tue, Aug 4, 2020 at 6:41 PM Christian Weisgerber wrote: > > The base system has officially switched to LLVM 10. Snapshots with > the new compiler are available. > > Right now I'm signing and uploading the first set of official amd64 > snapshot packages built with LLV

Re: i386/LLVM 10

2020-08-04 Thread George Koehler
On Tue, 4 Aug 2020 23:22:14 +0100 Stuart Henderson wrote: > ld.lld: error: undefined symbol: __atomic_is_lock_free kettenis wrote an __atomic_is_lock_free for macppc when it switched to base-clang: /usr/src/lib/libcompiler_rt/ppc/atomic_lock_free.c Do we now need to write __atomic_is_lock_free

Re: Switch to LLVM 10 imminent

2020-08-04 Thread Christian Weisgerber
The base system has officially switched to LLVM 10. Snapshots with the new compiler are available. Right now I'm signing and uploading the first set of official amd64 snapshot packages built with LLVM 10. Logs from the remaining build failure: http://build-failures.rhaalovely.net/amd64/20

Re: i386/LLVM 10

2020-08-04 Thread Stuart Henderson
On 2020/08/04 23:14, Stuart Henderson wrote: > More information after my next build (some build that failed caused > my log archival scripts to break) but there was a lot of breakage > on i386. > > I'll have complete logs when rebuild finishes in about 9 hours - > not sure when I will have time to

i386/LLVM 10

2020-08-04 Thread Stuart Henderson
More information after my next build (some build that failed caused my log archival scripts to break) but there was a lot of breakage on i386. I'll have complete logs when rebuild finishes in about 9 hours - not sure when I will have time to upload them. Here are some of the more important broken

Re: LLVM 10: lang/crystal

2020-08-03 Thread Wesley Moxam
er wrote: > > Hi. This is about OpenBSD ports/lang/crystal. > > > > When OpenBSD switches base-clang to LLVM 10, it will add > > /usr/bin/llvm-config to base. This will break crystal, because it > > will run the wrong llvm-config and get a linker error: > > > h

Re: Switch to LLVM 10 imminent

2020-08-03 Thread Patrick Wildt
wrote: > I'd like to try llvm-10 (latest git master), but when i try to build on > OpenBSD-6.7 (amd64), but i get build failures such as: > > llvm-project/libcxxabi/../libcxx/include/__config:1150:6: error: "No thread > API"). > > Is there a set of patches s

Re: Switch to LLVM 10 imminent

2020-08-03 Thread Kurt Mosiejczuk
On Mon, Aug 03, 2020 at 08:58:44AM +0100, Julian Smith wrote: > I'd like to try llvm-10 (latest git master), but when i try to build on > OpenBSD-6.7 (amd64), but i get build failures such as: > llvm-project/libcxxabi/../libcxx/include/__config:1150:6: error: "No thread >

Re: LLVM 10: lang/crystal

2020-08-03 Thread Stuart Henderson
On 2020/08/02 20:25, George Koehler wrote: > Hi. This is about OpenBSD ports/lang/crystal. > > When OpenBSD switches base-clang to LLVM 10, it will add > /usr/bin/llvm-config to base. This will break crystal, because it > will run the wrong llvm-config and get a linker error:

Re: Switch to LLVM 10 imminent

2020-08-03 Thread Julian Smith
I'd like to try llvm-10 (latest git master), but when i try to build on OpenBSD-6.7 (amd64), but i get build failures such as: llvm-project/libcxxabi/../libcxx/include/__config:1150:6: error: "No thread API"). Is there a set of patches somewhere that i can use? [ports/lang/clan

LLVM 10: lang/crystal

2020-08-02 Thread George Koehler
Hi. This is about OpenBSD ports/lang/crystal. When OpenBSD switches base-clang to LLVM 10, it will add /usr/bin/llvm-config to base. This will break crystal, because it will run the wrong llvm-config and get a linker error: http://build-failures.rhaalovely.net/amd64-clang/2020-08-01/lang

LLVM 10: www/netsurf/libcss

2020-08-02 Thread George Koehler
LLVM 10 can't build www/netsurf/libcss because of -Werror. This diff allows me to build libcss with LLVM 10 on amd64. "make test" passes in libcss, and I can run the netsurf browser. OK? I don't remove -Werror. I change "xx" to from float to double, so "xx &

Re: Switch to LLVM 10 imminent

2020-08-02 Thread Christian Weisgerber
On 2020-08-01, Christian Weisgerber wrote: > I have uploaded the failure logs from early builds at > http://build-failures.rhaalovely.net/amd64-clang/ There's a new 2020-08-01/ subdirectory with the results from the latest build. With pango fixed, nearly the complete ports tree built. The rema

Re: Switch to LLVM 10 imminent

2020-08-02 Thread Timo Myyrä
"Raymond E. Pasco" writes: > On Sat Aug 1, 2020 at 4:14 PM EDT, Christian Weisgerber wrote: >> I have uploaded the failure logs from early builds at >> http://build-failures.rhaalovely.net/amd64-clang/ > > games/gzdoom may be fixable by updating the port to 4.4.x, which removes > the offending li

Re: Switch to LLVM 10 imminent

2020-08-01 Thread Raymond E. Pasco
On Sat Aug 1, 2020 at 4:14 PM EDT, Christian Weisgerber wrote: > I have uploaded the failure logs from early builds at > http://build-failures.rhaalovely.net/amd64-clang/ games/gzdoom may be fixable by updating the port to 4.4.x, which removes the offending line.

Switch to LLVM 10 imminent

2020-08-01 Thread Christian Weisgerber
I don't think there was any public announcement, but most will have surmised it by now: The base compiler will soon switch from LLVM 8 to LLVM 10 on all CLANG_ARCHS. This also concerns the linker on LLD_ARCHS. This will cause a certain amount of breakage in the ports tree. We are working

Re: LLVM 10: devel/glib2, devel/pango

2020-08-01 Thread Christian Weisgerber
Antoine Jacoutot: > Sure ok. > Is there a missing pango bump? It's only changing the fallthrough annotation so -Werror=implicit-fallthrough won't abort the build. There is no code change. -- Christian "naddy" Weisgerber na...@mips.inka.de

Re: LLVM 10: devel/glib2, devel/pango

2020-08-01 Thread Antoine Jacoutot
Sure ok. Is there a missing pango bump? — Antoine > On 1 Aug 2020, at 17:45, Christian Weisgerber wrote: > > devel/pango fails to build with LLVM 10, which takes out a large part > of the ports tree. > http://build-failures.rhaalovely.net/amd64-clang/2020-07-31/devel/pango.l

Re: LLVM 10: mail/bogofilter

2020-08-01 Thread Marc Espie
On Sat, Aug 01, 2020 at 05:13:11PM +0200, Christian Weisgerber wrote: > mail/bogofilter's build failure with LLVM 10 is another silly case > of a configure script failing to recognize the compiler and treating > is as gcc3 or older. > http://build-failures.rhaalovely.net/amd64

LLVM 10: devel/glib2, devel/pango

2020-08-01 Thread Christian Weisgerber
devel/pango fails to build with LLVM 10, which takes out a large part of the ports tree. http://build-failures.rhaalovely.net/amd64-clang/2020-07-31/devel/pango.log The fix has two parts, picked from upstream: (1) In glib2, define G_GNUC_FALLTHROUGH in such a way that is also available with

LLVM 10: mail/bogofilter

2020-08-01 Thread Christian Weisgerber
mail/bogofilter's build failure with LLVM 10 is another silly case of a configure script failing to recognize the compiler and treating is as gcc3 or older. http://build-failures.rhaalovely.net/amd64-clang/2020-07-31/mail/bogofilter%2Cqdbm.log $ cc -dumpversion 10.0.0 ok? Index: patches/

LLVM 10

2020-07-22 Thread Josias Allestad
Hello, I was wondering about the porting of LLVM 10. I have successfully compiled it, and wanted to know if any porter has done so as well and is working on the update. I understand the licensing difficulties, and that those may affect the port in the future (like gcc I assume), but I assume

Re: LLVM 10

2020-07-22 Thread Jeremie Courreges-Anglas
On Wed, Jul 22 2020, "Josias Allestad" wrote: > Hello, > > I was wondering about the porting of LLVM 10. > I have successfully compiled it, and wanted to know > if any porter has done so as well and is working on > the update. > > I understand the licensing