Sorry about the large delay in responding to your bug report. I
have been busy.
A Mennucc <[EMAIL PROTECTED]> writes:
> I was trying to use AC_PATH_XTRA , and found a bug.
> According to the info ,
> vvvvvvvvvvvvv
> - Macro: AC_PATH_XTRA ([LIBRARY = `Xt'], [HEADER-FILE =
> `X11/Intrinsic.h'], [FUNCTION-CALL = `XtMalloc (0)'])
> An enhanced version of `AC_PATH_X'. It adds the C compiler flags
> that X needs to output variable `X_CFLAGS', and the X linker flags
> to `X_LIBS'. Define `X_DISPLAY_MISSING' if X is not available.
>
> This macro checks that FUNCTION-CALL compiles when HEADER is
> included and that the resulting executable links against LIBRARY.
> The ability to specify these explicitly is an experimental,
> Debian-specific feature. The defaults reflect what other versions
> of Autoconf always check.
> ^^^^^^^^^^^^^^
>
> The above is wrong.
The documentation is maintained in the autoconf-doc package in
non-free by Henrique de Moraes Holschuh <[EMAIL PROTECTED]>. If you
are really reporting a documentation bug (I am not sure about
this) then you should report it against autoconf-doc. A related
bug is already filed as #298504.
> The bug is caused by the macro _AC_PATH_X_XMKMF (
> /usr/share/autoconf/autoconf/libs.m4 , in line 191).
>
> Here is what happens in that macro: 'xmkmf' creates Imakefile; then
> using the values in found in 'Imakefile', the macro sets
> 'ac_im_incroot="${INCROOT}"; ac_im_usrlibdir="${USRLIBDIR}' ; then, the
> macro checks if $ac_im_incroot/X11/Xos.h exists, and in that case it
> sets ac_x_includes=$ac_im_incroot ; similarly it checks if $ac_im_usrlibdir
> falls into "/usr/lib | /lib" and in that case it sets
> 'ac_x_libraries=$ac_im_usrlibdir' .
>
> Summarizing, currently in Debian, the macro AC_PATH_XTRA just checks
> if /usr/include/X11/Xos.h exists , and in that case it sets both
> ac_x_includes and ac_x_libraries. All other tests that follow are
> then skipped.
>
> To witness the above, unpack the attachment; the file
> 'x-test/configure-debug' is almost identical to the 'configure', but for
> 8 additional 'echo DEBUG ....' statements ( you should
> $ diff -u configure configure-debug
> ). When you run './configure-debug' you will see that most DEBUG are not
> printed, and you will see where the bug triggers
>
> a.
This is a good analysis of what is happening, but I don't see a
statement of what the bug is. I think that you may be saying
that it is a bug that AC_PATH_XTRA does not try to compile and
link when it finds that /usr/include/X11/Xos.h exists. Is that
the bug that you are reporting?
> ps: X11/Intrinsic.h is never ever checked anywhere :
> $ grep Intrinsic.h -r /usr/share/a* x-test/
> does not report anything
The documentation is wrong. Here is what the relevant changelog
entry says:
* AC_PATH_X now checks for X11/Xlib.h and XrmInitialize (X proper)
rather than X11/Intrinsic.h and XtMalloc (Xt). Thanks to Kurt Roeckx,
Thomas Dickey, and Paul Eggert. Closes: #327655.
--
"Long noun chains don't automatically imply security."
--Bruce Schneier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
