Re: [coLinux-devel] [PATCH] buld-colinux.sh-20040421

[Robert C. <rw...@al...>]

On Thursday, April 22, 2004, at 08:29  PM, gboutwel wrote:
> I wasn't recommending the removal of wine, just temporarily removing
> the setting/mechanism that's linked wine to *.exe's.  But I guess
> it's enough to show that that was the problem.  Did the FC1 that
> you where having problems, also, have WINE such that it handles
> *.exe's?

On the FC1 box, wine is not installed.  From a quick browse through the 
logs, it looks as though FLTK requires X, which is not installed on 
this FC1 box:
   http://cwelug.org/~rwcitek/colinux/fc1.fltk.logs/bad/

> I'm learning about it as I go,

I know that feeling.  :)

> Among others.  I don't know that coLinux should be lugging
> around a bunch of patches for the configure scripts for libraries
> it depends on.  So probably the best approach is to file an bug
> report (developer would really like it if it came with an patch)
> about this with the project, allowing them to develop/improve
> the scripts as they best see fit.

I agree.  But sometimes you gotta do whatever it takes to make things 
work.  We can refactor  and file bug reports later.

> The short term solution for allowing them to co-exist, is to
> figure out how WINE is linked to handle EXEs and determine if
> there is an way to TEMPORARILY disable that while doing cross-compile
> builds like this.

Yup.  But I'd first like to test the .exe files to see if they actually 
work under Windows.  Will be reading up on that shortly.

Regards,
- Robert