RE: Debug version of cygwin dll

RE: Debug version of cygwin dll

[Polley Christopher W]

Thanks,  my apologies for asking a FAQ; I didn't see it on the list.  I'll
give these methods a try and see how it goes.

Having done the make/make install from my source tree, do I have to repair
anything now?  Where can I find more information on the rationale behind not
building in the src directory?

Why does the README in the cygwin package say:
>It is now possible to automatically configure and build a variety of
>tools with one command.  To build all of the tools contained herein,
>run the ``configure'' script here, e.g.:
>
>	./configure 
>	make 

if this is the incorrect way to do it?

-Chris

> -----Original Message-----
> From:	egor duda [SMTP:deo@logos-m.ru]
> Hi!
> 
> Wednesday, 05 December, 2001 Peter Buckley peter.buckley@cportcorp.com
> wrote:
> 
> PB> You need to bunzip2 and untar the src, then cd to 
> PB> /usr/src/cygwin-1.3.5-3 (or wherever you extracted it to) and do the 
> PB> following:
> 
> PB> mkdir build
> PB> cd build
> PB> ../configure
> PB> make
> PB> make install
> 
> please, don't make wrong suggestions!
> 
> this way is _wrong_. for a correct way, check the FAQ, particularly
> question "How do I rebuild the tools on my NT box?"
> 
> cygwin sources also contain a file how-to-debug-cygwin.txt which
> contains several debugging hints.
> 
> Egor.            mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19
> 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Debug version of cygwin dll

[Gerrit P. Haase]

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

Hallo Polley,

Am 2001-12-05 um 22:30 schriebst du:

>>       ./configure
>>       make 

> if this is the incorrect way to do it?

This script is from Ch. Wilson (The Master of Puppets;)

Ciao,

Gerrit P. Haase                            mailto:gp@familiehaase.de
-- 
=^..^=

[-- Attachment #2: cygwin-build --]
[-- Type: application/octet-stream, Size: 2680 bytes --]

#!/bin/bash
export src=/winsup/src
export inst=/winsup/build/inst

build=i686-pc-cygwin
target=i686-pc-cygwin

case $1 in
  conf*) ${src}/configure --build=${build} --target=${target} \
  --srcdir=${src} --prefix=/usr \
  --exec-prefix=/usr --sysconfdir=/etc --libdir=/usr/lib \
  --includedir=/nonexistent/include \
  --with-included-gettext 2>&1 | tee log.configure
  ;;
  build*) make CFLAGS=-O2 tooldir=/usr  2>&1 | tee log.make
  make info CFLAGS=-O2 tooldir=/usr 2>&1 | tee log.make-info
  ;;
  check*) make CFLAGS=-O2 tooldir=/usr check 2>&1 | tee log.check
  ;;
  clean*) make CFLAGS=-O2 tooldir=/usr clean 2>&1 | tee log.clean
  ;;
  install*) make install prefix=$inst/usr exec_prefix=$inst/usr \
  bindir=$inst/usr/bin libdir=$inst/usr/lib \
  sysconfdir=$inst/etc includedir=$inst/usr/include \
  tooldir=$inst/usr 2>&1 | tee log.install
  make install-info prefix=$inst/usr exec_prefix=$inst/usr \
  bindir=$inst/usr/bin libdir=$inst/usr/lib \
  sysconfdir=$inst/etc includedir=$inst/usr/include \
  tooldir=$inst/usr 2>&1 | tee log.install-info
  rm -rf $inst/usr/etc 
  rm -f $inst/usr/info/dir
  ;;
  strip*) (cd ${inst} ; find . -name "*.exe" | xargs strip )
  ;;
  package*) (cd ${inst} ; 
    find . -name "*.exe" | xargs strip ;
	rm usr/lib/lib[cgm].a
	for i in c g m
	do
		ln -s libcygwin.a usr/lib/lib$i.a
	done
    tar cvjf ../mingw-new.tar.bz2 usr/bin/mingwm10.dll \
             usr/include/mingw usr/lib/mingw ;
    tar cvjf ../w32api-new.tar.bz2 usr/include/w32api \
             usr/lib/w32api ;
    tar cvjf ../cygwin-new.tar.bz2 usr --exclude='usr/bin/mingwm10.dll' \
             --exclude='usr/include/mingw' --exclude='usr/lib/mingw' \
             --exclude='usr/include/w32api' --exclude='usr/lib/w32api' \
             --exclude='usr/bin/runtest' --exclude='usr/info/dejagnu.info*' \
             --exclude='usr/share/dejagnu' )
  ;;
  packdeb*) (cd ${inst} ; 
	rm usr/lib/lib[cgm].a
	for i in c g m
	do
		ln -s libcygwin.a usr/lib/lib$i.a
	done
    tar cvjf ../mingw-new-debug.tar.bz2 usr/bin/mingwm10.dll \
             usr/include/mingw usr/lib/mingw ;
    tar cvjf ../w32api-new-debug.tar.bz2 usr/include/w32api \
             usr/lib/w32api ;
    tar cvjf ../cygwin-new-debug.tar.bz2 usr --exclude='usr/bin/mingwm10.dll' \
             --exclude='usr/include/mingw' --exclude='usr/lib/mingw' \
             --exclude='usr/include/w32api' --exclude='usr/lib/w32api' \
             --exclude='usr/bin/runtest' --exclude='usr/info/dejagnu.info*' \
             --exclude='usr/share/dejagnu' )
  ;;
  *) echo 'argument required: configure, build, install, strip, package, packdebug'
  echo    '                   [check, clean]'   
  ;;
