Bug 92282 – Haddock-0.6-r3 Compile Failure

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Timm Murray 2005-05-11 12:09:58 UTC]

Using gcc 3.3.5

Reproducible: Always
Steps to Reproduce:
1. emerge haddock

Actual Results:  
make INSTALLING=0 BIN_DIST=0 - --no-print-directory -r all
/opt/ghc/bin/ghc -H16m -O -package network -fglasgow-exts -cpp    -c
FastMutInt.hs -o FastMutInt.o  -ohi FastMutInt.hi
Warning: retaining unknown function `__i686.get_pc_thunk.bx' in output from C
compiler
Prologue junk?: .globl __stack_smash_handler
.globl __stginit_FastMutInt
	.type	__stginit_FastMutInt, @function
__stginit_FastMutInt:
	movl	%ebx, 40(%esp)
	call	__i686.get_pc_thunk.bx
	addl	$_GLOBAL_OFFSET_TABLE_, %ebx
	movl	__guard@GOT(%ebx), %eax
	movl	(%eax), %eax
	movl	%eax, 16(%esp)

make[3]: *** [FastMutInt.o] Error 255
make[2]: *** [all] Error 2
make[1]: *** [all] Error 1
make[1]: Leaving directory
`/var/tmp/portage/haddock-0.6-r3/work/haddock-0.6/haddock'
make: *** [build] Error 1

!!! ERROR: dev-haskell/haddock-0.6-r3 failed.
!!! Function src_compile, Line 47, Exitcode 2
!!! make failed
!!! If you need support, post the topmost build error, NOT this status message.

Expected Results:  
Compiled sucessfully

Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130,
glibc-2.3.4.20041102-r1, 2.6.10-gentoo-r4 i686)
=================================================================
System uname: 2.6.10-gentoo-r4 i686 Intel(R) Celeron(R) CPU 2.40GHz
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.5 [2.3.5 (#1, Apr 27 2005, 09:00:16)]
dev-lang/python:     2.3.5
sys-apps/sandbox:    [Not Present]
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.8.5-r3, 1.5, 1.6.3, 1.7.9, 1.4_p6, 1.9.5
sys-devel/binutils:  2.15.92.0.2-r7
sys-devel/libtool:   1.5.16
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=i686 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config
/usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=i686 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://mirrors.tds.net/gentoo http://gentoo.netnitco.net
ftp://gentoo.netnitco.net/pub/mirrors/gentoo/source/
http://mirror.tucdemonic.org/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 3dnow X Xaw3d acpi alsa apache2 apm arts avi berkdb bitmap-fonts bonobo
cdr crypt cups curl dga directfb doc dvd eds emboss encode esd ethereal fam flac
foomaticdb fortran gd gdbm gif gnome gpm gps gstreamer gtk gtk2 gtkhtml guile
hardened imagemagick imlib ipv6 jabber jack java jikes joystick jpeg kde libg++
libwww mad maildir mikmod mmx motif mozilla mp3 mpeg ncurses nls ogg oggvorbis
opengl oss pam pcmcia pda pdflib perl png pnp postgres python qt quicktime
readline ruby samba sdl slang spell sqlite sse ssl svga tcpd tiff truetype
truetype-fonts type1-fonts unicode usb videos vorbis wxwindows xine xinerama xml
xml2 xmms xosd xv zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY

[Comment 1 Duncan Coutts (RETIRED) 2005-05-11 17:38:19 UTC]

Yes, it looks like a mangler conflict with your hardened gcc. What version of ghc-bin is it that you are using?

We thought that we were sucessfully disabling the hardened gcc stuff (as ghc is not compatible with it) but obviously we'll need to take another look at it. Thanks for the report.

[Comment 2 Timm Murray 2005-05-12 05:38:09 UTC]

ghc-bin is at version 6.2.2

[Comment 3 Duncan Coutts (RETIRED) 2005-05-18 03:55:45 UTC]

We believe a workaround is to use the non'-bin' version of the ghc ebuild,
ie "ghc" rather than "ghc-bin". I'm afraid this does take quite some time to
emerge. If you do try this workaround we would apreciate if you could report
back if it does or does not solve the problem you found.

We would like the "-bin" version to be as fully working as the source ebuild, so
we will continue to look into this bug.

[Comment 4 Duncan Coutts (RETIRED) 2005-05-18 03:58:29 UTC]

Sorry, just realised of course that if you can't compile Haddock then you wont
be able to compile anything else, like ghc! So my suggested workaround is
nonsense, ignore it!

[Comment 5 Daniel Black (RETIRED) 2005-06-20 19:23:10 UTC]

similar to bug 36154? 

[Comment 6 Duncan Coutts (RETIRED) 2006-03-11 09:45:52 UTC]

I've now comitted a updated ghc-6.4.1-r2 and ghc-bin-6.4.1 ebuilds to portage. I have tested emerging ghc-bin and ghc from scratch while using a hardened gcc profile.

Tim, would you mind trying an emerge sync and seeing if this now works for you?

[Comment 7 Duncan Coutts (RETIRED) 2006-03-24 05:02:54 UTC]

I think this is fixed in the current stable ghc-bin-6.4.1 and ghc-6.4.1-r2.

I'm closing this bug now but feel free to re-open this bug or file and new one if anyone finds there's still a problem.