On *BSD'ish systems bare-system headers are in /usr/include/ but not
application headers which are located in /usr/local/include/ nor "third"
party libraries with possible headers.
This is just a convention in a *BSD'ish world (and actually it makes the
system really tight and clean).
The file which couldnt be found was giconv.h which not part of the
bare-system in FreeBSD. Other variants of *BSD does not have this header
either as it is part of the giconv library.
SunOS/Solaris is a *BSD variant.
I have only just joined the maillists so I didnt know about the SSL
stuff...but I can see a lot of commits happening in that area in the
cvs.
With configure, wouldnt it be possible to test where is giconv and then
just have the -I set for that ?
On FreeBSD it is necessary to edit the Makefile manually and have
-I/usr/local/include set:
/usr/local/include/libxml2/libxml/encoding.h:30: warning: No include
path in which to find giconv.h
In file included from gwlib/charset.h:23,
from gwlib/gwlib.h:36,
from gw/msg.h:13,
from gw/sms.h:33,
from gw/sms.c:9:
/usr/local/include/libxml2/libxml/encoding.h:30: warning: No include
path in which to find giconv.h
Then adding the switch and it just compiles with warnings:
/usr/lib/libc.so: WARNING! setkey(3) not present in the system!
/usr/lib/libc.so: warning: this program uses gets(), which is unsafe.
/usr/lib/libc.so: warning: mktemp() possibly used unsafely; consider
using mkstemp()
/usr/lib/libc.so: WARNING! des_setkey(3) not present in the system!
/usr/lib/libc.so: WARNING! encrypt(3) not present in the system!
/usr/lib/libc.so: warning: tmpnam() possibly used unsafely; consider
using mkstemp()
/usr/lib/libc.so: warning: this program uses f_prealloc(), which is not
recommended.
/usr/lib/libc.so: WARNING! des_cipher(3) not present in the system!
/usr/lib/libc.so: warning: tempnam() possibly used unsafely; consider
using mkstemp()
I have no need for SSL at this time so I havent done an effort to get
the des_cipher.
On Thu, Dec 27, 2001 at 01:35:38PM +0100, Stipe Tolj wrote:
> > 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
--
med venlig hilsen / Best Regards
Bernino Lind - [EMAIL PROTECTED]
catpipe Systems ApS - www.catpipe.net
Best done *BSD solutions
