FWIW, it seems to compile ok for me on Leopard (i.e., autodetect
--- MCA component installdirs:autodetect (m4 configuration macro)
checking for MCA component installdirs:autodetect compile mode... static
checking procfs.h usability... no
checking procfs.h presence... no
checking for procfs.h... no
checking for /proc/self/maps... no
checking if MCA component installdirs:autodetect can compile... no
However, I see that autodetect configure.m4 is checking
$backtrace_installdirs_happy -- which seems like a no-no. The
ordering of framework / component configure.m4 scripts is not
guaranteed, so it's not a good idea to check the output of another
On Jul 21, 2009, at 6:45 PM, Iain Bason wrote:
> On Jul 21, 2009, at 6:31 PM, Ralph Castain wrote:
> > This commit appears to have broken the build system for Mac OSX.
> > Could you please fix it - since it only supports Solaris and Linux,
> > how about setting it so it continues to work in other environments??
> That was the intent of the configure.m4 script in that directory. It
> is supposed to check for the existence of some files in /proc, which
> should not exist on a Mac. Could you send me the relevant portion of
> the config.log on Mac OSX?
> devel mailing list