Re: Build problem

[Hardy G. <nt...@ma...>]

Hans-Bernhard Bröker wrote:
> Hardy Griech wrote:
>>
>> Although this might seem to be outdated, I have the same problem on a 
>> cygwin installation with the same versions of automake and automake like 
> 
> I'm sure it works with current autoconf and automake on Cygwin --- if 
> that Cygwin contains enough other things.  I have current Cygwin 
> versions of just about everything GNU related to development installed 
> here (including TeX, auto tools, pkg-config, gd, png, font utils and 
> whatnot).

I hoped so too.  But reality check showed that it does not work... :-(

Ethan Merrit was so kind to send me a configure from a working linux build.

Comparison shows a lot of differences.  Not very astonishing is that 
AC_MSG_WARN in my version has not been expanded.  Interesting is that 
PKG_CHECK_MODULES has not been expanded too.

Unfortunately I'm not an automake/autoconf expert, but perhaps this is a 
problem of some include paths (m4?).

Here is a small snippet of the problem area CAIRO:

<mine>
     PKG_CHECK_MODULES(CAIRO, cairo >= 0.9.0,
     HAVE_CAIRO=1,     AC_MSG_WARN([Cairo can't be found. The wxWidgets 
terminal will not be compiled
     enable_wxwidgets_ok=no
   )
</mine>

<ethans>
if test $pkg_failed = yes; then
         CAIRO_PKG_ERRORS=`$PKG_CONFIG --errors-to-stdout --print-errors 
"cairo >= 0.9.0"`
         # Put the nasty error message in config.log where it belongs
         echo "$CAIRO_PKG_ERRORS" 1>&5

             { echo "$as_me:$LINENO: WARNING: Cairo can't be found. The 
wxWidgets terminal will not b
echo "$as_me: WARNING: Cairo can't be found. The wxWidgets terminal will 
not be compiled." >&2;}
     enable_wxwidgets_ok=no

elif test $pkg_failed = untried; then
             { echo "$as_me:$LINENO: WARNING: Cairo can't be found. The 
wxWidgets terminal will not b
echo "$as_me: WARNING: Cairo can't be found. The wxWidgets terminal will 
not be compiled." >&2;}
     enable_wxwidgets_ok=no
</ethans>

I have omitted a lot of bunch beforehand which contains something like 
'--exists --print-errors' and so on.  Everybody with a working configure 
can see that.

My conclusion is still that there is something broken in the (my?) 
cygwin installation with automake and so on.  Perhaps you 
(Hans-Bernhard) has set a path to get m4/automake/autoconf working?

Hardy