x86intrin.h not found after 10.4->11.2 upgrade
Morgan Reed
morgan.s.reed at gmail.com
Tue Jan 8 21:35:52 UTC 2019
Ah, that's the problem, /usr/include/x86intrin.h was a symlink to an old
clang 3.4.1 version of that header which doesn't exist on the filesystem
any more, I've deleted it and now things are much happier.
Really ought to do a clean rebuild on this box one of these days...
Thanks,
Morgan
On Wed, Jan 9, 2019 at 5:47 AM Dimitry Andric <dim at freebsd.org> wrote:
> On 8 Jan 2019, at 12:50, Morgan Reed <morgan.s.reed at gmail.com> wrote:
> >
> > Just did a find across /usr for the file and it's definitely there so I'm
> > not sure why the compiler can't find it :/
>
> Please post the output of:
>
> cc -v -x c -c /dev/null -o /dev/null
>
>
> >
> > # find /usr -name x86intrin.h
> > /usr/include/x86intrin.h
>
> This copy should not exist. Any idea where it came from, and what is
> its contents?
>
>
> > /usr/src/contrib/llvm/tools/clang/lib/Headers/x86intrin.h
> >
> /usr/local/lib/gcc7/gcc/x86_64-portbld-freebsd11.2/7.4.0/include/x86intrin.h
> > /usr/local/llvm60/lib/clang/6.0.1/include/x86intrin.h
> > /usr/lib/clang/6.0.0/include/x86intrin.h
>
> If your /usr/bin/cc reports being clang 6.0.0, then the latter one is
> correct.
>
> My guess would be that something (/etc/make.conf, for instance) is
> messing with your CFLAGS, causing the internal headers to not be found.
>
> -Dimitry
>
>
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-- Benjamin Franklin, 1759
More information about the freebsd-stable
mailing list