| Summary: | sys-apps/dmtcp fails to build (with gold, but seems unrelated) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
| Component: | New packages | Assignee: | Development Tools Team <dev-tools> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Build log | ||
|
Description
Diego Elio Pettenò (RETIRED)
2011-05-17 09:34:35 UTC
Hi, if this ebuild is still having problems, there is a new version of DMTCP, 1.2.3, and it should be configured with only default options (unless you really know what you're doing). Perhaps we can be of assistance in creating an ebuild for it, but we aren't the most experienced ebuild writers. Regards, DMTCP Upstream Devs Hi! After upgrading a series of packages dmtcp doesn't work anymore so I've tried to reinstall the existing version in portage. [ebuild R ] sys-apps/dmtcp-1.2.1 USE="-debug -emacs -fast -mpi -trace" 0 kB Although in the past I could install this version now it fails with the following error: >>> Emerging (1 of 1) sys-apps/dmtcp-1.2.1 * dmtcp-1.2.1.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking dmtcp-1.2.1.tar.gz to /var/tmp/portage/sys-apps/dmtcp-1.2.1/work >>> Source unpacked in /var/tmp/portage/sys-apps/dmtcp-1.2.1/work >>> Preparing source in /var/tmp/portage/sys-apps/dmtcp-1.2.1/work/dmtcp-1.2.1 ... * Applying dmtcp-1.2.1-gcc46.patch ... [ ok ] * Running eautoreconf in '/var/tmp/portage/sys-apps/dmtcp-1.2.1/work/dmtcp-1.2.1' ... * Running aclocal ... * Running eautoreconf in '/var/tmp/portage/sys-apps/dmtcp-1.2.1/work/dmtcp-1.2.1/dmtcp' ... * Running aclocal ... [ ok ] * Running autoconf ... [ ok ] * Running elibtoolize in: dmtcp-1.2.1/dmtcp/ * Applying portage/2.2 patch ... * Running autoconf ... * Applying sed/1.5.6 patch ... * Applying as-needed/2.2.6 patch ... [ ok ] * Running autoheader ... [ ok ] * Running automake --add-missing --copy --foreign ... [ !! ] * Failed Running automake ! * * Include in your bugreport the contents of: * * /var/tmp/portage/sys-apps/dmtcp-1.2.1/temp/automake.out * ERROR: sys-apps/dmtcp-1.2.1 failed (prepare phase): * Failed Running automake ! * * Call stack: * ebuild.sh, line 85: Called src_prepare * environment, line 3000: Called eautoreconf * environment, line 799: Called multijob_child_init 'eautoreconf' * environment, line 2642: Called eautoreconf * environment, line 827: Called eautomake * environment, line 780: Called autotools_run_tool 'automake' '--add-missing' '--copy' '--foreign' * environment, line 593: Called die * The specific snippet of code: * die "Failed Running $1 !"; * * If you need support, post the output of `emerge --info '=sys-apps/dmtcp-1.2.1'`, * the complete build log and the output of `emerge -pqv '=sys-apps/dmtcp-1.2.1'`. /usr/lib64/portage/bin/isolated-functions.sh: line 214: wait: `Failed Running automake !': not a pid or valid job spec * The complete build log is located at '/var/tmp/portage/sys-apps/dmtcp-1.2.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/dmtcp-1.2.1/temp/environment'. * Working directory: '/var/tmp/portage/sys-apps/dmtcp-1.2.1/work/dmtcp-1.2.1/dmtcp' * S: '/var/tmp/portage/sys-apps/dmtcp-1.2.1/work/dmtcp-1.2.1' Because I think this is a one of a kind application in the portage tree (I'm not aware of a replacement for it) I consider this bug should be resolved asap. Due to the fact that the current version in portage is 1.2.1(released at 2011-03-12) and the current version on the sourceforge is 1.2.6(released at 2012-07-31) I would like to know if a new bug("version bump request") is needed. +*dmtcp-1.2.6 (07 Oct 2012) + + 07 Oct 2012; Pacho Ramos <pacho@gentoo.org> +dmtcp-1.2.6.ebuild: + Version bump as current version doesn't compile for a long time (#367687). + |