Re: What is xmmintrin.h, and why aren't ports finding it?
On 07 Nov 2014, at 04:36, Chris H bsd-li...@bsdforge.com wrote: Greetings, Working on a recent 11-CURRENT install (11-CURRENT #1 amd64 r274134 Nov 5 12:56:14 PST 2014) svn info /usr/ports Revision: 372176 Given the above, and the fact that I have installed lang/gcc-48. Is there any reason that any port wanting to include xmmintrin.h fails to find it? Even though dmesg messages reflects the fact that gcc48 is included within my $PATH? What you have in your PATH does not matter. The xmmintrin.h header contains SSE intrinsics, and should automatically be found by your gcc 4.8 port. Normally it is located in: /usr/local/lib/gcc48/gcc/i386-portbld-freebsd11.0/4.8.4/include/xmmintrin.h or if you have a slightly different gcc version, just run: find /usr/local/lib/gcc48 -name xmmintrin.h to find it. If you run: gcc48 -v -x c -c /dev/null -o /dev/null it should show you the paths it searches for include files (look for the #include ... search starts here: line). For example, on my system this shows: #include ... search starts here: /usr/local/lib/gcc48/gcc/i386-portbld-freebsd11.0/4.8.4/include /usr/local/include /usr/local/lib/gcc48/gcc/i386-portbld-freebsd11.0/4.8.4/include-fixed /usr/include End of search list. The directory where you found xmmintrin.h should be listed in the search directories. -Dimitry ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: What is xmmintrin.h, and why aren't ports finding it?
On Fri, 7 Nov 2014 13:10:51 +0100 Dimitry Andric d...@freebsd.org wrote On 07 Nov 2014, at 04:36, Chris H bsd-li...@bsdforge.com wrote: Greetings, Working on a recent 11-CURRENT install (11-CURRENT #1 amd64 r274134 Nov 5 12:56:14 PST 2014) svn info /usr/ports Revision: 372176 Given the above, and the fact that I have installed lang/gcc-48. Is there any reason that any port wanting to include xmmintrin.h fails to find it? Even though dmesg messages reflects the fact that gcc48 is included within my $PATH? What you have in your PATH does not matter. The xmmintrin.h header contains SSE intrinsics, and should automatically be found by your gcc 4.8 port. Normally it is located in: /usr/local/lib/gcc48/gcc/i386-portbld-freebsd11.0/4.8.4/include/xmmintrin.h or if you have a slightly different gcc version, just run: find /usr/local/lib/gcc48 -name xmmintrin.h to find it. If you run: gcc48 -v -x c -c /dev/null -o /dev/null it should show you the paths it searches for include files (look for the #include ... search starts here: line). For example, on my system this shows: #include ... search starts here: /usr/local/lib/gcc48/gcc/i386-portbld-freebsd11.0/4.8.4/include /usr/local/include /usr/local/lib/gcc48/gcc/i386-portbld-freebsd11.0/4.8.4/include-fixed /usr/include End of search list. The directory where you found xmmintrin.h should be listed in the search directories. Thank you _very_ much for the reply, Dimitry. Indeed, following your example above. Indicates that xmmintrin.h _is_ in the search path. I think it must be a matter of _which_ CC USE_GCC is defaulting to. I'll have to examine things in that range, a little closer. Thank you again, for the informative reply, Dimitry. --Chris -Dimitry ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
What is xmmintrin.h, and why aren't ports finding it?
Greetings, Working on a recent 11-CURRENT install (11-CURRENT #1 amd64 r274134 Nov 5 12:56:14 PST 2014) svn info /usr/ports Revision: 372176 Given the above, and the fact that I have installed lang/gcc-48. Is there any reason that any port wanting to include xmmintrin.h fails to find it? Even though dmesg messages reflects the fact that gcc48 is included within my $PATH? This is causing me no end of grief, and try as I might, I can't seem to get past this problem. Thank you for all your time, and consideration. --Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
