Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!

Full Text Bug Listing

pike-7.6.6 compiles and installs cleanly on amd64, but it is currently masked.

However, the ebuild required a little extra work to get it to work correctly; I had to unmask another package and add -fPIC to my CFLAGS in order to get it to compile properly.

Pike depends on dev-lib/nettle-1.10 to work.  I had to add ~amd64 to the keywords to emerge it, and once I had it still wouldn't link correctly against pike until I re-emerged it with:

CFLAGS="-fPIC -O2" emerge nettle

I was then able to use:

CFLAGS="-fPIC -O2" emerge pike

...and pike compiled and installed.  There were a few warnings during the install process, but they indicated that they were non-fatal errors.  In any event, pike runs all of the sample programs from http://pike.ida.liu.se/ that I've tried.

I'm no ebuild expert or I would submit some kind of patch.  Following is my emerge --info output:

Portage 2.0.50-r9 (default-amd64-2004.2, gcc-3.3.4, glibc-2.3.4.20040619-r0, 2.6.7-gentoo-r11)
=================================================================
System uname: 2.6.7-gentoo-r11 x86_64 4
Gentoo Base System version 1.5.1
ccache version 2.3 [enabled]
Autoconf: sys-devel/autoconf-2.59-r4
Automake: sys-devel/automake-1.8.5-r1
ACCEPT_KEYWORDS="amd64 ~amd64"
AUTOCLEAN="yes"
CFLAGS="-O2"
CHOST="x86_64-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /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"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache"
GENTOO_MIRRORS="http://gentoo.binarycompass.org http://gentoo.ccccom.com http://gentoo.llarian.net/ ftp://gentoo.ccccom.com"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
USE="X alsa amd amd64 apache2 apm arts avi berkdb crypt curl dvd encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 guile imlib java jpeg junit kde libg++ libwww log4j mikmod motif mozilla moznocompose moznoirc mpeg multilib mysql ncurses nls nogcj oggvorbis opengl oss pam parse-clocks pcap pcmcia pdflib perl png postgres python qt quicktime radeon readline ruby samba sdl slang speedo speex spell ssl tcltk tcpd threads truetype wxwindows xalan xerces xml xml2 xmms xv zlib"

tracking ;)

I can confirm that compiling with -fPIC (I had to set it in make.conf and not
add it to the command line) works and generates an apparently good pike.  I
emerged it so I could use mkdvd.pike.  I have now run that successfully and
made a good DVD.  I suggest that the -fPIC be added to the two ebuilds and they
be unmasked for amd64

I'll test nettle and pike (+deps, which all are fortunatly already x86_64ified
;) shortly on amd64, and eventuall mark them ~.

I added ~amd64 to the nettle ebuild, including the -fPIC part.

Can anybody who take a look if we really need -fPIC for pike, too?
I just built it and had no problems without -fPIC.

duh, I think this bug is cursed, in every comment I write there is at least one
spelling or grammar mistake ;)

Tested it out, it's working well.

Fixed in CVS. Thanks for reporting.