Re: Help: build emacs in cygwin (fwd)

Re: Help: build emacs in cygwin (fwd)

[Angelo Graziosi]

Regarding the 'MAKE' questions, I would suggest to try the Cygwin patched
version of make that accepts PATH in DOS style:

  http://cygwin.com/ml/cygwin/2006-11/msg00490.html

If I remeber correcly those patches were accepted upstream.


Cheers,

   Angelo.

Re: Help: build emacs in cygwin (fwd)

[Eli Zaretskii]

> Date: Thu, 8 Mar 2007 12:27:03 +0100 (MET)
> From: Angelo Graziosi <Angelo.Graziosi@roma1.infn.it>
> cc: Eli Zaretskii <eliz@gnu.org>
> 
>   http://cygwin.com/ml/cygwin/2006-11/msg00490.html
> 
> If I remeber correcly those patches were accepted upstream.

Yes, they were.

Re: Help: build emacs in cygwin

[Angelo Graziosi]

Eli Zaretskii wrote:

> Strange, that's the version that caused lots of trouble to Angelo
> Graziosi.  Also, he reported problems with debug info generated by
> 3.4.4-2 (can you debug your binary?).

I confirm. 

I have done a build with GCC-3.4.4 (that now is 3.4.4-3, not -2) using the
configure options described here
http://lists.gnu.org/archive/html/emacs-devel/2007-03/msg00722.html
(it differs from mine only because it does not uses XAW3D) but it segment
faults in a few seconds/minutes!

Every time I use GCC-3.4.4 the result is unstable. Instead GCC-4.0.3 gives
results very stable.


Cheers,

   Angelo. 

Re: Help: build emacs in cygwin

[Harald Maier]

Angelo Graziosi <Angelo.Graziosi@roma1.infn.it> writes:

> Eli Zaretskii wrote:
>
>> Strange, that's the version that caused lots of trouble to Angelo
>> Graziosi.  Also, he reported problems with debug info generated by
>> 3.4.4-2 (can you debug your binary?).
>
> I confirm. 
>
> I have done a build with GCC-3.4.4 (that now is 3.4.4-3, not -2) using the
> configure options described here
> http://lists.gnu.org/archive/html/emacs-devel/2007-03/msg00722.html
> (It differs from mine only because it does not uses XAW3D) but it segment
> faults in a few seconds/minutes!
>
> Every time I use GCC-3.4.4 the result is unstable. Instead GCC-4.0.3 gives
> results very stable.

Me too. An Cygwin-Emacs compiled with gcc-3.4.4 is unusable!
Especially, I saw lots of crashes by subprocess handling such as ssh
and with SQLi buffers.

Harald

Re: Help: build emacs in cygwin

[Angelo Graziosi]

Eli Zaretskii wrote:

>> From: "djh" <address@hidden>
>> Date: Tue, 13 Mar 2007 14:51:48 +0900
>> 
>> No. I get the below results.  Same as Angelo, but I think Angelo was
>> trying 
>> to build a native w32 version and had pathname converstion problems.

> No, he was building a Cygwin binary, not a native w32 binary.

Obviously.

I never tried to build a native 32 binary.

I refer always to a pure Cygwin build.


Cheers,

   Angelo.

Re: Help: build emacs in cygwin

[djh]

I did not have the problems that Angelo had. (I do have crash problems, but almost exclusively when using ddskk, a skk based Japanese input method.). 

I believe Angelo also had symbol problems, that is a lack of symbols for debugging.

I believe the problem is not the compiler, but the cygwin x-window implementation.
If if the compiler, then it has been fixed (my 3.4.4 shows an installed date of December 18, 2006).

I mainly have problems (crashes) when using a Japanese input method.  
Which leads me more to believe that the problem is not the compiler but the cygwin x-window implementation. 

> Me too. An Cygwin-Emacs compiled with gcc-3.4.4 is unusable!
> Especially, I saw lots of crashes by subprocess handling such as ssh
> and with SQLi buffers.
> 
> Harald

I just downloaded and built the newest gcc, gcc (GCC) 4.1.3 20070312 (prerelease)
and compiled emacs with it successfully.

