> 4. The configure.in does not setup -I/usr/local/include, so if thats not > part of your gmake configuration per default, you should edit the > generated makefile and add this include flag, in the CFLAG variable.
-I/usr/local/include should not be necessary, due that system headers should reside in /usr/include and for all optional (xml2, ssl, mysql) libs we are testing in configure.in and modify CFLAGS accordingly. Have you any scenario where pre-defined inclusion of /usr/local/include would be necessary? We may then include it. > Also take care that configure.in have some static defined paths to > various dependencies such as ssl libraries. That's to be changed and has been announced already. The SSL detection will be smarter. > 5. Use 'gmake' instead of make to do all compilations That's also valid for Sun's make on Solaris 2.x. [EMAIL PROTECTED] ------------------------------------------------------------------- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de ------------------------------------------------------------------- wapme.net - wherever you are
