- User Since
- Aug 15 2016, 6:00 AM (100 w, 6 d)
Tue, Jul 17
I don't think this could break anything. I presume you've tested it though.
Mon, Jul 9
Fri, Jun 29
Tue, Jun 26
Ping. This is necessary to resolve https://github.com/google/sanitizers/issues/974 and fix tests on systems which don't enable all the backwards compatibility cruft (Arch, Gentoo). See also D47817 as necessary dependency.
Jun 15 2018
Jun 6 2018
Jun 5 2018
Erm, louder ping?
Erm, louder ping?
Good catch! LGTM.
May 9 2018
To add a real use case broken by this: Gentoo prior to 17.1 (which includes most of existing installs) used /usr/lib -> lib64 symlink. The canonical LLVM install path for Gentoo is:
May 8 2018
…at the cost of breaking CMake, and having to hack LLVM and CMake to make it work again. And I'm pretty sure sooner or later this realpath use will break somebody's use case. Think of a simple example of someone using a temporary symlink in path to relocate LLVM install. By using realpath, you're effectively replacing the canonical location with possibly temporary current location that may no longer be valid afterwards.
Works just fine. Note that find_package documentation actually mentions scanning locations relative to PATH.
Gentoo also supports installing multiple versions (in /usr/lib/llvm/X), and I have never seen any problems close to what you're describing. We're just putting the appropriate bin/ directories in PATH, and CMake finds its files just fine (relatively to PATH). So why do you need a lot of symlink magic to achieve the same effect?
I don't think I agree with this change. Unless I'm missing something, Debian is using a install layout that is broken by design, and you're now attempting to workaround that by adding symlinks and realpath hacks that are supposed to make the broken design somewhat incidentally work, if only someone doesn't miss one of the fragile connections and accidentally break it.
May 6 2018
For the record, this has been fixed upstream: https://github.com/sphinx-doc/sphinx/pull/4282. However, I don't know which release version (if any) has the fix.
Apr 24 2018
Apr 9 2018
I've based this change on an earlier fix to lldb when that project started using LLVMTestingSupport.
Apr 8 2018
I think you'd want a definition list instead then. But I haven't tested if they can be nested inside option lists.
Apr 7 2018
W dniu nie, 08.04.2018 o godzinie 00∶13 +0000, użytkownik Zachary Turner
Well, my idea was to list the standards one per line (like on GCC manpage), and then the '(deprecated)' comments would probably stand out enough to apply to a single line. Also, FWICS the gcc manpage simply lists which aliases are deprecated in the description text. But skipping them entirely also works for me.
To be honest, I find those '(deprecated)' confusing — the user may mistakenly assume that it's about all values rather than the alias.
Works fine, thanks a lot! Note that I haven't tested crossdev or anything special, just regular multilib.
I'm sorry, I see the problem now — the diff generated by Phabricator does not include the empty files x_x (seriously, this thing keeps surprising me in how broken it could be). I'm going to try again with correct file set tonight or tomorrow. If you could send the complete patch (preferably -p1 if you have one) to mgorny AT gentoo.org, that would also be helpful.
Apr 6 2018
Well, it's better:
To be honest, I don't really know. But since we're not installing it straight to /usr, I suppose that's not a problem we need to solve right now.
Apr 5 2018
Ok, that's a problem. I think we really ought to consider all possibilites of sysroot first, and either do not fall back to main system at all or do that only if sysroot doesn't have any install at all. Basically, it is important that we don't break non-Gentoo sysroots, even when running on top of Gentoo.
Ok, I've tried it on top of clang-6.0.0 and I get the following test failures:
Apr 4 2018
If that's not a problem, then the more tests, the merrier ;-). Preferably something specific to crossdev would be helpful, given this is a new use case, and/or something that would actually have directory mismatches with CURRENT entry name (i.e. that wouldn't have worked before).
Thanks. Besides that one tiny nit, looks good at a first glance. I'll test it tomorrow or the next day (but only for the most basic use, sorry).
Mar 29 2018
Mar 20 2018
Mar 19 2018
Mar 15 2018
Mar 12 2018
Aye, sorry, I confused it with generated config ;-). It looks sane to me.
I don't see why not but I'm not sure if it has any value by itself. FWICS, LLVM_DYLIB_COMPONENTS is not used anywhere in cmake/*.
Yes, full standalone.
I can't test this right now but please make sure not to break linking to split shared libraries without dylib.
Mar 8 2018
Thanks for the review. As for the -Wl,-z,origin part, I'd rather leave that alone unless we have a clear indication that either it is not necessary for any of the supported FreeBSD and DragonFly BSD versions, or that it can be passed unconditionally without breaking any of the supported systems (and which linkers accept it).
Mar 6 2018
@rnk, could you confirm the rebased patch? I'm not sure if I should override InputKind::RenderScript as well.
Mar 5 2018
Mar 2 2018
Ping. I'd like to have this reviewed before I roll 6.0.0 final for Gentoo.
Feb 26 2018
Feb 24 2018
@beanz, updated as requested.
Feb 23 2018
Feb 19 2018
Ping for the third time.
Jan 29 2018
Jan 20 2018
Jan 19 2018
Disclaimer: I have never seen a plugin for LLDB. I've just noticed the wrong path in strace output and fixed it ;-).
Jan 18 2018
Jan 9 2018
Jan 7 2018
Updated the patch to use LLVM_ENABLE_ZLIB directly.
I was talking of:
Jan 6 2018
Well, it's actually more complex. In Gentoo we want to let the user choose whether he wants to build against zlib or without zlib support. So in the end there are two uses to be considered:
Maybe we could. I presumed people are using the separate variables for some reason. We'd have to check that it's properly sanitized when building in-tree and given to cmake though.