Richard Campbell wrote:
This is due to the way that the configure script for libiberty is called in configure.ac:


If I was paying attention, libiberty uses autoconf 2.13 or similar, and the other pieces use 2.5...That's going to be a real pain to set up, I think...

It's just our top-level configure being stupid and passing CFLAGS and LDFLAGS as options instead of as environment variables. I don't think it matters what version of autoconf libiberty is using (at least not for this problem).


Harold

Reply via email to