On 3/31/16 4:42 PM, Mark Millard wrote:
> On 2016-Mar-31, at 3:34 PM, Bryan Drewery <bdrewery at FreeBSD.org> wrote:
>> > #include "..." search starts here:
>> > #include <...> search starts here:
>> > /usr/local/lib/gcc49/include/c++/
>> > /usr/local/lib/gcc49/include/c++//x86_64-portbld-freebsd11.0
>> > /usr/local/lib/gcc49/include/c++//backward
>> > /usr/local/lib/gcc49/gcc/x86_64-portbld-freebsd11.0/4.9.4/include
>> > /usr/local/include
>> > /usr/local/lib/gcc49/gcc/x86_64-portbld-freebsd11.0/4.9.4/include-fixed
>> > /usr/include
>> > End of search list.
> Beyond /usr/local/include is also the fun of [ignoring C++ specific issues]:
> (My quoting of a copy/paste)
> 
>> > # ls /usr/local/lib/gcc49/gcc/powerpc64-portbld-freebsd11.0/4.9.4/include*
>> > /usr/local/lib/gcc49/gcc/powerpc64-portbld-freebsd11.0/4.9.4/include:
>> > altivec.h          iso646.h                ppc-asm.h               
>> > spu2vmx.h               stdatomic.h             stdint-gcc.h            
>> > unwind.h
>> > float.h                    objc                    ppu_intrinsics.h        
>> > ssp                     stdbool.h               stdint.h                
>> > varargs.h
>> > htmintrin.h                omp.h                   si2vmx.h                
>> > stdalign.h              stddef.h                stdnoreturn.h           
>> > vec_types.h
>> > htmxlintrin.h              paired.h                spe.h                   
>> > stdarg.h                stdfix.h                tgmath.h
>> > 
>> > /usr/local/lib/gcc49/gcc/powerpc64-portbld-freebsd11.0/4.9.4/include-fixed:
>> > README             libmilter       limits.h        netinet         
>> > stddef.h        stdio.h         stdlib.h        sys             
>> > syslimits.h     unistd.h        wchar.h
> But at least in recent times after WCHAR_TYPE was fixed for powerpc/powerpc64 
> I've not had troubles that traced to these for CC and CXX being based on 
> gcc49 while XCC and XCXX were based on powerpc64-gcc for 
> buildworld/buildkernel on a powerpc64 host.
> 
> I have had various examples of /usr/local/include/ files breaking builds 
> depending on what ports were in place at the time. All along I've been doing 
> renaming in that area to allow buildworld/buildkernel use.

This should be fine with my fix too.

Trying add this to your make.conf for now:

CFLAGS.gcc+= -isystem /usr/include

-- 
Regards,
Bryan Drewery
_______________________________________________
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"

Reply via email to