Package Base Details: lib32-llvm-git

Git Clone URL: https://aur.archlinux.org/lib32-llvm-git.git (read-only)
Keywords: clang git llvm
Submitter: yurikoles
Maintainer: Lone_Wolf
Last Packager: Lone_Wolf
Votes: 11
Popularity: 0.061969
First Submitted: 2019-01-11 15:50
Last Updated: 2019-11-14 12:52

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

Lone_Wolf commented on 2015-07-25 12:25

Krejzi,

I noticed that lordheavy lib32-llvm-svn http://pkgbuild.com/~lcarlier/mesa-git/sources/lib32-llvm-svn/ doesn't build lib32-clang-svn .

Are you sure lib32-clang-svn is useful/needed ?

Krejzi commented on 2015-07-23 17:32

I tried and failed last time. clang build would fail for multilib when using autotools.

cmake build kinda works but can't build mesa with it and all shared libs build fails miserably when building.

I was out of ideas back then. Waiting for devs to fix their problems before attempting again.

oxalin commented on 2015-07-23 17:29

Also, as with llvm-svn and llvm-libs-svn, could you fix the PKGBUILD so the build has an out-of-source folder. That would fix the following error:

configure: error: In-source builds are not allowed. Please configure from a separate build directory!

oxalin commented on 2015-07-23 17:21

Please, apply the earlier proposed modification:
- svn export "${srcdir}/clang" tools/clang
- svn export "${srcdir}/compiler-rt" projects/compiler-rt
+ svn export --force "${srcdir}/clang" tools/clang
+ svn export --force "${srcdir}/compiler-rt" projects/compiler-rt
That would help.

That being said, I had put the debugging process aside for some time, I had not much time to work on it. But I'll be working on it again in the next couple of days. I hope to fix this thing or identify what is going on...

bountykiller commented on 2015-06-25 21:32

Same problem here. I'll try to investigate this when I'll found time to.
Also, i think that the change proposed by oxalin about adding the --force option to svn export would be nice, since right now I have to remove those 2 directories manually each time I rebuild the package.

oxalin commented on 2015-04-16 01:04

Still struggling to switch to cmake. However, I made some progress and I'm communicating with the LLVM devs about some changes.

That said, I had a look at the code repository. Around the time the bug appeared (with libclang_rt.asan...), there was a lot of clean up going on. In other words, even with a working cmake script, it may not work properly. I'm now thinking about using autotools as it was and bisecting the compiler-rt git code...

qubodup commented on 2015-04-09 20:16

same here http://codepad.org/skuBnpHY - slightly different lines though it seems

oxalin commented on 2015-04-07 07:05

After hearing from the LLVM dev team, it seems that:
- there might be a bug appearing with autotools;
- we should move to cmake, since autotools are slowly being deprecated;

See https://llvm.org/bugs/show_bug.cgi?id=23063

I'll work on a PKGBUILD that would use cmake and I'll give you some info about it, since it seems to be the way to go. I'll work on the autotools bug later on the LLVM side.

oxalin commented on 2015-03-29 17:58

I tried to build LLVM from scratch outside of this package and it fails the same way as Behem0th and I have reported. I'm filing a bug on LLVM project's side.

oxalin commented on 2015-03-16 03:08

I get the same error as Behem0th since a couple of weeks. However, building the native llvn-svn works without a glitch.


Also, I'd like to suggest two simple modifications to the PKGBUILD:
- svn export "${srcdir}/clang" tools/clang
- svn export "${srcdir}/compiler-rt" projects/compiler-rt
+ svn export --force "${srcdir}/clang" tools/clang
+ svn export --force "${srcdir}/compiler-rt" projects/compiler-rt

This will prevent an error from svn complaining about folders already existing when trying to restart the build if it has failed.