Bowie Bailey writes:
On 3/7/2017 7:17 AM, Sam Varshavchik wrote: > Alessandro Vesely writes: > >> On Tue 07/Mar/2017 03:43:45 +0100 Sam Varshavchik wrote: >> > Download: http://www.courier-mta.org/download.html#unicode >> > >> > This is a test build of the courier-unicode package, that uses >> C++11's unicode >> > support. Please report any build issues to the courier-users list. >> >> Yes, it works, but I had to manually set CXXFLAGS="-std=c++11". That >> could be >> avoided by using AX_CXX_COMPILE_STDCXX in configure. I found no m4 >> dir, so I >> added it and saved there the file I found in: >> https://www.gnu.org/software/autoconf-archive/ax_cxx_compile_stdcxx.html >> >> I attach other minor changes. I didn't test it on a "difficult" >> system. I >> guess that if 'optional' works as advertised, the behavior won't get >> worse. > > Ok, but C++11 is mandatory now, that's the whole point. Looks like > this macro tries both -std=c++11 and -std=c++0x, which is what's > needed; however looks like the macro executes a fairly extensive check > for C++11 coverage, while all that's needed here is unicode string > support. > > I've added this macro and prepared the 20150307 build. Can someone try > courier-unicode-20150307 to see if it builds by default with gcc 4.4.I tried it on my CentOS 6.6 system and it failed. (Although your test program did not give any errors.) $ ./configure ... checking whether g++ supports C++11 features by default... no checking whether g++ supports C++11 features with -std=gnu++11... no checking whether g++ supports C++11 features with -std=gnu++0x... no checking whether g++ supports C++11 features with -std=c++11... no checking whether g++ supports C++11 features with +std=c++11... no checking whether g++ supports C++11 features with -h std=c++11... no checking whether g++ supports C++11 features with -std=c++0x... no checking whether g++ supports C++11 features with +std=c++0x... no checking whether g++ supports C++11 features with -h std=c++0x... no configure: error: *** A compiler with support for C++11 language features is required.
That's fine. I would have to look at what you ended up with in your config.log to confirm this, but I'm fairly certain that the compiler fails that macro's thorough check for C++11 compliance. It checks a bunch of stuff, and gcc 4.4 is not fully C++11 compliant. Which is ok, since only unicode support is needed here.
I'll back that out, and replace it with my own check just for unicode. There'll be another build tomorrow.
pgpH7ytni76Dj.pgp
Description: PGP signature
------------------------------------------------------------------------------ Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford
_______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
