| Summary: | sys-devel/llvm - add support for building only non-native targets | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Luke-Jr <luke-jr+gentoobugs> |
| Component: | [OLD] Development | Assignee: | Michał Górny <mgorny> |
| Status: | RESOLVED CANTFIX | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=506594 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Luke-Jr
2014-04-12 14:35:08 UTC
Please rephrase that more verbosely, since I don't understand what you exactly want to get and for which targets. LLVM does not currently support x32, but Mesa's OpenCL requires LLVM for the r600 compiler. So the only way to get OpenCL support on x32 right now would be to build LLVM targetting *only* r600, but not the native platform (x32, unsupported). Oh, so you mean you want libx32 version of llvm without the 'host' target, correct? Did you confirm that building like this works? Also, could you elaborate a bit more on how x32 doesn't work? Looking at the configure code, I think it should select plain x86_64 on x32. Does that fail to build or does something else happen? Build log would be appreciated to understand the issue better. (In reply to Michał Górny from comment #3) > Oh, so you mean you want libx32 version of llvm without the 'host' target, > correct? Did you confirm that building like this works? I wasn't able to get it to work, but the LLVM developers tell me it should... somehow. > Also, could you elaborate a bit more on how x32 doesn't work? Looking at the > configure code, I think it should select plain x86_64 on x32. Does that fail > to build or does something else happen? Build log would be appreciated to > understand the issue better. At least bugs #480378 and #506594 are tracking this. Ok, I'm going to take a look at this but I need to get x32-capable toolchain first and this will take a while. Since this specific subset of targets is quite uncommon, I'm going to merge this into the bug requesting full target selection. *** This bug has been marked as a duplicate of bug 523732 *** Ok, so things changed a little. Good news is that we have fine-grained target selection now. Bad news is that in order to keep dependencies sane, native target is always enabled. However, you can explicitly un-package.use.force if you really want to. |
