Thank you for your help in diagnosing the problem. And the information about not putting additional software in /opt/local.
The make process unfortunately failed again. Making all in src make[1]: Entering directory '/home/rstephan/hdf5-1.8.14/src' make all-am make[2]: Entering directory '/home/rstephan/hdf5-1.8.14/src' CC H5detect.o H5detect.c:115:19: warning: size of 'd_g' is 12800 bytes [-Wlarger-than=] H5detect.c:149:1: error: unknown type name 'sigjmp_buf' H5detect.c: In function 'sigsegv_handler': *********** # grep sigjmp_buf /usr/include/setjmp.h typedef long sigjmp_buf[_SIGJBLEN]; typedef int sigjmp_buf[_SIGJBLEN]; extern int sigsetjmp(sigjmp_buf, int) __RETURNS_TWICE; extern void siglongjmp(sigjmp_buf, int) __NORETURN; # grep setjmp.h src/H5detect.c ************ There seems to be more issues with missing includes. Thank You, Richard -----Original Message----- From: Keith Wesolowski via smartos-discuss [mailto:[email protected]] Sent: Monday, November 24, 2014 10:29 AM To: [email protected]; a b Subject: Re: [smartos-discuss] Compiling HDF5 On Mon, Nov 24, 2014 at 04:21:11PM +0100, a b via smartos-discuss wrote: > > H5Fint.c: In function 'H5F_build_actual_name': > > H5Fint.c:1572:27: error: 'PATH_MAX' undeclared (first use in this > > function) > > PATH_MAX is defined in /usr/include/limits.h. Please check which .h files > H5Fint.c is including, and fgrep for "limits.h" in them. > > If none of the header files include it, add the following line to one > of them, or even to H5Fint.c (least preferred): > > #include <limits.h> If the C file were including headers that in turn included limits.h, this problem could not be occurring. So there's no point grepping around for it. To be more specific, the header should be included by the file that references its contents. So if PATH_MAX is being used in foo.h, then foo.h should have the above #include; if it's being used in H5Fint.c, then H5Fint.c should have the #include, etc. Adding more includes to random headers is not preferred at all; there is a simple and specific way to tell what file should be including the header. Without being deeply familiar with this software, I cannot tell you exactly which file(s) require change. You need to see where PATH_MAX is being referenced. ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/24882246-6ef95fdc Modify Your Subscription: https://www.listbox.com/member/?&; Powered by Listbox: http://www.listbox.com The information in this email is confidential and may be legally privileged against disclosure other than to the intended recipient. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please immediately delete this message and inform the sender of this error. ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
