cross-compiling IOR

[roblatham00]

Issue: undefined references to 'rpl_malloc' when cross compiling

Cause: AC_FUNC_MALLOC is based on a run-time test

When cross-compiling, the run-time test cannot run, so autoconf assumes non-gnu-libc behavior

(I found this link helpful: http://wiki.buici.com/xwiki/bin/view/Programing+C+and+C%2B%2B/Autoconf+and+RPL_MALLOC )

Platform: Blue Gene /P (but probably /L and maybe /Q?)

mpicc  -g -O2   -o ior ior.o utilities.o parse_options.o aiori-POSIX.o aiori-MPIIO.o     -lm
ior.o: In function `HumanReadable':
../../src/ior.c:917: undefined reference to `rpl_malloc'
ior.o: In function `CreateTest':
../../src/ior.c:583: undefined reference to `rpl_malloc'
ior.o: In function `AllocResults':
../../src/ior.c:532: undefined reference to `rpl_malloc'
../../src/ior.c:536: undefined reference to `rpl_malloc'
../../src/ior.c:541: undefined reference to `rpl_malloc'

I can work around this with an environment variable but if you could toss a 'rpl_malloc' in IOR to keep cross compilers happy, that would be great.

[morrone]

It looks like removing AC_FUNC_MALLOC from configure.in would work as well. I don't think that I made a conscious decision to include AC_FUNC_MALLOC; it probably just was part of what autoscan produced when I started the configure.in file.

So I think I'll likely just back out that line as the quick solution. IOR should work as well as it always has without it.

You could try it out by removing that line, and then running "bootstrap" to regenerate the configure script.

FYI, I did not see this on BG/Q. Likely because the architectures are more similar on the compilation and compute nodes with Q.