Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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: Thu, 5 Feb 2004 11:28:10 -0500 (EST)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Charles Plager <cplager+cygwin AT physics DOT ucla DOT edu>
cc: cygwin AT cygwin DOT com
Subject: Re: howto build a debug version of a Cygwin package, and debug it
In-Reply-To: <40225B42.2070205@physics.ucla.edu>
Message-ID: <Pine.GSO.4.56.0402051113140.3804@slinky.cs.nyu.edu>
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> <Pine DOT GSO DOT 4 DOT 56 DOT 0402041835550 DOT 8094 AT slinky DOT cs DOT nyu DOT edu> <40225B42 DOT 2070205 AT physics DOT ucla DOT edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 5 Feb 2004, Thomas L Roche wrote:

> Charles Plager: thanks for starting this thread, since I may also need
> to go down this road :-( However, please continue it under this more
> demonstrative Subject: line.

Switched the subject as per the above request.

On Thu, 5 Feb 2004, Charles Plager wrote:

> Igor Pechtchanski wrote:
>
> >>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.
>
> Is there a way I can get the cygwin source (or binarys for that matter)
> for emacs 21.1.something?

Umm, I don't think so.  AFAIR, Cygwin emacs was only packaged starting at
version 21.2.

> >>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/<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.
>
> If the answer to the above question is no, would it be possible to
> "reconstruct" the cygwin source by using the build procedures for
> 21.2.11 on a 21.1.X release?

The above question being "are there special Cygwin procedures"?  I suggest
reviewing the README file to find out.  Also, there may have been
Cygwin-specific patches applied to 21.2.* that won't work with 21.1.X.
IOW, you can certainly try it, but be prepared to invest some effort.

> >>3) When past hurdle #2, how do I force a debug build? (simply
> >>'make DEBUG=yes'?)?
> >
> > 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.
>
> Again, pardon my ignorance, but what does "stripping of the executables"
> mean and how would I avoid it?
>
> Thanks,
>   Charles

It means stripping debug information out of the executables.  This could
happen in one of a few ways: by explicitly calling the "strip" utility, by
passing a "-s" flag to "install", or by passing a flag (which I can't
recall at the moment) to "ld" during linking.  If the documentation
doesn't shed any light on this, you'll have to figure out which method is
used to strip the executables and how to disable it.
	Igor
P.S. Many configures support the "--enable-debugging" flag.  I don't have
the emacs source, but perhaps someone else can
-- 
				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/