Re: [Mingw-cross-env-list] Preparation of Release 2.11

[Volker Grabsch]

Tony Theodore <address@hidden> schrieb:
> Freeimage is also failing, I've attached the log

I'll have to investigate that.

> and also config.status from xerces.

Okay, I had a look at it. The xerces stuff is very strange.
The ./configure script contains code to generate config.status.
Lines 20048-20058 say:

    cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
    exec 5>>config.log
    {
      echo
      sed 'h;s/./-/g;s/^.../## /;s/...$/ ##/;p;x;p;x' <<_ASBOX
    ## Running $as_me. ##
    _ASBOX
      $as_echo "$ac_log"
    } >&5

    _ACEOF

So the generated config.status should contain the following code:

    exec 5>>config.log
    {
      echo
      sed 'h;s/./-/g;s/^.../## /;s/...$/ ##/;p;x;p;x' <<_ASBOX
    ## Running $as_me. ##
    _ASBOX
      $as_echo "$ac_log"
    } >&5

However, it instead contains this code (lines 531-539):

    exec 5>>config.log
    {
      echo
      sed 'h;s/./-/g;s/^.../## /;s/...$/ ##/;p;x;p;x' <<_ASBOX
    ## Running $as_me. ##
    elSBOX
      $as_echo "$ac_log"
    } >&5

It contains "elSBOX" where the end marker "_ASBOX" should be.
So the generated config.status shell script doesn't find an end
for that here-document, which causes the error.

How could that happen? What mechanism inside Solaris could
have replaced "_ASBOX" with "elSBOX"? (i.e. replaced "_A" with "el")

Could you check whether the unpacked ./configure script is correct
under Solaris? Maybe the xerces source tarball triggers a bug in the
Solaris "tar" commmand, resulting in an invalid unpacked ./configure
script?


Greets,

    Volker

-- 
Volker Grabsch
---<<(())>>---
Administrator
NotJustHosting GbR