esac


[-- Attachment #3: Type: text/plain, Size: 214 bytes --]

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Debug version of cygwin dll

[egor duda]

Hi!

Thursday, 06 December, 2001 Polley Christopher W PolleyChristopherW@JohnDeere.com wrote:

PCW> Having done the make/make install from my source tree, do I have to repair
PCW> anything now?

just delete the source tree, unpack in again, rebuild in separate
directory.

PCW> Where can I find more information on the rationale behind not
PCW> building in the src directory?

in mailing list archives. many people, including core cygwin
developers, find it preferable to make builds in separate directory
not only for cygwin, but for any autoconf-managed package. So,
in-place configure is unmaintained therefore unsupported therefore not
recommended. believe me, building in separate tree makes a _lot_ of
things easier, once you're accustomed to it :)

PCW> Why does the README in the cygwin package say:
>>It is now possible to automatically configure and build a variety of
>>tools with one command.  To build all of the tools contained herein,
>>run the ``configure'' script here, e.g.:
>>
>>       ./configure 
>>       make

PCW> if this is the incorrect way to do it?

because it's not cygwin README. it's generic GNU package README. i
admit that it may be not clear.

Egor.            mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Debug version of cygwin dll

[Peter Buckley]

Ah. I guess that would be the wrong part :-)
I don't ever build inside the source tree. I don't install the source, I 
just download it, and I manually extract to 
srcdir=/cygdrive/d/compile-dir and then

cd /cygdrive/d/compile-dir
mkdir build
../configure
make

I just assumed (and I know what that does, sorry) that people would use 
the /usr/src default location where the source was installed, and not be 
silly like me and create their own separate directory for compilation. Ha!

I stand corrected,
Peter

John Peacock wrote:

> Peter Buckley wrote:
> 
>>I don't do the "make install" part- is that the wrong part? Otherwise
>>the part about
>>
>>cd srcdir
>>mkdir build
>>../configure
>>make
>>
>>
> 
> The first line in the FAQ on rebuilding the tools:
> 
>   Note: You must build in a directory outside the source tree. 
>                                       -------
> 
> Note, _not_ below the srcdir.  Just because you haven't had a problem doesn't
> mean that your way is the correct way.
> 
> John
> 
> 


-- 
Your mouse has moved.
Windows NT must be restarted for the change to take effect.
Reboot now?  [OK]

--


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Debug version of cygwin dll

[John Peacock]

Peter Buckley wrote:
> 
> I don't do the "make install" part- is that the wrong part? Otherwise
> the part about
> 
> cd srcdir
> mkdir build
> ../configure
> make
> 

