Re: 11.0: head/lib/libsysdecode/Makefile for . . ./libsoft/usr/include uses CPP when XCPP needed? [Makefile.libcompat issue]

2016-04-15 Thread Mark Millard
On 2016-Apr-14, at 1:41 PM, Bryan Drewery wrote: > . . .Please try this patch though: > > https://people.freebsd.org/~bdrewery/patches/libcompat-xcpp.diff So far so good. . . TARGET_ARCH=amd64 hosted on amd64: buildworld/buildkernel built without reporting any errors. TARGET_ARCH=armv6 host

Re: 11.0: head/lib/libsysdecode/Makefile for . . ./libsoft/usr/include uses CPP when XCPP needed? [Makefile.libcompat issue]

2016-04-14 Thread Mark Millard
This will take me a while. I'm trying 2 or more builds, all from amd64 context: TARGET_ARCH=amd64 TARGET_ARCH=armv6 (with my rpi2 armv7a tailoring in src.conf) possibly TARGET_ARC=powerpc64 (without lib32) or powerpc (which has no lib32 or libsoft option) I'm doing this because my personal work

Re: Fwd: 11.0: head/lib/libsysdecode/Makefile for . . ./libsoft/usr/include uses CPP when XCPP needed? [Makefile.libcompat issue]

2016-04-14 Thread Bryan Drewery
On 4/6/2016 1:14 PM, Mark Millard wrote: > The below forwards an example of a possibly more general issue not > necessarily limited to arm context of the example: in a cross compile context > the host CPP is in use via Makefile.libcompat not involving "${XCPP}" and so > various macro checks for

Fwd: 11.0: head/lib/libsysdecode/Makefile for . . ./libsoft/usr/include uses CPP when XCPP needed? [Makefile.libcompat issue]

2016-04-06 Thread Mark Millard
The below forwards an example of a possibly more general issue not necessarily limited to arm context of the example: in a cross compile context the host CPP is in use via Makefile.libcompat not involving "${XCPP}" and so various macro checks for the target context fail to work. [The below and