[Bug 1162960] New: LLVM aarch64-w64-mingw32 target is not built
http://bugzilla.opensuse.org/show_bug.cgi?id=1162960 Bug ID: 1162960 Summary: LLVM aarch64-w64-mingw32 target is not built Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening@forge.provo.novell.com Reporter: guillaume.gardet@arm.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- aarch64-w64-mingw32 support is missing from current LLVM package, but is required for mingw64 support on aarch64 in order to build WSL in OBS for aarch64. On x86_64, gcc is used to get x86_64-w64-mingw32-{gcc,etc.}, but it does not support aarch64. So, we need to enable build of aarch64-w64-mingw32 in our LLVM package. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1162960 Guillaume GARDET <guillaume.gardet@arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |afaerber@suse.com, | |guillaume.gardet@arm.com, | |lnussel@suse.com, | |msrb@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1162960 http://bugzilla.opensuse.org/show_bug.cgi?id=1162960#c1 --- Comment #1 from Guillaume GARDET <guillaume.gardet@arm.com> --- My understanding is llvm package should just provide a wrapper which take: aarch64-w64-mingw32-{clang,clang++,...} and point to {clang,clang++,....} Simple symbolic links or maybe a real wrapper with some options? Then, compile-rt need to be built for windows target to get lib/windows/libclang_rt.builtins-aarch64.a One script doing it is available here: https://github.com/mstorsjo/llvm-mingw/blob/master/build-compiler-rt.sh -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1162960 http://bugzilla.opensuse.org/show_bug.cgi?id=1162960#c2 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenther@suse.com --- Comment #2 from Stefan Dirsch <sndirsch@suse.com> --- Better let's also add Richard here. He's currently working on llvm(9) package anyway ... JFYI, Michal Srb <msrb@suse.com> left the company some time ago and is no longer maintaining llvm. He's one of the many Bugzilla zombies. :-( -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1162960 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|msrb@suse.com | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1162960 http://bugzilla.opensuse.org/show_bug.cgi?id=1162960#c4 Richard Biener <rguenther@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matz@suse.com --- Comment #4 from Richard Biener <rguenther@suse.com> --- I never understood the need for a mingw compiler to build WSL - can't the "install" component be written in sth like Powershell? Indeed GCC doesn't support aarch64-*-mingw*, adding support for that is welcome. Guess at ARM you should have the resources to push this. Using clang to build packages is not exactly welcome since clang isn't a supported part of our infrastructure so it's not wise to rely on it. -- You are receiving this mail because: You are on the CC list for the bug.
From what I saw so far MS does not provide Powershell bindings for the WSL interface. The official way they want distros to be delivered apparently is
http://bugzilla.opensuse.org/show_bug.cgi?id=1162960 http://bugzilla.opensuse.org/show_bug.cgi?id=1162960#c5 --- Comment #5 from Ludwig Nussel <lnussel@suse.com> --- that launcher written in C. Of course one could develop something that manually sets up the right registry keys via powershell, bypassing their official API but that would require reverse engineering and resources to actually maintain that method. We don't have anyone assigned to do that. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1162960 http://bugzilla.opensuse.org/show_bug.cgi?id=1162960#c6 --- Comment #6 from Richard Biener <rguenther@suse.com> --- Huh, I somehow misremember that Powershell has a way to interface with random C APIs then... Quick googling shows up you can? https://devblogs.microsoft.com/scripting/use-powershell-to-interact-with-the... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1162960 Ismail Dönmez <idonmez@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |idonmez@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1162960 Marius Kittler <marius.kittler@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marius.kittler@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com