autoconf's AC_PATH_X(TRA) doesn't set x_includes/X_CFLAGS

[braden@…]

Per the autoconf documentation, AC_PATH_X should set the shell variable x_includes if any such directory is not known about by the compiler by default; similarly, AC_PATH_XTRA should set the substitution X_CFLAGS. It seems that, indeed, gcc does not know about /usr/X11R6/include; however, x_includes does not get set when running configure.

[blb@…]

Is this against the autoconf port? And is there an easy way to reproduce the issue?

[braden@…]

Using AC_PATH_X in configure.ac causes the option --with-x to be added to configure. I filed this bug because providing --with-x to configure was not sufficient to find and use X. Reproducing this bug is as simple as writing a configure.ac that invokes AC_PATH_X (or find an existing one that does), running it with --with-x, and seeing if it actually finds X.

When I filed this, I'm pretty sure I was using the autoconf port with Apple's X11 on Mac OS X 10.4. There's an argument to be made that this should only be expected to work if MacPorts X11 is installed. I don't think I've tested that; but if it works, I think this can be closed.

(Incidentally, note that one can provide --x-includes and --x-libraries arguments to point to Apple's X11, and that does work as expected.)

[(none)]

Milestone Port Bugs deleted

[tobypeterson]

Is this still an issue with autoconf 2.64? In any case, this is really something that should be reported upstream.