"make check-deps" does not detect missing Python.h. #409

New Issue

nejucomo · 2008-05-06T19:43:34Z

nejucomo commented

2008-05-06 19:43:34 +00:00

When installing Tahoe from source, I overlooked the install.html mention that I needed python dev headers.

I ran make check-dep which succeeded (it gave no output and had a zero exit status, which I assume is success).

-but when I run "make" the build fails. Could check-deps tell me Python.h is missing?

When installing Tahoe from source, I overlooked the install.html mention that I needed python dev headers. I ran make check-dep which succeeded (it gave no output and had a zero exit status, which I assume is success). -but when I run "make" the build fails. Could check-deps tell me Python.h is missing?

nejucomo added the

labels 2008-05-06 19:43:34 +00:00

nejucomo added this to the eventually milestone 2008-05-06 19:43:34 +00:00

zooko commented

2008-05-06 20:47:05 +00:00

Does the build fail in a way that clearly indicates that you are missing Python.h?

It isn't convenient for either Python or GNU make code to check for a header file. The best way to do it is "try it and see", or use the autoconf approach, which actually embeds a little C program inside itself and attempts to compile that program to see if it works.

Does the build fail in a way that clearly indicates that you are missing Python.h? It isn't convenient for either Python or GNU make code to check for a header file. The best way to do it is "try it and see", or use the autoconf approach, which actually embeds a little C program inside itself and attempts to compile that program to see if it works.