On Sun, Feb 2, 2014 at 7:58 PM, Dave Johansen <davejohansen@xxxxxxxxx> wrote:
The EL6 build of llvm 3.4 is currently in testing and it was just pointed out that there's a potential issue with the build ( https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-0264/llvm-3.4-5.el6 ).
If you examine the build.log ( http://kojipkgs.fedoraproject.org//work/tasks/593/6470593/build.log ) It looks like the include path is being included twice and that's causing the warning about the invalid host type. Is there something wrong with the .spec file? Or is there something I can do to fix/prevent this issue?
Thanks,
Dave
I was able to get a hold of the original submitter of the issue and the issue is because of the multiple paths that exist on EL6. Here's his explanation and recommended solution:
> $ echo /usr/lib/gcc/x86_64*/*/include
> /usr/lib/gcc/x86_64-redhat-linux/4.4.4/include /usr/lib/gcc/x86_64-redhat-linux/4.4.7/include
Thanks,
Dave
> $ echo /usr/lib/gcc/x86_64*/*/include
> /usr/lib/gcc/x86_64-redhat-linux/4.4.4/include /usr/lib/gcc/x86_64-redhat-linux/4.4.7/include
>
> EL6 originally had gcc-4.4.4 and gcc-4-4.7 still has the old path included for compatibility. Because of the space inbetween configure thinks /usr/lib/gcc/x86_64-redhat-linux/4.4.7/include is a host type.
>
> The files in /usr/lib/gcc/x86_64-redhat-linux/4.4.7/include have nothing to do with C++. Clang has own versions of these files in /usr/lib/clang/3.4/include.
>
> Therefore it should just be --with-c-include-dirs=%{_includedir}, which is also the default if you specify nothing.
>
> C++ headers and runtime libs from gcc are selected by clang at runtime:
>
> $ clang -v
> clang version 3.4 (tags/RELEASE_34/final)
> Target: x86_64-redhat-linux-gnu
> Thread model: posix
> Found candidate GCC installation: /usr/lib/gcc/x86_64-redhat-linux/4.4.4
> Found candidate GCC installation: /usr/lib/gcc/x86_64-redhat-linux/4.4.7
> Selected GCC installation: /usr/lib/gcc/x86_64-redhat-linux/4.4.7![]()
So my question is if the same sort of change also needs to be made in the Fedora .spec file that the EL6 one is based on.> EL6 originally had gcc-4.4.4 and gcc-4-4.7 still has the old path included for compatibility. Because of the space inbetween configure thinks /usr/lib/gcc/x86_64-redhat-linux/4.4.7/include is a host type.
>
> The files in /usr/lib/gcc/x86_64-redhat-linux/4.4.7/include have nothing to do with C++. Clang has own versions of these files in /usr/lib/clang/3.4/include.
>
> Therefore it should just be --with-c-include-dirs=%{_includedir}, which is also the default if you specify nothing.
>
> C++ headers and runtime libs from gcc are selected by clang at runtime:
>
> $ clang -v
> clang version 3.4 (tags/RELEASE_34/final)
> Target: x86_64-redhat-linux-gnu
> Thread model: posix
> Found candidate GCC installation: /usr/lib/gcc/x86_64-redhat-linux/4.4.4
> Found candidate GCC installation: /usr/lib/gcc/x86_64-redhat-linux/4.4.7
> Selected GCC installation: /usr/lib/gcc/x86_64-redhat-linux/4.4.7
Thanks,
Dave
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
