Kilian,

On Sat, Mar 12, 2005 at 09:09:04PM +0100, Kilian Krause wrote:
> i've come to find a large problem debugging the FTBFS listed in
> http://buildd.debian.org/fetch.php?&pkg=gnugk&ver=2%
> 3A2.2.1-4&arch=alpha&stamp=1110438256&file=log&as=raw

> Quite apparently i have neither a gdb backtrace (Cannot access memory at
> address 0x202dbae000000000) nor a serious strace output
> (http://backend.verfaction.de/~kk/gnugk.strace) to hand in. The only
> guess i have so far is that either the dynlinker or gcc output code is
> broken in latest SID. As i have no idea about where to start digging for
> the issue causing this within the gcc-internals or glibc-changes, i'd
> welcome a guiding light on how to get this solved.

> As this seems be the only blocker for the pkg-voip packages to proceed
> into Sarge, we'd be quite relieved to see this solved. Whoever has a
> proposal what to try or which patch to add, i'm all ears.

Attached is the final patch resulting from my investigations.  -Os is the
culprit here, as originally suspected. :)

Cheers,
-- 
Steve Langasek
postmodern programmer
--- gnugk-2.2.1.orig/Makefile.in
+++ gnugk-2.2.1/Makefile.in
@@ -104,6 +104,8 @@
 # GK version infomation
 STDCCFLAGS     += [EMAIL PROTECTED]@ [EMAIL PROTECTED]@ [EMAIL PROTECTED]@
 
+OPTCCFLAGS     = -O2
+
 # special dependency to ensure version.cxx is rebuilt each time gnugk is 
recompiled
 # so the proper build timestamp is included
 versionts.h: $(subst version.cxx,,$(SOURCES)) $(HEADERS) 
$(OH323_LIBDIR)/$(OH323_FILE) $(PW_LIBDIR)/$(PTLIB_FILE)

Attachment: signature.asc
Description: Digital signature

Reply via email to