Next Version of preflight.sh out <VirusChecked>

[Lars Sonchocky-Helldorf]

After days of lingering around I finaly put together a new version of 
preflight.sh.

What's new?

- you can save the output to a file now
- you can save debug information to a file now (well, that's a feature 
that only I need ;-))
- preflight.sh now prints information regarding the importance of the 
various bits and pieces (that rating is not final now)
- some formating of the output

please test it and send your preflight.out and preflight.debug to me if 
you discover something strange.

to Jay McCarthy:

> On OpenBSD 3.0-stable, it dies on line 2993: "syntax error near
> unexpected token 'else'"

should be fixed now. I asume you used the very first version of 
preflight.sh (were there was an error indeed)

to Tristan Alexander McLeay:

> Result: FreeBSD 4.5-RELEASE; it appears to work fine except that it 
doesn't
> find ffcall stuff even though it's installed.

Don't know what is going wrong here. checked the differences between 
GNUstep-base's configure script and preflight.sh but found nothing 
relevant. What result gives the configure script of GNUstep-base to you?

to Dennis Leeuw:

> Still have the following problem:
> checking for ffi.h... no
> checking for forwarding callback in runtime... no
> checking for callback.h... yes
> checking FFI library usage... none
> preflight.sh: warning: No ffcall interface library found
>
>         ! GNUstep requires the ffcall library to do invocations and DO
>         ! Make sure this library is installed (see installation 
instructions)
>         ! Otherwise DO will not be compatible with other systems

Again, I don't know the cause for this. Could you also please send me your 
preflight.out, preflight.debug and possibly the output of GNUstep-base's 
configure to me?

to David Ayers:

> preflight.sh
>      The script tests for ObjC-threads before testing for ObjC. So if 
ObjC
> doesn't work it reports that threads don't work. May be the check for 
ObjC could
> be placed infront of ObjC threads. (I was mislead by believing the lack 
of
> threading had to do with the objc problems)

I took the code for this check from configure of GNUstep-base. The code 
for testing "wether objc really works" depends a little on the check for 
threading. One more time, I have no clue what is causing this. Does the 
configure script recognize threading properly? Please send me all your 
output too.



Now I won't miss the opportunity to thank everybody who helped me in this 
case: Many thanks to all!

greetings, Lars

preflight.sh
Description: Binary data