public inbox for cygwin-apps-cvs@sourceware.org help / color / mirror / Atom feed
From: jturney@sourceware.org To: cygwin-apps-cvs@sourceware.org Subject: [setup - the official Cygwin setup program used to install Cygwin and keep it up to date] branch master, updated. release_2.876-7-g77ddbf4 Date: Wed, 07 Dec 2016 12:47:00 -0000 [thread overview] Message-ID: <20161207124703.6764.qmail@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=cygwin-apps/setup.git;h=77ddbf45b5c16faeb0c7247ded8c7a5f6fb59b19 commit 77ddbf45b5c16faeb0c7247ded8c7a5f6fb59b19 Author: Jon Turney <jon.turney@dronecode.org.uk> Date: Tue Nov 22 16:05:58 2016 +0000 Strip symbols to setup.dbg As noted in https://cygwin.com/ml/cygwin/2016-11/msg00254.html debugging the distributed setup executable is a lost cause at the moment. Preserve symbols so it's not quite as hopeless. Note: to debug the distributed setup executable with gdb, it will be necessary to decompress the setup executable with 'upx -d', and, if the .dbg file has been renamed to match the renamed setup executable, explicitly load it into gdb with the 'symbol-file' command. Signed-off-by: Jon Turney <jon.turney@dronecode.org.uk> Diff: --- Makefile.am | 5 ++++- configure.ac | 14 +------------- 2 files changed, 5 insertions(+), 14 deletions(-) diff --git a/Makefile.am b/Makefile.am index 3498c9d..12ad5ca 100644 --- a/Makefile.am +++ b/Makefile.am @@ -297,7 +297,10 @@ setup-src: .PHONY: strip upx strip: all - $(STRIP) -s setup$(EXEEXT) + $(OBJCOPY) --add-gnu-debuglink=/dev/null --only-keep-debug setup$(EXEEXT) setup.dbg + $(OBJCOPY) --strip-all setup$(EXEEXT) + $(OBJCOPY) --add-gnu-debuglink=setup.dbg setup$(EXEEXT) setup$(EXEEXT) + upx: strip @if [ -e `which upx` ]; then\ upx --best --lzma setup$(EXEEXT) ;\ diff --git a/configure.ac b/configure.ac index 32a3b01..42ad3e2 100644 --- a/configure.ac +++ b/configure.ac @@ -48,20 +48,8 @@ AC_CANONICAL_BUILD AC_CANONICAL_HOST AC_PROG_LIBTOOL -dnl AC_CHECK_TOOL(AR, ar, ar) -dnl AC_SUBST(AR) -dnl AC_CHECK_TOOL(AS, as, as) -dnl AC_SUBST(AS) -dnl AC_CHECK_TOOL(RANLIB, ranlib, ranlib) -dnl AC_SUBST(RANLIB) -dnl AC_CHECK_TOOL(LD, ld, ld) -dnl AC_SUBST(LD) -dnl AC_CHECK_TOOL(DLLTOOL, dlltool, dlltool) -dnl AC_SUBST(DLLTOOL) AC_CHECK_TOOL(WINDRES, windres, windres) -AC_SUBST(WINDRES) -dnl AC_CHECK_TOOL(OBJCOPY, objcopy, objcopy) -dnl AC_SUBST(OBJCOPY) +AC_CHECK_TOOL(OBJCOPY, objcopy, objcopy) AC_CHECK_HEADERS(alloca.h \ errno.h \
reply other threads:[~2016-12-07 12:47 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20161207124703.6764.qmail@sourceware.org \ --to=jturney@sourceware.org \ --cc=cygwin-apps-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).