Gerhard Wesp wrote:

> well, I ditched all Linux/Solaris/IRIX... variants and finally arrived
> at FreeBSD and now I'm happy :)

Welcome to a wonderful world ....  didn't I already tell this to Curt ?
O.k., I didn't ditch IRIX but I arrived at FreeBSD as well, not far in
the past.
Most of the stuff you encountered has already been worked on, fixes are
in CVS. In case you want to build PLIB yourself, then grab the current
PLIB CVS and apply the patch files from
/usr/ports/x11-toolkits/plib/files/ from your FreeBSD system - assuming
you installed the "ports collection". This is worth the effort because
some FlightGear-related fixes made it into PLIB CVS recently.

> Step 4.  Download SimGear and FlightGear sources, unzip and compile.
> Observations for SimGear:
> The configure script appears to be broken (doesn't check for openal):

This is not entirely correct. It actually _does_ the check for
'openal', but due to recent changes in the FreeBSD threads library
world it does not link the correct thread lib for the 'openal' test.
'-lpthread' would be correct - I already tried to fix this but my
knowledge of the autoconf/automake stuff is limited and 'trial and
error' didn't lead to the desired result. Usually I manually add
'-lpthread' to the 'LIBS'-token for the openal-test. Later on you have
to add '-lpthread' to the 'openal_LIBS'-token in
SimGear/simgear/sound/Makefile and FlightGear/src/Main/Makefile.
Surprisingly I usually find '-lusbhid' in the openal_LIBS for
FlightGear which I replace  :-)

> C++ error at screen/extensions.cpp:116:  dlerror() returns char const*
>   and not char*.  Straightforward fix: Replace by
> 
>         char const *error = dlerror();

Fixed in CVS.

> configure script doesn't seem to check for usb libraries:
> Symptoms:
> /usr/X11R6/lib/libplibjs.a(jsBSD.o)(.text+0xb02): In function
> `jsJoystick::rawRead(int*, float*)':
> : undefined reference to `hid_get_data'

Fixed in CVS.

> The prototype of a not very helpful error message :-).  Which directory
> exactly are you trying to open and why the h*ll can't you?  Educated
> guess: ulOpenDir() (plib) tries to open() the directory in read-write
> mode.  Running fgfs as root works around the problem.

Well, it usually depends on the permissions  :-)  I didn't see this
problem, but I do have read/write acces to my base package directory.

> Tomorrow I'll know more!

Good luck,
        Martin.
-- 
 Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------

_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to