Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Wed, 4 Feb 2004 18:40:32 -0500 (EST) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Charles Plager cc: cygwin AT cygwin DOT com Subject: Re: Is it possible to move emacs from one computer to another? In-Reply-To: <40217F74.7020804@physics.ucla.edu> Message-ID: References: <40210ECD DOT 9080901 AT physics DOT ucla DOT edu> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040204110844 DOT 039b73b0 AT 127 DOT 0 DOT 0 DOT 1> <40212892 DOT 6070701 AT physics DOT ucla DOT edu> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040204135449 DOT 039b6280 AT 127 DOT 0 DOT 0 DOT 1> <40217F74 DOT 7020804 AT physics DOT ucla DOT edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 4 Feb 2004, Charles Plager wrote: > Larry Hall wrote: > > OK. I'd suggest building a debug version and just try running it in gdb > > until you see the problem. This should be pretty easy to do for crash > > anyway. I'd recommend starting with this. > > I'm not particularly experienced at building large packages so I have a > few questions: > > 1) Do I just get the source from http://ftp.gnu.org/pub/gnu/emacs/? No, you download the Cygwin source using setup.exe by checking the 'Src' box for the package. Note that by design of setup.exe, if you have a version of the package installed, you can only download the source for that version. > 2) Are there special cygwin build procedures? When I typed 'configure' > (a script that came with emacs), it simply said: > cplager AT pointyjr> configure > loading cache ./config.cache > checking host system type... i686-pc-cygwin > configure: error: Emacs hasn't been ported to `i686-pc-cygwin' systems. > Check `etc/MACHINES' for recognized configuration names. Most Cygwin packages come with Cygwin-specific documentation that should be in /usr/share/doc/Cygwin/-.README for newer packages. That README file should contain build procedures on Cygwin, the exact configuration options used to build the binary package, etc. > 3) When past hurdle #2, how do I force a debug build? (simply > 'make DEBUG=yes'?)? > > Thanks for your help, > Charles Most likely that information will be in the Cygwin-specific README as well. If not, you could try setting CC="gcc -g" and CXX="g++ -g". You may also have to disable stripping of the executables. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/