On 2017-Jul-24, at 12:03 AM, David Chisnall <thera...@freebsd.org> wrote:

> On 23 Jul 2017, at 23:54, Mark Millard <mar...@dsl-only.net> wrote:
>>>   c++ -isystem ${OUTDIR}/tmp/usr/include/c++/v1 -std=c++11  -nostdinc++ 
>>> -isystem ${OUTDIR}/tmp/usr/include -L${OUTDIR}/tmp/usr/lib 
>>> -B${OUTDIR}/tmp/usr/lib --sysroot=${OUTDIR}/tmp -B${OUTDIR}/tmp/usr/bin  -O 
>>> -pipe -G0 -EB -mabi=32 -msoft-float  -DIN_GLIBCPP_V3 -DHAVE_CONFIG_H 
>>> -I${SRCDIR}/gnu/lib/libstdc++ -I${SRCDIR}/contrib/libstdc++/libsupc++ 
>>> -I${SRCDIR}/contrib/gcc -I${SRCDIR}/contrib/libstdc++/include 
>>> -I${SRCDIR}/contrib/gcclibs/include -I${SRCDIR}/contrib/libstdc++/include 
>>> -I. -frandom-seed=RepeatabilityConsideredGood -fno-implicit-templates 
>>> -ffunction-sections -fdata-sections -Wno-deprecated   -c 
>>> ${SRCDIR}/contrib/libstdc++/src/bitmap_allocator.cc -o bitmap_allocator.o
> This is quite a surprising build command.  It’s using usr/include/c++/v1 for 
> system includes, but usr/include/c++/v1 is the libc++ header directory.  
> libstdc++ shouldn’t need to be built with C++11 support, but libc++ does, so 
> this command looks like a combination of both libc++ and libstdc++ build 
> flags all mashed together.

I see that when I forwarded Ravi Pokala's message to other
lists that seemed appropriate --where it was more likely
to be noticed-- I forgot to CC Ravi.

I fix this now by listing him in the To for this reply.

As for the command: I expect that the weird mix is the
essence of what Ravi P. was reporting, going along with
the -std=c++11 command line option that was explicitly
rejected by the compiler.

I have not yet tried a gcc 4.2.1 based build for powerpc64
or powerpc yet. (I tend to experiment with clang support
of them.) But I will at some point and see if I get a similar

Mark Millard
markmi at dsl-only.net

freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to