https://bugs.kde.org/show_bug.cgi?id=352896
Sergio Martins changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #29 from RJVB ---
This is what I have in the llvm lib dir:
> lc /opt/local/libexec/llvm-3.9/lib/libLLVM*
> libLLVM.dylib*
> libLLVMCodeGen.a l
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #33 from RJVB ---
Yep, after removing that everything builds and runs against 3.7, 3.8 and 3.9 .
Note I've only tested it against a simple file that contains nothing clazy
complains about even at level3 but I don't really suspect any platf
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #32 from Sergio Martins ---
that was an oversight, everything builds ok for you without it ?
I'll remove it soon
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #31 from RJVB ---
Except that then you need to get rid of this:
-if(APPLE)
- target_link_libraries(clazylib LLVM)
-endif()
because that adds -lLLVM to the link command. That'll succeed except with 3.7
where that library doesn't exist.
--
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #30 from RJVB ---
(In reply to Sergio Martins from comment #28)
> the clazy branch fixing_mac doesn't even link to libLLVM
Oops, cross-over. Indeed, that corresponds to my observation!
--
You are receiving this mail because:
You are watch
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #28 from Sergio Martins ---
the clazy branch fixing_mac doesn't even link to libLLVM
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #27 from RJVB ---
(In reply to Sergio Martins from comment #25)
> but we're not linking to libLLVM.dylib, it's all static libs.. so why is
> that needed ? Or the static libs are also versioned ?
Well, no, I'm getting dynamic libs. Maybe it
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #26 from RJVB ---
Created attachment 102004
--> https://bugs.kde.org/attachment.cgi?id=102004&action=edit
patch to allow building against llvm 3.7 on Mac
As said, I have no idea if the versions libLLVM name is an LLVM thing or a
MacPorts
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #25 from Sergio Martins ---
but we're not linking to libLLVM.dylib, it's all static libs.. so why is that
needed ? Or the static libs are also versioned ?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #24 from RJVB ---
This works with 3.7, 3.8 and 3.9 from MacPorts. However, for 3.7 I had to
compensate for the fact that libLLVM is called libLLVM-3.7.dylib in that
version. I have no idea whether that's a MacPorts thing or not.
I'll attach
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #23 from Sergio Martins ---
Can you test 'fixing_mac' branch ? Works for me with 3.9 + macports
Should also work with 3.7
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #22 from Sergio Martins ---
Git commit 05262016a161d3a163ab94b5358ade7a1a1b5e78 by Sergio Martins.
Committed on 02/11/2016 at 23:09.
Pushed by smartins into branch 'fixing_mac'.
Testing a proper mac fix
M +10 -6CMakeLists.txt
M +7
https://bugs.kde.org/show_bug.cgi?id=352896
Sergio Martins changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #20 from Sergio Martins ---
Git commit 91e005f34df7db3eb537169c2df3b65dc345dd62 by Sergio Martins.
Committed on 02/11/2016 at 22:33.
Pushed by smartins into branch 'master'.
Fix run_tests.py on macOS
Needs to load a .dylib instead of .so
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #19 from Sergio Martins ---
(In reply to RJVB from comment #18)
> Is there anything Mac specific in support for different clang versions?
Apparently yes, otherwise 3.9 would also work, just like it does on Linux.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #18 from RJVB ---
Is there anything Mac specific in support for different clang versions? I
didn't mention it but the exact same "build recipe" works fine on Linux with
clang 3.9 . Why would that be any different on Mac?
--
You are receivi
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #17 from Sergio Martins ---
I can only afford to support one clang version (3.8) on macOS.
Even if you provide a patch for other versions, sooner or later they will break
as I don't have bandwith to maintain all the combinations of clazy/LLV
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #16 from RJVB ---
Have you tested building against LLVM versions < 3.7.9 on OS X? According to my
local patches those had a versioned libLLVM name (libLLVM-${LLVM_VERSION}), at
least in MacPorts.
Also, while everything builds correctly, I'm
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #15 from Antonio Forgione ---
I confirm that I can now compile successfully on Mac using brew packages.
Thanks!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=352896
Allen Winter changed:
What|Removed |Added
CC||win...@kde.org
--- Comment #14 from Allen Winter
https://bugs.kde.org/show_bug.cgi?id=352896
Sergio Martins changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #12 from Sergio Martins ---
Git commit 7b1aac484be5e14affe175ba8b4300a0e981b7ea by Sergio Martins.
Committed on 28/10/2016 at 23:32.
Pushed by smartins into branch 'master'.
Fix build on macOS when using macports llvm
The clazy convenience
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #11 from RJVB ---
Antonio: apologies for the delay. I never got (saw) a notification for your
question.
In practice I used a personal MacPorts port to build clazy:
https://github.com/RJVB/macstrop/tree/master/devel/clazy
The "Portfile" con
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #10 from Sergio Martins ---
RJVB, can you see previous comment ? Thanks
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=352896
Antonio Forgione changed:
What|Removed |Added
CC||emi...@gmail.com
--- Comment #9 from Antonio
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #8 from RJVB ---
I confirm: the same fix makes the build succeed on OS X.
The same issue with the missing plugin path exists though, and in addition the
wrapper script assumes a .so extension while the plugin is now generated with
the more
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #7 from RJVB ---
Yes, evidently :)
I think I have an idea of the reason for the error. I tried building clazy
against Ubuntu's clang 3.7, and got an error about a missing symbol,
_ZTIN4llvm27CrashRecoveryContextCleanupE. That one was resolv
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #6 from Sergio Martins ---
did you build kdevelop's clang plugin too ?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #5 from RJVB ---
Created attachment 96999
--> https://bugs.kde.org/attachment.cgi?id=96999&action=edit
log of the failing link command
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #4 from RJVB ---
Well, after pulling from the new repo everything seems to work fine, but the
(final?) link step fails. I don't think that's kdevelop's fault (kdevelop5
builds against the same llvm/clang 3.7 install). See the log.
--
You a
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #3 from Sergio Martins ---
We're now using the build system from kdevelop and sync with them periodically.
Any fix or complaint should be filled with kdevelop, but this should be
working now.
--
You are receiving this mail because:
You ar
32 matches
Mail list logo
