Messages in this thread | | | Date | Fri, 12 Jun 2015 21:43:37 -0700 | From | Alexei Starovoitov <> | Subject | Re: [RFC PATCH v7 23/37] perf tools: Introduce llvm config options |
| |
On 6/12/15 9:11 PM, pi3orama wrote: > > > 发自我的 iPhone > >> 在 2015年6月13日,上午10:31,Alexei Starovoitov <ast@plumgrid.com> 写道: >> >>> On 6/11/15 10:35 PM, Wang Nan wrote: >>> # Path to clang. If omit, search it from $PATH. >>> clang-path = "/path/to/clang" >> >> I think this bit and search_program() from the next patch is >> overly flexible. It's always delicate to search file paths. > > About this clang-path: in my environment the name of clang is x86_64-oe-linux-clang, and installed in /usr/bin/llvm-3.7, neither in $PATH nor has its default name. This is the default setting of yocto and open-embedded based systems. Please see do_install part in building script of it: > > https://github.com/openembedded/meta-oe/blob/master/meta-oe/recipes-core/llvm/llvm.inc
well, that setup installs host backend only due to: --enable-targets=host-only in the above script, whereas typical clang install on ubuntu/fedora includes all backends. So in your case you'd need to install another clang. I agree that the name can be different than just 'clang', so yeah 'clang-path' is needed for this reason. So I'm ok keeping patches 23 and 24 as-is.
| |