Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.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 <pechtcha@cs.nyu.edu>
Reply-To: cygwin@cygwin.com
To: Charles Plager <cplager+cygwin@physics.ucla.edu>
cc: cygwin@cygwin.com
Subject: Re: Is it possible to move emacs from one computer to another?
In-Reply-To: <40217F74.7020804@physics.ucla.edu>
Message-ID: <Pine.GSO.4.56.0402041835550.8094@slinky.cs.nyu.edu>
References: <40210ECD.9080901@physics.ucla.edu> <6.0.1.1.0.20040204110844.039b73b0@127.0.0.1> <40212892.6070701@physics.ucla.edu> <6.0.1.1.0.20040204135449.039b6280@127.0.0.1> <40217F74.7020804@physics.ucla.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@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/<package>-<version>.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@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.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/