Bug 232331

Summary:	sys-cluster/mpich-1.2.7_p1 - configure.in:140: error: AC_SUBST: `$CC' is not a valid shell variable name
Product:	Gentoo Linux	Reporter:	Dwan <firstprinciple>
Component:	[OLD] Development	Assignee:	Michael Imhof (RETIRED) <tantive>
Status:	RESOLVED INVALID
Severity:	normal	CC:	cklarson, hp-cluster
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	226305
Attachments:	autoconf output build log emerge --info

Description Dwan 2008-07-19 14:04:48 UTC

* ERROR: sys-cluster/mpich-1.2.7_p1 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_unpack
 *             environment, line 2583:  Called eautoreconf
 *             environment, line  844:  Called eautoconf
 *             environment, line  787:  Called autotools_run_tool 'autoconf'
 *             environment, line  332:  Called die
 * The specific snippet of code:
 *           die "Failed Running $1 !";
 *  The die message:
 *   Failed Running autoconf !

Reproducible: Always

Steps to Reproduce:
1.emerge -av mpich
2.
3.

Actual Results:  
***** 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

Comment 1 Dwan 2008-07-19 14:10:39 UTC

Created attachment 160842 [details]
autoconf output

Comment 2 Dwan 2008-07-19 14:12:17 UTC

Created attachment 160844 [details]
build log

Comment 3 Jeroen Roovers (RETIRED) gentoo-dev

2008-07-19 14:22:39 UTC

Oh, and please do attach your `emerge --info' as well.

Comment 4 Dwan 2008-07-20 00:58:06 UTC

Created attachment 160888 [details]
emerge --info

Comment 5 Chris Larson 2008-09-15 19:58:54 UTC

I'm not authorized to chage the status, so I'll simply put this in a comment:

Pretty sure this is a duplicate of Bug 154438.

The suggested change to the ebuild mentioned there solved this problem for me.

Comment 6 Diego Elio Pettenò (RETIRED) gentoo-dev

2008-10-11 11:42:00 UTC

No it doesn't seem to be a duplicate; by the way forcing autoconf 2.13 here is not the solution since there _is_ a bug in that configure.in file.

Comment 7 BlackWhiteAtgentoo 2009-03-18 19:36:02 UTC

method provided by Bug 154438 does fix the problem.
You just use your autoconf and autoheader version provided by your system.

Comment 8 Justin Bronder (RETIRED) gentoo-dev

2009-06-13 20:47:12 UTC

sys-cluster/mpich is gone.