At 03:21 PM 11/12/99 -0500, Phil C wrote:
>I am now terribly confused, the man page for compat_freebsd ofcourse warns
>that it could be outdated... But it says that you will need to have
>complimentary libs for the kernel to be able to run FreeBSD apps. 
> [...]

I would recommend two things:

1) Rather than attempting to get the right library setup by hand, just get
pkgsrc and install the package emulators/freebsd_lib. (and while you're at
it, you may as well install emulators/suse_linux too - *NOT* Linux_SuSE!)

2) Use a simpler test case than wine. AFAIK, the current version of wine
uses threads (or something like that) that aren't supported on
NetBSD-release. Older versions can be built on NetBSD native just as easily
as on FreeBSD, but if the new version can't be built native on NetBSD, I'd
bet that you won't be able to run the FreeBSD version either. (BTW, Wine is
also available for NetBSD in pkgsrc - emulators/wine and
emulators/wine-current).

To test your FreeBSD compat, try something like the FreeBSD version of
NetScape (although it seems most people are using the Linux version) or the
FreeBSD version of the rc5des cracker from distributed.net (be sure to edit
the binary to give "NetBSD" as the system rather than "FreeBSD", and sign
up for the "NetBSD Users" team!)

In case you don't already have it, pkgsrc is available from
ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-current/pkgsrc.tar.gz. Or, if you've
installed CVS, you can check it with:

declare -x CVSROOT=:pserver:anoncvs@anoncvs.netbsd.org:/cvsroot
cvs login
(give "anoncvs" as the password)
cvs co pkgsrc

This will allow you to get updates by just going into the pkgsrc directory
and doing "cvs update". Hundreds of applications already ported to NetBSD,
available simply by cd'ing to a directory and typing "make install".

At 03:21 PM 11/12/99 -0500, Phil C wrote:
>I am now terribly confused, the man page for compat_freebsd ofcourse warns
>that it could be outdated... But it says that you will need to have
>complimentary libs for the kernel to be able to run FreeBSD apps. Ok, but I
>have FreeBSD's 3.2 copy of ldd and FBSD's 3.2 copy of /usr/lib/libc.so.3, and
>I have my NBSD 1.4.1 copy of /usr/lib/libc.so.12.40 and FBSD's ldd still
>works. Now I also have the FBSD copy of wine-99.04.??.tgz (package) along
with
>all of the required shared libs that it wants, and ofcourse I do not have the
>NBSD counterparts since they do not seem to exist. Right now tho wine is
>executed but nothing ever happens, wether I specify a file to run, tell it
>to debug.. anything. It just never does anything?
>
>mez# fwine -debug /c/Program\ Files/CuteFTP/cuteftp.exe 
>mez# echo $?
>0
>
>Oh, fwine is a bash function which automaticly sticks in the -config dir for
>me (/emul/freebsd/etc/wine.conf). Ofcourse I have tried it without the
>function, tho it makes no difference.
>
>That is a Win16 app, which I got to test the whole process, and as you can
see
>it goes no where and does nothing. Any thoughts on what could be happeneing
>here?
>
>I have run FBSD's ldconfig as decribed in the man page, I have installed all
>the necessary libs for FBSD in the /emul/freebsd dir... I am not sure what
>to do next? Is this because of threads? ... So far anything that I try to
>compile on NetBSD 1.4.1 that wnats threads fails, and wine is no different, I
>tried to compile it and it failed around the threads (as did the Apple
>Streaming QuickTime server and TCL with threads).
>
>
>thanks
>phil
>