[PROJ] PROJ 6.0.0RC3

[Greg Troxel]

Even Rouault <even.rouault at spatialys.com> writes:

>>   - There is no "--std=c++11".
>
> That's a weird one. I do have g++ 5.5 on Ubuntu 16.04 and it defaults to
> C++98, but ./configure automatically adds -std=c++11
> But it would be strange that mutex.cpp is the only file to fail compilation.
> C++11 is used extensively even in proj_internal.h, so all files should fail 
> compilation.
> Are you absolutely sure that your "c++" binary is g++ 5.5 ?
>
> What does the following return ?
> c++ -dM -E -x c++  /dev/null | grep -F __cplusplus

$ c++ -dM -E -x c++  /dev/null | grep -F __cplusplus
#define __cplusplus 199711L
$ type -a c++
c++ is /usr/bin/c++
$ /usr/bin/c++ -v
Using built-in specs.
COLLECT_GCC=/usr/bin/c++
COLLECT_LTO_WRAPPER=/usr/libexec/lto-wrapper
Target: x86_64--netbsd
Configured with: /usr/src/tools/gcc/../../external/gpl3/gcc/dist/configure --target=x86_64--netbsd --enable-long-long --enable-threads --with-bugurl=http://www.NetBSD.org/Misc/send-pr.html --with-pkgversion='NetBSD nb3 20180905' --with-system-zlib --disable-libstdcxx-dual-abi --enable-__cxa_atexit --enable-libstdcxx-time=rt --enable-libstdcxx-threads --with-tune=nocona --with-diagnostics-color=auto-if-env --with-mpc-lib=/var/obj/mknative/amd64-x86_64/usr/src/external/lgpl3/mpc/lib/libmpc --with-mpfr-lib=/var/obj/mknative/amd64-x86_64/usr/src/external/lgpl3/mpfr/lib/libmpfr --with-gmp-lib=/var/obj/mknative/amd64-x86_64/usr/src/external/lgpl3/gmp/lib/libgmp --with-mpc-include=/usr/src/external/lgpl3/mpc/dist/src --with-mpfr-include=/usr/src/external/lgpl3/mpfr/dist/src --with-gmp-include=/usr/src/external/lgpl3/gmp/lib/libgmp/arch/x86_64 --enable-tls --disable-multilib --disable-symvers --disable-libstdcxx-pch --disable-libstdcxx-dual-abi --build=x86_64--netbsd --host=x86_64--netbsd --with-sysroot=/var/obj/mknative/amd64-x86_64/usr/src/destdir.amd64
Thread model: posix
gcc version 5.5.0 (nb2 20180327)

But, I suspect the pkgsrc wrappers are adding --std=c++11, and I am
guessing that proj's configure only adds that if it is necessary.  I'll check that.

(The machine also has gcc 6 installed, in a different prefix, but no older versions.)

I would hope that proj builds ok with gcc 4.8; haven't tried yet.


> If that's indeed the only file to fail compilation, I'd suggest you try 
> tweaking the start of the file to comment out the #define _XOPEN_SOURCE 500 
> and/or #define _GNU_SOURCE

That was the only one.  It makes sense then that the --std flag is not
the issue.  Thanks for those hints - I had forgotten about
_XOPEN_SOURCE, but now that I remember about definition visibility
controls it sounds promising.



Has anyone built proj 6 with clang?  Any success reports from other than Linux?