Mail Archives: cygwin/2004/02/05/00:25:48
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.
Larry Hall Wed, 04 Feb 2004 13:58:47 -0500
>>> 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.
On Wed, 4 Feb 2004, Charles Plager 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/?
Igor Pechtchanski Wed, 4 Feb 2004 18:40:32 -0500 (EST)
> 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?
> 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'?)?
> 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.
--
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/
- Raw text -