The latest stable version in portage is 0.4.4.2 but the latest stable in sourceforge is 0.4.5.0. Reproducible: Always Steps to Reproduce: 1. cp k3d-0.4.4.2.ebuild k3d-0.4.5.0.ebuild 2. Change line 11, SRC_URI="mirror://sourceforge/k3d/${P}-src.tar.bz2" to: SRC_URI="mirror://sourceforge/k3d/${P}.tar.bz2" 3. emerge k3d Actual Results: Builds and launches fine.
See the 0.4.5.0 ebuild posted in bug 102936
*** Bug 102936 has been marked as a duplicate of this bug. ***
From k3d-0.4.5.0-2/modules/javascript/js/src/fdlibm/k_standard.c #if _LIB_VERSION == _IEEE_ && !(defined(DARWIN) || defined(XP_MACOSX)) int errno; # define EDOM 0 # define ERANGE 0 #else # include <errno.h> #endif Is quite wrong and faults on glibc systems with tls check
(In reply to comment #1) > See the 0.4.5.0 ebuild posted in bug 102936 That bug was marked as a duplicate and closed. It was also reported as not working on bug 99619. However, the simple instructions I originally posted here worked for me. Here is a quick diff of the posted and my ebuild: < # $Header: /var/cvsroot/gentoo-x86/media-gfx/k3d/k3d-0.4.4.2.ebuild,v 1.3 2005/04/02 19:27:02 lu_zero Exp $ --- > # $Header: /var/cvsroot/gentoo-x86/media-gfx/k3d/k3d-0.4.5.0.ebuild,v 1.0 2005/08/23 13:44:59 lu_zero Exp $ 7c7 < IUSE="truetype doc python" --- > IUSE="truetype doc python ruby" 11c11 < SRC_URI="mirror://sourceforge/k3d/${P}-2.tar.bz2" --- > SRC_URI="mirror://sourceforge/k3d/${P}.tar.bz2" 15c15 < KEYWORDS="~x86 ~sparc ~ppc ~amd64" --- > KEYWORDS="~amd64 ~ppc ~sparc ~x86" 28,30c28,29 < python? ( >=dev-lang/python-2.3 )" < < S=${WORKDIR}/${P}-2 --- > python? ( >=dev-lang/python-2.3 ) > ruby? ( virtual/ruby )" 44c43 < local myconf="--with-plib --without-graphviz --without-new-pnmtotiff" --- > local myconf="--with-plib --without-graphviz" 57a57,60 > use ruby \ > && myconf="${myconf} --with-ruby=`ruby -rrbconfig -e 'puts Config::CONFIG["archdir"]'`" \ > || myconf="${myconf} --without-ruby" > 59c62 < econf "CXXFLAGS=${CXXFLAGS}" $myconf || die --- > econf "CXXFLAGS=${CXXFLAGS}" || die Note that ruby support might be broken. I haven't tried it. I also posted my ebuild on this bug report. I'm not sure why this one works and Timothy's doesn't--must be beginner's luck. One more note--cvs sources were recently modified and it now builds on 64-bit systems. Guess it is time to start working on a 0.5.0.x ebuild. --Dan
Created attachment 66647 [details] 0.4.5.0 ebuild The ebuild posted on bug 102936 didn't work on my system but this ebuild did. --Dan
Ah, @ comment #3
Just for the record, this ebuild doesn't work for me. Same netpbm error as I got with the other one (see bug 99619) Jim
Did you check out comment #9 in bug 99619? << I added netpbm-10.28 to /etc/portage/package.mask on my system, downgraded to the last stable version, netpbm-10.20 then emerged k3d and it seems fine now. Perhaps this is a netpbm bug? >> I have been building k3d from their CVS sources and it is working fine for me. Maybe it is time to abandon trying to get 0.4.5.0 working and start a 0.5.0.x ebuild. --Dan
k3d 0.5.0.33 now in portage