Hi Ken, can you tell if it's trying to run make or jam in multiple
threads (with the -j option)? I've seen several Makefiles in the wild
that are broken and screw up if you try to do that.   I would imagine
that Makefiles generated by automake are set up correctly and immune to
concurrency problems, but you never know (especially in a hybrid
environment like MinGW).

Reed



Ken Taylor wrote:
>> libcrystalspace.a exists and "file" detects it just fine, so I don't know
>> what's going on there. libzlib.dll is an empty (size-0) file, so I really
>> don't know what's going on there.
>>
> *snip*
>> Even stranger -- the first make run made a size-0 wxterangreal.exe.
>> Re-running "make" on the terangreal directory copied over a fully-formed
>> wxterangreal.exe. Looks like some sort of file system synch problem....
>> perhaps something similar occurred with libzlib; but I can't figure out
>> where that file comes from.
> 
> meh:
> 
>  # this is required to fool libtool
>  case $host in
>    *-*-mingw*) touch $INPLACE/lib/libzlib.dll ;;
>  esac
> 
> You people are sneaky :P
> 
> I also see that a patch gets applied to ltmain.sh... however, the patch
> might not be getting applied correctly. The investigation continues...
> 
> -Ken
> 
> 
> _______________________________________________
> vos-d mailing list
> [email protected]
> http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d


_______________________________________________
vos-d mailing list
[email protected]
http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d

Reply via email to