trunk build failure on windows

trunk build failure on windows

[Sean Sieger]

I just now set up a MinGW environment in Windows 7 on a new machine and
got this here business:

Byte-compile the created files by:
  % emacs -batch -f batch-byte-compile XXX.el
"./../src/oo/i386/emacs.exe" -batch --no-init-file --no-site-file --multibyte  -
l \
            "c:/trunk/leim/../lisp/international/quail" \
            -f batch-byte-compile quail/CCDOSPY.el quail/Punct.el quail/QJ.el qu
ail/SW.el quail/TONEPY.el quail/4Corner.el quail/ARRAY30.el quail/ECDICT.el quai
l/ETZY.el quail/Punct-b5.el quail/PY-b5.el quail/QJ-b5.el quail/ZOZY.el
Wrote c:/trunk/leim/quail/CCDOSPY.elc
Wrote c:/trunk/leim/quail/Punct.elc
Wrote c:/trunk/leim/quail/QJ.elc
Wrote c:/trunk/leim/quail/SW.elc
make[2]: *** [quail/CCDOSPY.elc] Error 255
make[2]: Leaving directory `c:/trunk/leim'
make[1]: *** [all-other-dirs-gmake] Error 2
make[1]: Leaving directory `c:/trunk/nt'
make: *** [bootstrap] Error 2

Re: trunk build failure on windows

[Eli Zaretskii]

> From: Sean Sieger <sean.sieger@gmail.com>
> Date: Fri, 04 Jun 2010 21:48:19 -0400
> 
> I just now set up a MinGW environment in Windows 7 on a new machine and
> got this here business:
> 
> Byte-compile the created files by:
>   % emacs -batch -f batch-byte-compile XXX.el
> "./../src/oo/i386/emacs.exe" -batch --no-init-file --no-site-file --multibyte  -
> l \
>             "c:/trunk/leim/../lisp/international/quail" \
>             -f batch-byte-compile quail/CCDOSPY.el quail/Punct.el quail/QJ.el qu
> ail/SW.el quail/TONEPY.el quail/4Corner.el quail/ARRAY30.el quail/ECDICT.el quai
> l/ETZY.el quail/Punct-b5.el quail/PY-b5.el quail/QJ-b5.el quail/ZOZY.el
> Wrote c:/trunk/leim/quail/CCDOSPY.elc
> Wrote c:/trunk/leim/quail/Punct.elc
> Wrote c:/trunk/leim/quail/QJ.elc
> Wrote c:/trunk/leim/quail/SW.elc
> make[2]: *** [quail/CCDOSPY.elc] Error 255
> make[2]: Leaving directory `c:/trunk/leim'
> make[1]: *** [all-other-dirs-gmake] Error 2
> make[1]: Leaving directory `c:/trunk/nt'
> make: *** [bootstrap] Error 2

Please tell what versions of development tools (GCC, Binutils, Make,
shell, etc.) you have there.

It sounds like it bails out compiling TONEPY.el, is that right?

Re: trunk build failure on windows

[Sean Sieger]

    Please tell what versions of development tools (GCC, Binutils, Make,
    shell, etc.) you have there.

I guess the MinGW project switched hosts and in the process their files
got really screwed up.  A solution is to go to another part of
Sourceforge, and Eli, where up-to-date versions could be had (I've
been under the impression that old MinGW was all there was.)  ... I
thought I was gonna have a field day ...

GCC 4.5
Binutils 2.20
Make 3.81
W32api 3.14 and so on.  Bad news??

    It sounds like it bails out compiling TONEPY.el, is that right?

Yes, TONEPY.el is next.

Re: trunk build failure on windows

[Eli Zaretskii]

> From: Sean Sieger <sean.sieger@gmail.com>
> Date: Fri, 04 Jun 2010 22:44:46 -0400
> 
> GCC 4.5

GCC 4.5 is known to produce bad code, especially in optimized builds.
I'm not sure this problem has anything to do with your failure, but
I'd recommend to downgrade to an earlier version, just in case.

> Yes, TONEPY.el is next.

If you compile it manually, do you see the same problem?

Re: trunk build failure on windows

[Sean Sieger]

    > GCC 4.5

    GCC 4.5 is known to produce bad code, especially in optimized builds.
    I'm not sure this problem has anything to do with your failure, but
    I'd recommend to downgrade to an earlier version, just in case.

    > Yes, TONEPY.el is next.

    If you compile it manually, do you see the same problem?

Yep.  I tried that and thought, `well, how 'bout byte-compiling the
whole directory,' but haven't figured out how to force that ...

Anyway, maybe I'll hear from ya before I get the time to go back to an
earlier GCC (will 4.4 work? and can it an 4.5 co-exist in my MinGW?),
otherwise I'll move back to said earlier GCC.

And another question, given the compilers co-existance, when I
configure, do I use the argument say `--with-gcc=4.4' or something?

Re: trunk build failure on windows

[Eli Zaretskii]

> From: Sean Sieger <sean.sieger@gmail.com>
> Date: Sat, 05 Jun 2010 10:33:11 -0400
> 
> Anyway, maybe I'll hear from ya before I get the time to go back to an
> earlier GCC (will 4.4 work? and can it an 4.5 co-exist in my MinGW?),
> otherwise I'll move back to said earlier GCC.

I think only GCC 4.5 has that problem.

As for coexistence: each version of gcc.exe should be able to find its
own sub-programs (they are installed in different directories whose
name includes the version).  So what I usually do is rename the couple
of executables installed on PATH to something like gcc45.exe and
cpp45.exe, and invoke them by that name when I need.

> And another question, given the compilers co-existance, when I
> configure, do I use the argument say `--with-gcc=4.4' or something?

This is not supported by the current nt/configure.bat.  --with-gcc
means use the compiler named literally "gcc".  You could rename
gcc45.exe to gcc.exe before running configure.bat, though.

(Btw, if the problem is really in GCC 4.5, why would you want to leave
a buggy compiler on your system?  I'd just nuke it.)

Re: trunk build failure on windows

[Sean Sieger]

    (Btw, if the problem is really in GCC 4.5, why would you want to leave
    a buggy compiler on your system?  I'd just nuke it.)

Nuked.  Thank you for your guidance, Eli.