I still get:
$ gdb /bin/emacs.exe
GNU gdb 6.5.50.20060706-cvs (cygwin-special)
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-cygwin"...
(gdb) r
Starting program: /bin/emacs.exe
Loaded symbols for /cygdrive/c/WINDOWS/system32/ntdll.dll
Loaded symbols for /cygdrive/c/WINDOWS/system32/kernel32.dll
Loaded symbols for /usr/bin/cygncurses-8.dll
Loaded symbols for /usr/bin/cygwin1.dll
Loaded symbols for /cygdrive/c/WINDOWS/system32/advapi32.dll
Loaded symbols for /cygdrive/c/WINDOWS/system32/rpcrt4.dll
Loaded symbols for /usr/bin/cygjpeg-62.dll
Loaded symbols for /usr/bin/cygpng12.dll
Loaded symbols for /usr/bin/cygz.dll
Loaded symbols for /usr/bin/cygtiff-5.dll
Loaded symbols for /usr/bin/cygungif-4.dll
Loaded symbols for /usr/X11R6/bin/cygX11-6.dll
Loaded symbols for /usr/X11R6/bin/cygICE-6.dll
Loaded symbols for /usr/X11R6/bin/cygSM-6.dll
Loaded symbols for /usr/X11R6/bin/cygXaw-8.dll
Loaded symbols for /usr/X11R6/bin/cygXext-6.dll
Loaded symbols for /usr/X11R6/bin/cygXmu-6.dll
Loaded symbols for /usr/X11R6/bin/cygXt-6.dll
Loaded symbols for /usr/X11R6/bin/cygXp-6.dll
Loaded symbols for /usr/X11R6/bin/cygXau-6.dll
Loaded symbols for /usr/X11R6/bin/cygXpm-4.dll
emacs: standard input is not a tty

Program exited with code 01.

-----

Which leads me to believe it is not a compiler problem.

Darel

Re: Help: build emacs in cygwin

[Jason Rumney]

djh wrote:
> I mainly have problems (crashes) when using a Japanese input method.  
> Which leads me more to believe that the problem is not the compiler but the cygwin x-window implementation. 
>   

I think there is a bug in the interaction between skk and some versions 
of X and/or certain window managers. I've seen lockups and crashes on 
GNU/Linux with certain combinations not involving Emacs or Cygwin.

Re: emacs snapshot tarball test build

[Angelo Graziosi]

djh wrote:

> The only problem is shown below (and maybe it is not a real problem).
>
> --------
> make[1]: Leaving directory `/usr/src/emacs-tmp/emacs-22.0.95/leim'
> cd lib-src; make maybe-blessmail  \
>          MAKE='make' archlibdir='/libexec/emacs/22.0.95/i686-pc-cygwin'
> make[1]: Entering directory `/usr/src/emacs-tmp/emacs-22.0.95/lib-src'
> ../src/emacs -batch --no-site-file --multibyte -l 
> /usr/src/emacs-tmp/emacs-22.0.95/lib-src/../lisp/mail/blessmail.el
> Fatal error (6)make[1]: *** [blessmail] Aborted (core dumped)
> make[1]: Leaving directory `/usr/src/emacs-tmp/emacs-22.0.95/lib-src'
> make: *** [blessmail] Error 2
> ------


This often happens boostraping Emacs on Cygwin.

Workaround: try to build in another nested directory.

Generally, a build with the above problem gives problems!


Cheers,

   Angelo.

Re: emacs snapshot tarball test build

[djh]

Thanks Angelo.  But, one shouldn't have to build in a specific directory, or guess about a directory structure, and this should be an easy thing to fix. 

If it is a semi-hard coded (if should a thing code be) reference or assumption in a Makefile then it should be corrected in my opinion.

It would be good to know why "make" aborted on blessmail.el.  It was reported as
"Fatal error (6)make[1]: *** [blessmail] Aborted (core dumped)" below.

> djh wrote:
> > The only problem is shown below (and maybe it is not a real problem).
> > --------
> > make[1]: Leaving directory `/usr/src/emacs-tmp/emacs-22.0.95/leim'
> > cd lib-src; make maybe-blessmail  \
> >          MAKE='make' archlibdir='/libexec/emacs/22.0.95/i686-pc-cygwin'
> > make[1]: Entering directory `/usr/src/emacs-tmp/emacs-22.0.95/lib-src'
> > ../src/emacs -batch --no-site-file --multibyte -l 
> > /usr/src/emacs-tmp/emacs-22.0.95/lib-src/../lisp/mail/blessmail.el
> > Fatal error (6)make[1]: *** [blessmail] Aborted (core dumped)
> > make[1]: Leaving directory `/usr/src/emacs-tmp/emacs-22.0.95/lib-src'
> > make: *** [blessmail] Error 2
> > ------
> 
> 
> This often happens boostraping Emacs on Cygwin.
> Workaround: try to build in another nested directory.
> Generally, a build with the above problem gives problems!
> 
> Cheers,
>    Angelo.