The first line in the FAQ on rebuilding the tools:

  Note: You must build in a directory outside the source tree. 
                                      -------

Note, _not_ below the srcdir.  Just because you haven't had a problem doesn't
mean that your way is the correct way.

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Debug version of cygwin dll

[Peter Buckley]

I don't do the "make install" part- is that the wrong part? Otherwise 
the part about

cd srcdir
mkdir build
../configure
make

builds a the cygwin1.dll quite well on NT and win2k. And the FAQ, docs, 
readmes, MLA, etc lacked any information to help me in my search to 
learn how to successfully build the cygwin1.dll. Gerrit Haase and some 
other posters got me working okay though, in case I forgot to say thanks.

Thanks,
Peter

egor duda wrote:

> Hi!
> 
> Wednesday, 05 December, 2001 Peter Buckley peter.buckley@cportcorp.com wrote:
> 
> PB> You need to bunzip2 and untar the src, then cd to 
> PB> /usr/src/cygwin-1.3.5-3 (or wherever you extracted it to) and do the 
> PB> following:
> 
> PB> mkdir build
> PB> cd build
> PB> ../configure
> PB> make
> PB> make install
> 
> please, don't make wrong suggestions!
> 
> this way is _wrong_. for a correct way, check the FAQ, particularly
> question "How do I rebuild the tools on my NT box?"
> 
> cygwin sources also contain a file how-to-debug-cygwin.txt which
> contains several debugging hints.
> 
> Egor.            mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19
> 
> 


-- 
Your mouse has moved.
Windows NT must be restarted for the change to take effect.
Reboot now?  [OK]

--


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Debug version of cygwin dll

[egor duda]

Hi!

Wednesday, 05 December, 2001 Peter Buckley peter.buckley@cportcorp.com wrote:

PB> You need to bunzip2 and untar the src, then cd to 
PB> /usr/src/cygwin-1.3.5-3 (or wherever you extracted it to) and do the 
PB> following:

PB> mkdir build
PB> cd build
PB> ../configure
PB> make
PB> make install

please, don't make wrong suggestions!

this way is _wrong_. for a correct way, check the FAQ, particularly
question "How do I rebuild the tools on my NT box?"

cygwin sources also contain a file how-to-debug-cygwin.txt which
contains several debugging hints.

Egor.            mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Debug version of cygwin dll

[Peter Buckley]

You need to bunzip2 and untar the src, then cd to 
/usr/src/cygwin-1.3.5-3 (or wherever you extracted it to) and do the 
following:

mkdir build
cd build
../configure
make
make install

Also, I don't know if you need to manually export CFLAGS=-g, just don't 
strip the dll after you build it. IIRC when you build anything it has 
the debug info included, but the binaries are shipped stripped :-)

Another thing- if you plan on debugging another cygwin1.dll with this 
debug version of the cygwin1.dll, search for "running independent 
site:cygwin.com" on google, there is an excellent discussion (don't try 
this at home kids) about running two independent cygwin1.dll's.

HTH,
Peter

Polley Christopher W wrote:

> Hello,
> 
> I'm trying to build cygwin(-1.3.5.3) with the debug symbols included.  I
> exported CFLAGS=-g, then did ./configure, make, and make install; but only
> the .a libraries were built.  Is there more info available about the
> makefile targets in this package?  The README doesn't mention it and it's
> not obvious (to me) from inspection of the Makefile.  How does one build the
> dlls? (or are debug versions available in a tarball?)
> 
> Thanks,
> Chris
> 
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 
> 


-- 
Your mouse has moved.
Windows NT must be restarted for the change to take effect.
Reboot now?  [OK]

--


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Debug version of cygwin dll

[Polley Christopher W]

Hello,

I'm trying to build cygwin(-1.3.5.3) with the debug symbols included.  I
exported CFLAGS=-g, then did ./configure, make, and make install; but only
the .a libraries were built.  Is there more info available about the
makefile targets in this package?  The README doesn't mention it and it's
not obvious (to me) from inspection of the Makefile.  How does one build the
dlls? (or are debug versions available in a tarball?)

Thanks,
Chris


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/