On Sun, 6 Jul 2003, Erik Hofman wrote:

> I've been working on making the autoconf scripts for SimGear cleaner and
> much more flexible. It would be nice if some developers want to try it out:
>
> http://www.a1.nl/~ehofman/fgfs/download/SimGear-configure_clean.diff
>
> I would particularly be interested in the result of the prthread test
> for FreeBSD developers.

The diff does not apply to the current SimGear copy.

% patch -p0 < SimGear-configure_clean.diff
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- /home/erik/src/CVS/fgfs/SimGear/configure.ac       Sun Jul  6
13:11:22 2003
|+++ configure.ac       Sun Jul  6 18:48:26 2003
--------------------------
Patching file configure.ac using Plan A...
Hunk #1 failed at 136.
Hunk #2 failed at 203.
Hunk #3 failed at 226.
Hunk #4 succeeded at 419 (offset -18 lines).
3 out of 4 hunks failed--saving rejects to configure.ac.rej

(Even -l doesn't work its usual wonder).

However, browsing the diff shows that it removes the -pthread flags from
CFLAGS. One can dispute the wisdom of FreeBSD's pthreads implementation,
but the ugly contortion that's in the configure script seems to be the
only supported way of doing it on FreeBSD. Yes, you might get lucky
adding -D_REENTRANT and linking explicitly against -lc_r, but I've been
through too much pain and suffering by trying to cut corners with
pthreads (for easing autoconf) to recommend this.

If you don't specify -pthread, -lc will be dragged in impicitly and this
can cause all sorts of breakage. As far as I know, -lc_r should never be
linked explicitly.

I do not like FreeBSD's solution (heaven knows I much prefer BSDi's
implementation), but it seems the OS maintainers won't budge on this
one.

Cheers,

                                -- Bert

-- 
Bert Driehuis -- [EMAIL PROTECTED] -- +31-20-3116119
If the only tool you've got is an axe, every problem looks like fun!

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

Reply via email to