Regards,
   Darel Henman

Re: emacs snapshot tarball test build

[Angelo Graziosi]

On Fri, 23 Mar 2007, djh wrote:

> 
> Thanks Angelo.  But, one shouldn't have to build in a specific directory, or guess about a directory structure, and this should be an easy thing to fix. 
> 
> If it is a semi-hard coded (if should a thing code be) reference or assumption in a Makefile then it should be corrected in my opinion.
> 
> It would be good to know why "make" aborted on blessmail.el.  It was reported as


> "Fatal error (6)make[1]: *** [blessmail] Aborted (core dumped)" below.


Boostrapping Emacs on Cygwin, one often has "Fatal error
(6)make[1]:..." not only at the end, when installing, with "blessmail",
but also when it starts to compile "el" files or after it has rebuilt the
final version of "emacs.exe".

Theste errors happen at random, without an evident logic.

Usually, changing the build directory (increasing the nested level) solve
the thing (same Emacs CVS source).

So correcting the Makefile left some doubts (but I can err).

Obviously, the bootstrap of the same CVS code on GNU/Linux Kubuntu does
not give any problem.


Cheers,

   Angelo.
 







> 
> > djh wrote:
> > > The only problem is shown below (and maybe it is not a real problem).
> > > --------
> > > make[1]: Leaving directory `/usr/src/emacs-tmp/emacs-22.0.95/leim'
> > > cd lib-src; make maybe-blessmail  \
> > >          MAKE='make' archlibdir='/libexec/emacs/22.0.95/i686-pc-cygwin'
> > > make[1]: Entering directory `/usr/src/emacs-tmp/emacs-22.0.95/lib-src'
> > > ../src/emacs -batch --no-site-file --multibyte -l 
> > > /usr/src/emacs-tmp/emacs-22.0.95/lib-src/../lisp/mail/blessmail.el
> > > Fatal error (6)make[1]: *** [blessmail] Aborted (core dumped)
> > > make[1]: Leaving directory `/usr/src/emacs-tmp/emacs-22.0.95/lib-src'
> > > make: *** [blessmail] Error 2
> > > ------
> > 
> > 
> > This often happens boostraping Emacs on Cygwin.
> > Workaround: try to build in another nested directory.
> > Generally, a build with the above problem gives problems!
> > 
> > Cheers,
> >    Angelo.
> 
> Regards,
>    Darel Henman
> 

Re: emacs snapshot tarball test build

[Eli Zaretskii]

> From: "djh" <henman@it.to-be.co.jp>
> Date: Fri, 23 Mar 2007 10:34:19 +0900
> Cc: djh <henman@it.to-be.co.jp>, emacs-devel@gnu.org
> 
> It would be good to know why "make" aborted on blessmail.el.  It was reported as
> "Fatal error (6)make[1]: *** [blessmail] Aborted (core dumped)" below.

It's not "make" who aborted, it's Emacs.  "make" just printed a
human-readable description of why Emacs died.

Re: Pretest 22.0.97

[Angelo Graziosi]

Cygwin binaries here:

   http://www.webalice.it/angelo.graziosi/Emacs.html


Cheers,

  Angelo.

Re: Build failure on Cygwin

[Angelo Graziosi]

Eric Hanchrow wrote:

> I simply did "cvs co ...", "./configure", "make bootstrap". 
>
> ...
> Fatal error (6)/bin/sh: line 2:   220 Aborted....
>

This often happens in bootstrapping under Cygwin.

Solution: build in a separate directory and/or build from an
"xterm" console (NOT the dos-like console)...

...or use prebuild (22.0.97-pretest) Cygwin binaries from
http://www.webalice.it/angelo.graziosi/Emacs.html.

To build use GCC-4.0.3 or 4.0.4 which seem to give very stable binaries.



Cheers,

   Angelo.

RE: merging Unicode branch and availability of Windows binaries

[Angelo Graziosi]

Drew Adams wrote:

> I asked about Windows binaries. Where will one be able to find a Windows
> binary of Emacs 22?

You will find the Cygwin binaries (which are in any case Windows
binaries!) here:


  http://www.webalice.it/angelo.graziosi/Emacs.html


For the moment, there you will find only Emacs pretest 22.0.99 waiting for
the release 22!



Cheers,

   Angelo.

RE: merging Unicode branch and availability of Windows binaries

[Drew Adams]

> > Where will one be able to find a Windows binary of Emacs 22?
>
> You will find the Cygwin binaries (which are in any case Windows
> binaries!) here: http://www.webalice.it/angelo.graziosi/Emacs.html

Thanks, Angelo. Actually, I was looking for non-Cygwin (though I didn't
state that), but this is also good to know.

Re: emacs snapshot tarball test build

[Richard Stallman]

    This often happens boostraping Emacs on Cygwin.

    Workaround: try to build in another nested directory.

Is this documented in the installation instructions?
In etc/PROBLEMS?

If not, would someone like to add that info?

Re: emacs snapshot tarball test build

[Eli Zaretskii]

> From: Richard Stallman <rms@gnu.org>
> Date: Fri, 23 Mar 2007 00:37:11 -0400
> Cc: henman@it.to-be.co.jp, emacs-devel@gnu.org
> 
>     This often happens boostraping Emacs on Cygwin.
> 
>     Workaround: try to build in another nested directory.
> 
> Is this documented in the installation instructions?
> In etc/PROBLEMS?
> 
> If not, would someone like to add that info?

These are not workarounds that I'd recommend adding to PROBLEMS.

In general, if the problem only happens during bootstrap, and doesn't
have a good workarounds, I'd say let's ignore it.  Most Emacs users
will never bootstrap.

Build failure on Cygwin

[Eric Hanchrow]

[-- Attachment #1: Type: text/plain, Size: 60 bytes --]

I simply did "cvs co ...", "./configure", "make bootstrap".

[-- Attachment #2: typescript --]
[-- Type: application/octet-stream, Size: 290369 bytes --]

[-- Attachment #3: emacs.exe.stackdump --]
[-- Type: application/octet-stream, Size: 1086 bytes --]

Stack trace:
Frame     Function  Args
00217128  7C802532  (000006FC, 0000EA60, 000000A4, 00217170)
00217248  6109773C  (00000000, 00000000, 00000000, 00000000)
00217338  610952BB  (00000000, 00217460, 00217428, 00217300)
00217398  6109579B  (002173B0, 00000000, 00000094, 200D5805)
00217458  61095952  (000000DC, 00000006, 202DC801, 0022CE64)
00217478  61092D88  (00000006, 60030000, 002175A8, 610977FC)
00217568  61017B60  (000006FC, 0000EA60, 000000A4, 002175B0)
00217688  610977FC  (00000000, 0000005B, 0000005B, 00000001)
00217778  610952BB  (00000000, 202DC801, 002178A8, 610977FC)
002177D8  6109579B  (002177F0, 00000000, 00000094, 00217838)
00217898  61095952  (000000DC, 00000006, 002178C8, 201500A2)
002178A8  61092D88  (00000000, 20690000, 211C1708, 204CBEC0)
002178C8  201500A2  (206A16E8, 211C1708, 00007760, 00000000)
00217908  20150C91  (FFFDE000, FFFFFFFF, 00217938, 2004ABF3)
00217978  2014F5F4  (00003FD0, 0021BDD0, 002179A8, 200F187E)
00217988  200F1BE1  (00003FD0, 0021BDD0, 00000000, 202DC831)
End of stack trace (more stack frames may be present)

[-- Attachment #4: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

Re: Build failure on Cygwin

[Eli Zaretskii]

> Date: Thu, 12 Apr 2007 20:12:06 -0700
> From: "Eric Hanchrow" <eric.hanchrow@gmail.com>
> 
> I simply did "cvs co ...", "./configure", "make bootstrap".

Thanks for reporting.

Is this the first time you try to bootstrap the Cygwin build?  If so,
please look for relevant entries in PROBLEMS, and make sure you don't
trip on any of the Cygwin-related gotchas mentioned there.  In
particular, the one with GCC versions.

Re: Build failure on Cygwin

[Eric Hanchrow]

>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:

    >> Date: Thu, 12 Apr 2007 20:12:06 -0700 From: "Eric Hanchrow"
    >> <eric.hanchrow@gmail.com>
    >>
    >> I simply did "cvs co ...", "./configure", "make bootstrap".

    Eli> Thanks for reporting.

    Eli> Is this the first time you try to bootstrap the Cygwin build?

Yes, or at least, the first time in years.

    Eli> If so, please look for relevant entries in PROBLEMS, and make
    Eli> sure you don't trip on any of the Cygwin-related gotchas
    Eli> mentioned there.  In particular, the one with GCC versions.

I did indeed have gcc 3.4.4, which that file mentions doesn't work.
Thanks, that explains the failure.  But it leaves me with two
questions:

* Couldn't "configure" detect the gcc version, and fail if it finds
  that we're using any of those bad gcc versions on Cygwin?  That
  would have saved me and you time.

* Do I need to build gcc 4 myself from source?  It doesn't appear to
  be available from Cygwin's setup program.

-- 

Re: Build failure on Cygwin

[Eli Zaretskii]

> Cc: "Eric Hanchrow" <eric.hanchrow@gmail.com>,  emacs-devel@gnu.org
> From: Eric Hanchrow <offby1@blarg.net>
> Date: Fri, 13 Apr 2007 08:01:50 -0700
> 
> * Couldn't "configure" detect the gcc version, and fail if it finds
>   that we're using any of those bad gcc versions on Cygwin?  That
>   would have saved me and you time.

I'm not sure this is such a good idea, since the problems that cause
this could be fixed in the near future, and new GCC versions appear
much faster than Emacs releases.  We could be left with gratuitous
failures very soon.

> * Do I need to build gcc 4 myself from source?  It doesn't appear to
>   be available from Cygwin's setup program.

I hope someone who uses Cygwin, like Angelo Graziosi, can help you
here.

Re: Build failure on Cygwin

[Eric Hanchrow]

For what it's worth, I just built gcc 4 from source, which went
perfectly smoothly, and then built emacs from that, which also went
perfectly smoothly.
-- 

Re: Build failure on Cygwin

[Eli Zaretskii]

> From: Eric Hanchrow <offby1@blarg.net>
> Date: Fri, 13 Apr 2007 18:04:29 -0700
> 
> For what it's worth, I just built gcc 4 from source, which went
> perfectly smoothly, and then built emacs from that, which also went
> perfectly smoothly.

Thanks for reporting this, and for trying the Cygwin build in the
first place.

Re: Build failure on Cygwin

[Angelo Graziosi]

Eli Zaretskii wrote:

> I hope someone who uses Cygwin, like Angelo Graziosi, can help you
> here.


Hi Eric,

I have tried to send (by attaching, 3 MB) the Cygwin binaries of GCC-4.0.4
with which the Emacs-cvs build works fine but it seems that something went
wrong and the replay is absent from this list.

In any case I have seen that you have solved building yourself GCC-4 and
this is good.


Cheers,

   Angelo.