Such is my plan B. Just hoping to shortcut it with an inquiry to all if anyone 
knows of a recent change to GRASS source that might cause this.

No obvious change to my system, but may be something not obvious of course

Michael

Michael Barton
School of Human Evolution &Social Change
Center for Social Dynamics & Complexity
Arizona State University

...Sent from my iPad

On Nov 22, 2018, at 7:30 AM, Vaclav Petras 
<wenzesl...@gmail.com<mailto:wenzesl...@gmail.com>> wrote:



On Wed, Nov 21, 2018 at 4:22 PM Michael Barton 
<michael.bar...@asu.edu<mailto:michael.bar...@asu.edu>> wrote:

As far as I can tell, I do not have cpp anywhere in any of the Mac binaries 
I've done, although I do have a C++ compiler installed. All previous versions 
compiled and built without this error, and they run fine. So what was changed 
between 8 October and the release of 7.4.2 that makes configure fail if cpp is 
not found? Where should I look?

Do you mean a change in GRASS GIS source code or your system configuration 
(e.g. updates)? How to decide between them is to configure the last version of 
GRASS GIS which worked for you. If you can configure and compile from scratch 
that old version but not the new one, you can try a version in between these 
two, the go to beginning of this sentence (aka bisect). This way you find the 
change in GRASS GIS. In case both the old and the new version don't configure, 
the change is in your system.




On Nov 12, 2018, at 9:04 PM, Vaclav Petras 
<wenzesl...@gmail.com<mailto:wenzesl...@gmail.com>> wrote:

Since it's complaining about /lib/cpp,

./configure: line 5164: /lib/cpp: No such file or directory

I would say the problem is not zlib, but missing C++ compiler (at least on my 
machine, /lib/cpp eventually points to /usr/bin/cpp-5), although I don't know 
why ./configure would catch that problem earlier since a successful report 
contains:

  C compiler:                 clang -O2 -Wall -pedantic -Wextra
  C++ compiler:               clang++ -std=c++14 -fexceptions

The checking phase reports only about C compiler, so the difference is perhaps 
there.

checking for gcc... clang
checking whether the C compiler (clang -O2 -Wall -pedantic -Wextra -s) works... 
yes
checking whether the C compiler (clang -O2 -Wall -pedantic -Wextra -s) is a 
cross-compiler... no
checking whether we are using GNU C... yes
checking whether clang accepts -g... yes



On Fri, Nov 9, 2018 at 10:58 PM Michael Barton 
<michael.bar...@asu.edu<mailto:michael.bar...@asu.edu>> wrote:
>
> I could see that it could not find zlib in the configure output. I don't know 
> why, since I DO have zlib in the appropriate place
>
> MIchael
>
> On Nov 9, 2018, at 4:21 PM, Markus Neteler 
> <nete...@osgeo.org<mailto:nete...@osgeo.org>> wrote:
>
> Just scroll to the end of the file.
>
>
> ; return 0; }
> configure:5066: checking for socket in -lsocket
> configure:5083:
> /Applications/GRASS-7.4.2.app/Contents/Resources/bin/clang -o conftest
> -g -O2    -I/Applications/GRASS-7.4.2.app/Contents/Resources/include
> -L/Applications/GRASS-7.4.2.app/Contents/Resources/lib conftest.c
> -lsocket   1>&5
> ld: library not found for -lsocket
> clang-4.0: error: linker command failed with exit code 1 (use -v to
> see invocation)
> configure: failed program was:
> #line 5072 "configure"
> #include "confdefs.h"
> /* Override any gcc2 internal prototype to avoid an error.  */
> /* We use char because int might match the return type of a gcc2
>    builtin and then its argument prototype would still apply.  */
> char socket();
>
> int main() {
> socket()
> ; return 0; }
> configure:5131: checking for location of zlib includes
> configure:5157: checking for zlib.h
> configure:5165: /lib/cpp
> -I/Applications/GRASS-7.4.2.app/Contents/Resources/include conftest.c
>
> /dev/null 2>conftest.out
>
> ./configure: line 5164: /lib/cpp: No such file or directory
> configure: failed program was:
> #line 5160 "configure"
> #include "confdefs.h"
> #include <zlib.h>

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to