Summary: | sys-cluster/mpich-1.2.7_p1 fails to run autoheader | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michael Zeising <michael> |
Component: | [OLD] Library | Assignee: | Michael Imhof (RETIRED) <tantive> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | bugs, g.chulkov, hp-cluster, jka, marc.joanisse, mmokrejs |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Output of autoheader |
Description
Michael Zeising
2006-11-08 01:45:20 UTC
Created attachment 101433 [details]
Output of autoheader
*** Bug 154973 has been marked as a duplicate of this bug. *** I had similar issues with mpich-1.2.7_p1 not installing. I believe it has to do with an incompatibility with autoconf-2.61 (which is included in its depends). When I force it to ignore dependencies (emerge -uO mpich) it installs fine using autoconf 2.60 and at least upon light testing, mpicc and mpirun work fine. I get the following on ~x86:
>>> Unpacking mpich-1.2.7p1.tar.gz to /var/tmp/portage/sys-cluster/mpich-1.2.7_p1/work
* Applying 1.2.7_p1-fix-romio-sandbox-breakage.patch ... [ ok ]
/var/tmp/portage/sys-cluster/mpich-1.2.7_p1/work/mpich-1.2.7p1/romio /var/tmp/portage/sys-cluster/mpich-1.2.7_p1/work/mpich-1.2.7p1
* Running eautoreconf in '/var/tmp/portage/sys-cluster/mpich-1.2.7_p1/work/mpich-1.2.7p1/romio' ...
* Running autoconf ... [ ok ]
* Running autoheader ... [ ok ]
* Running elibtoolize in: mpich-1.2.7p1/mpe/slog2sdk/trace_sample
* Applying install-sh-1.5.patch ...
* Applying portage-1.5.10.patch ...
* Applying max_cmd_len-1.5.14.patch ...
* Applying sed-1.5.6.patch ...
* Running elibtoolize in: mpich-1.2.7p1/mpe/slog2sdk/trace_rlog
* Applying install-sh-1.5.patch ...
* Applying portage-1.5.10.patch ...
* Applying max_cmd_len-1.5.14.patch ...
* Applying sed-1.5.6.patch ...
* Running elibtoolize in: mpich-1.2.7p1/examples/perftest/config/confdb
* Applying install-sh-1.5.patch ...
* Applying portage-1.5.10.patch ...
* Applying max_cmd_len-1.5.20.patch ...
* Applying sed-1.5.6.patch ...
/var/tmp/portage/sys-cluster/mpich-1.2.7_p1/work/mpich-1.2.7p1
* Applying 1.2.7_p1-allow-fhs-afs.patch ... [ ok ]
/var/tmp/portage/sys-cluster/mpich-1.2.7_p1/work/mpich-1.2.7p1/mpid/server /var/tmp/portage/sys-cluster/mpich-1.2.7_p1/work/mpich-1.2.7p1
* Running eautoreconf in '/var/tmp/portage/sys-cluster/mpich-1.2.7_p1/work/mpich-1.2.7p1/mpid/server' ...
* Running autoconf ... [ !! ]
* Failed Running autoconf !
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/sys-cluster/mpich-1.2.7_p1/temp/autoconf-15925.out
...
***** autoconf *****
***** autoconf
configure.in:140: error: AC_SUBST: `$CC' is not a valid shell variable name
configure.in:140: the top level
autom4te-2.62: /usr/bin/m4 failed with exit status: 1
/var/tmp/portage/sys-cluster/mpich-1.2.7_p1/temp/autoconf-15925.out
I do not know much internals of ebuilds but the following did the trick for me. I edited mpich-1.2.7_p1.ebuild like below. Maybe you can someone force eautoreconf to execute specific version of autoconf? src_unpack() { unpack ${A} cd "${S}" grep -FrlZ '$(P) ' . | xargs -0 sed -i -e 's/\$(P)//' # Fix broken romio epatch "${FILESDIR}"/${PV}-fix-romio-sandbox-breakage.patch pushd "${S}"/romio rm configure eautoreconf popd epatch "${FILESDIR}"/${PV}-allow-fhs-afs.patch pushd "${S}"/mpid/server rm configure # do not run 2.62 autoconf but rather force expected old version # eautoreconf autoconf-2.13 autoheader-2.13 libtoolize popd } (In reply to comment #4) I had the same problem with this on a Lemote Fulong mips based machine. sys-cluster/mpich is gone. |