From xemacs-m  Thu Jun 26 20:03:04 1997
Received: from ns.jsys.co.jp (ns.jsys.co.jp [202.33.240.82])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id UAA20922
	for <xemacs-beta@xemacs.org>; Thu, 26 Jun 1997 20:03:02 -0500 (CDT)
Received: from cosmos.jsys.co.jp (cosmos.jsys.co.jp [172.31.80.5])
	by ns.jsys.co.jp (8.8.6/8.8.6) with ESMTP id KAA18701
	for <xemacs-beta@xemacs.org>; Fri, 27 Jun 1997 10:03:03 +0900 (JST)
Received: from skywalk.jsys.co.jp (j-04110.jsys.co.jp [172.31.49.72])
	by cosmos.jsys.co.jp (8.8.6/8.8.6/NOTES) with ESMTP id KAA08467
	for <xemacs-beta@xemacs.org>; Fri, 27 Jun 1997 10:03:03 +0900 (JST)
Received: (from ienaga@localhost) by skywalk.jsys.co.jp (8.8.5/3.5Wpl2) id KAA23888; Fri, 27 Jun 1997 10:02:46 +0900 (JST)
To: xemacs-beta@xemacs.org
Subject: Re: 20.3 Sofia OK on FreeBSD 2.2.2
References: <rys4tal68ou.fsf@skywalk.jsys.co.jp> <199706261113.EAA06871@xemacs.eng.sun.com> <ryswwnh4mga.fsf@skywalk.jsys.co.jp> <m2lo3xb7pa.fsf@altair.xemacs.org>
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
From: Kazuyuki IENAGA <ienaga@jsys.co.jp>
Date: 27 Jun 1997 10:02:45 +0900
In-Reply-To: Steven L Baur's message of "26 Jun 1997 10:22:09 -0700"
Message-ID: <rysn2ocn9hm.fsf@skywalk.jsys.co.jp>
Lines: 30
X-Mailer: Gnus v5.4.59/XEmacs 20.3(beta9) - "Sofia"
X-Face:  czfHfB+cCdftWr4Fwe9^^-!_PKouj^vkcIk4Hg_xxx<~JF.4vv)^7jM;w_w'(UZ#{K&xpz:
 [v3`j%a.u`CP*Tbsm[N0PYlk&+xt3Vd1KZL%'I+v,:*0\(akF?Vf>l_VeOHH]2.Z6^e_O;zDZJW.


Steven L Baur <steve@xemacs.org> writes:

> > Yes.  For instance, SunOS5.x has a crypt in /usr/lib/libc.*,
> 
> (and Linux w/ libc-5)

Yes, most operating systems have the function in libc.
Is there any other OS which does not have the func's entry in libc?
I've checked FreeBSD 2.1 and 2.2, SunOS, Solaris, Linux 2.0.27
w/libc-4, BSD/OS 2.1 and HP-UX 10.
All OSs except FreeBSD have the entry as global symbol in libc...

> > but FreeBSD does not have a crypt function in libc.
> 
> >     1.  If wnn is selected.
> >     2.  If the operating system (opsys) does not have a crypt in libc.
> >     3.  Check if the opsys has libcrypt.*, then add -lcrypt to
> > 	libs_system or libs_standard.
> 
> That sounds O.K.  Isn't that similar to what we currently do with
> libpng to see if it needs a -lz?

Yes.

I reconsidered that this might be a FreeBSD specific.
If so, is it ok to make the configure fat or settle it in freebsd.h?
The policy is to make a solution in the configure?

-- 
kazz

