Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 391331 - dev-cpp/eigen-2.0.13 fails tests
Summary: dev-cpp/eigen-2.0.13 fails tests
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Science Related Packages
URL:
Whiteboard:
Keywords:
Depends on: 398545
Blocks:
  Show dependency tree
 
Reported: 2011-11-22 07:42 UTC by Paweł Hajdan, Jr. (RETIRED)
Modified: 2012-02-01 09:11 UTC (History)
2 users (show)

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


Attachments
build.log.gz (dev-cpp:eigen-2.0.13:20111121-202044.log.gz,20.63 KB, application/x-gzip)
2011-11-22 07:42 UTC, Paweł Hajdan, Jr. (RETIRED)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Paweł Hajdan, Jr. (RETIRED) gentoo-dev 2011-11-22 07:42:04 UTC
Created attachment 293379 [details]
build.log.gz

Start 41: sparse_solvers
18/46 Test #41: sparse_solvers ...................***Failed    1.07 sec


Portage 2.1.10.11 (default/linux/x86/10.0/developer, gcc-4.5.3, glibc-2.12.2-r0, 3.0.6-gentoo i686)
=================================================================
System uname: Linux-3.0.6-gentoo-i686-Intel-R-_Core-TM-2_Duo_CPU_P8700_@_2.53GHz-with-gentoo-2.0.3
Timestamp of tree: Mon, 21 Nov 2011 12:00:01 +0000
app-shells/bash:          4.1_p9
dev-java/java-config:     2.1.11-r3
dev-lang/python:          2.7.2-r3, 3.1.4-r3
dev-util/cmake:           2.8.4-r1
dev-util/pkgconfig:       0.26
sys-apps/baselayout:      2.0.3
sys-apps/openrc:          0.8.3-r1
sys-apps/sandbox:         2.5
sys-devel/autoconf:       2.13, 2.68
sys-devel/automake:       1.10.3, 1.11.1
sys-devel/binutils:       2.21.1-r1
sys-devel/gcc:            4.5.3-r1
sys-devel/gcc-config:     1.4.1-r1
sys-devel/libtool:        2.4-r1
sys-devel/make:           3.82-r1
sys-kernel/linux-headers: 2.6.39 (virtual/os-headers)
sys-libs/glibc:           2.12.2
Repositories: gentoo x-portage
ACCEPT_KEYWORDS="x86"
ACCEPT_LICENSE="*"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=i686 -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/config /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c"
CXXFLAGS="-O2 -march=i686 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="assume-digests binpkg-logs collision-protect compress-build-logs distlocks ebuild-locks fixlafiles fixpackages multilib-strict news parallel-fetch protect-owned sandbox sfperms sign splitdebug strict test test-fail-continue unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox"
FFLAGS=""
GENTOO_MIRRORS="http://distfiles.gentoo.org"
LDFLAGS="-Wl,--hash-style=gnu -Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X a52 aac acl acpi alsa berkdb bzip2 cairo cdda cdr cli consolekit cracklib crypt cups cxx dbus device-mapper dri dts dvd dvdr emacs emboss encode exif fam firefox flac fortran gdbm gdu gif git gnome-keyring gnutls gtk iconv icu jpeg lcms libnotify mad mbox mercurial mng modules mp3 mp4 mpeg mudflap ncurses nls nptl nptlonly nss ogg opengl openmp pam pango pcre pdf perl png policykit ppds pppd python qt3support readline sdl secure-delete session snmp spell sqlite ssl startup-notification subversion svg sysfs tcb tcpd threads tiff toolkit-scroll-bars truetype udev unicode usb vorbis x264 x86 xcb xft xinerama xml xorg xulrunner xv xvfb xvid zlib" ALSA_CARDS="ens1371" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan stage tables krita karbon braindump" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx" INPUT_DEVICES="evdev keyboard vmmouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" PHP_TARGETS="php5-3" RUBY_TARGETS="ruby18" USERLAND="GNU" VIDEO_CARDS="vmware vesa vga" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Comment 1 Thomas Capricelli 2011-12-07 20:01:02 UTC
2.0.13 is quite old. Do you still have problem with eigen on gentoo ?
Comment 2 Paweł Hajdan, Jr. (RETIRED) gentoo-dev 2011-12-11 14:32:44 UTC
(In reply to comment #1)
> 2.0.13 is quite old. Do you still have problem with eigen on gentoo ?

That's the latest stable version. Should a more recent version be stabilized?

I'm not going to re-test since this report is not even 30 days old.
Comment 3 Ian Delaney (RETIRED) gentoo-dev 2012-01-10 05:20:56 UTC
gentoo64 eigen # emerge =dev-cpp/eigen-2.0.13 

-- Configuring incomplete, errors occurred!
 * ERROR: dev-cpp/eigen-2.0.13 failed (test phase):
 *   cmake failed

 *     ebuild.sh, line   75:  Called src_test
 *   environment, line 2895:  Called cmake-utils_src_configure
 *   environment, line  798:  Called _execute_optionaly 'src_configure'
 *   environment, line  301:  Called enable_cmake-utils_src_configure

 * The specific snippet of code:
 *       "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die "cmake failed";

It fell over at an earlier stage.  Could not complete the 'configure for the test' phase.
Comment 4 Thomas Capricelli 2012-01-10 19:20:46 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > 2.0.13 is quite old. Do you still have problem with eigen on gentoo ?
> 
> That's the latest stable version. Should a more recent version be stabilized?
> 
> I'm not going to re-test since this report is not even 30 days old.

Of course, 2.0.17 is out and should definitely be used in production / stable tree, see:
http://eigen.tuxfamily.org
Comment 5 Thomas Capricelli 2012-01-10 19:28:04 UTC
i've just renamed last 2.0.16 to my local overlay but i can't manage to emerge. I'm not familiar enough to understand how to fix the pb, but i can explain

 *   The source directory '/var/tmp/portage/dev-cpp/eigen-2.0.17/work/eigen-eigen-2.0.17' doesn't exist

The tarballs are directly provided by the mercurial soft at bitbucket. And recently (~nov 2011), they changed how this stuff works and the directory that the tarballs extracts has changed. We got some reports from BSD with similar problems too.
It used to extract to, say, 'eigen-2.0.17/', and now extracts to 'eigen-eigen-b23437e61a07/' (where the last part is the hash to the mercurial version labelled as '2.0.17').

If someone know how to fix this..
Comment 6 Justin Lecher (RETIRED) gentoo-dev 2012-01-10 19:31:19 UTC
(In reply to comment #4)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > 2.0.13 is quite old. Do you still have problem with eigen on gentoo ?
> > 
> > That's the latest stable version. Should a more recent version be stabilized?
> > 
> > I'm not going to re-test since this report is not even 30 days old.
> 
> Of course, 2.0.17 is out and should definitely be used in production / stable
> tree, see:
> http://eigen.tuxfamily.org


I will take care of this.
Comment 7 Justin Lecher (RETIRED) gentoo-dev 2012-01-10 19:57:13 UTC
okay I played around and there where random errors in the testsuite when repeated. I assume it to be a parallel test bug.
Could you please test with serial build?
Comment 8 Jorge Manuel B. S. Vicetto (RETIRED) Gentoo Infrastructure gentoo-dev 2012-01-10 20:04:25 UTC
(In reply to comment #5)
> i've just renamed last 2.0.16 to my local overlay but i can't manage to emerge.
> I'm not familiar enough to understand how to fix the pb, but i can explain
> 
>  *   The source directory
> '/var/tmp/portage/dev-cpp/eigen-2.0.17/work/eigen-eigen-2.0.17' doesn't exist
> 
> The tarballs are directly provided by the mercurial soft at bitbucket. And
> recently (~nov 2011), they changed how this stuff works and the directory that
> the tarballs extracts has changed. We got some reports from BSD with similar
> problems too.
> It used to extract to, say, 'eigen-2.0.17/', and now extracts to
> 'eigen-eigen-b23437e61a07/' (where the last part is the hash to the mercurial
> version labelled as '2.0.17').
> 
> If someone know how to fix this..

The correct way to fix this is for upstream to provide a "sane" directory name. Using the vcs commit hash for the directory name on a release tarball introduces "uncertainty" and causes more work for downstream.
Binary distributions that have developers manually download a tarball and creating a binary archive on their box and that redistribute that to their users are not too worried, but any source distribution that uses the upstream tarball and their "build recipe" to build a package, will need to update their "build recipe" (an ebuild in Gentoo) to update the change of the "moving directory name".
So please, *pretty* please if you want to be a good upstream, provide stable URLs for releases and use as the directory name inside a tarball a good convention, such as ${PN}-${PV} with ${PN} being the package name and ${PV} being the package version.