On Wed, Nov 21, 2018 at 10:17:31PM -0500, Alain Toussaint via blfs-dev wrote: > Hello, > > It might be useful to add CXX=g++ to the configure script of cups: > > before: > > CC=gcc \ > ./configure --libdir=/usr/lib \ > --with-rcdir=/tmp/cupsinit \ > --with-system-groups=lpadmin \ > --with-docdir=/usr/share/cups/doc-2.2.8 && > make > > after: > > CC=gcc CXX=g++ \ > ./configure --libdir=/usr/lib \ > --with-rcdir=/tmp/cupsinit \ > --with-system-groups=lpadmin \ > --with-docdir=/usr/share/cups/doc-2.2.8 && > make > > Some of the files are in C++ and clang++ have issues when having CFLAGS > and CXXFLAGS turning on flags that work for gcc/g++ and not in > clang/clang++ > > Alain
I wondered why you would want to use clang++ here. But now that my current build has stopped (the g'mic plugin for gimp : I have not looked at the error yet) I took a look at my own log for cups-2.2.8 and I can see your point : checking how to run the C preprocessor... gcc -E checking for clang++... clang++ checking whether we are using the GNU C++ compiler... yes checking whether clang++ accepts -g... yes [ Well, Duh! I suppose that comes from working for apple. ] And eventually among the general number of not-particularly-useful warnings are a number of warning: unknown warning option '-Wno-format-truncation' [-Wunknown-warning-option] If specifying CXX=g++ will disable those warnings, that is good. But does it, or will cups decide to anyway use clang++ ? ĸen -- If a man stands before a mirror and sees in it his reflection, what he sees is not a true reproduction, but a picture of himself when he was a younger man. -- de Selby -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
