Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 112756 - emerge klibido fails on amd64
Summary: emerge klibido fails on amd64
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Net-news project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-16 15:59 UTC by erik_vandenbergh
Modified: 2005-11-17 00:53 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description erik_vandenbergh 2005-11-16 15:59:43 UTC
While trying to emerge the latest klibido, i only get this error:

configure: error: expected an absolute directory name for --datadir:
'/var/tmp/portage/klibido-0.2.4.1/image/'/usr/share

!!! ERROR: net-nntp/klibido-0.2.4.1 failed.
!!! Function econf, Line 485, Exitcode 0
!!! econf failed

Reproducible: Always
Steps to Reproduce:
1.(echo net-nntp/klibido ~amd64 >> /etc/portage/package.keywords)
2. emerge klibido
3.

Actual Results:  
The above mentioned error appears and emerge stops

Expected Results:  
compiled :)

Portage 2.0.51.22-r3 (default-linux/amd64/2005.0, gcc-3.4.4, glibc-2.3.5-r2,
2.6.13-gentoo-r3 x86_64)
=================================================================
System uname: 2.6.13-gentoo-r3 x86_64 AMD Athlon(tm) 64 Processor 3000+
Gentoo Base System version 1.6.13
dev-lang/python:     2.3.5-r2, 2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.20
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=athlon64 -O2 -pipe -fomit-frame-pointer"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d"
CXXFLAGS="-march=athlon64 -O2 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/
ftp://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.belnet.be/gentoo-portage"
USE="amd64 X alsa audiofile avi berkdb bitmap-fonts bzip2 cdr crypt cups curl
dvd emboss exif expat fam ffmpeg flac foomaticdb fortran gif glut gpm gstreamer
gtk gtk2 idn imagemagick imlib java jpeg kde lcms lzw lzw-tiff mng motif mp3
mpeg mysql ncurses network nls nptl nptlonly nvidia ogg opengl oss pam pcre
pdflib perl png python qt quicktime readline recode samba sdl ssl symlink tcltk
tcpd tiff truetype truetype-fonts type1-fonts udev usb userlocales vorbis xine
xml2 xmms xpm xv xvid zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
Comment 1 erik_vandenbergh 2005-11-16 16:08:11 UTC
(In reply to comment #0)

It is very strange that when i manually compile the source of klibido, found on
sourceforge, with the same ./configure options, it does not complain.
Comment 2 erik_vandenbergh 2005-11-16 17:11:10 UTC
(In reply to comment #1)   
   
Anyway, the solution is to change this line in the ebuild 
  
--datadir='${D}'/usr/share   
into   
--datadir=/usr/share   
   
and this for both the klibido 2.4.1 as for the klibido 2.3.1-r1 ebuild  
and ofcourse update the Manifest accordingly.  
Comment 3 Diego Elio Pettenò (RETIRED) gentoo-dev 2005-11-17 00:51:13 UTC
This isn't matter for KDE herd actually... 
Comment 4 Diego Elio Pettenò (RETIRED) gentoo-dev 2005-11-17 00:53:22 UTC
But I fixed it anyway, as it was my changes that made the problem appear. 
FWIW, before yesterday the --datadir=/usr/share parameter was later added by 
kde eclass, overriding the --datadir='${D}'/usr/share parameter passed by the 
ebuild. I don't know the reason for suck a dirt hack but I can't see any 
problem within the makefiles, and it was anyway ignored with the old kde 
eclass so I just plainly removed it, leaving to econf to specify the datadir. 
 
net-news herd: hope I didn't do anything wrong.