On Thu, 15 Oct 2020 at 15:04, Zack Weinberg wrote:
> The thing that comes immediately to mind, and which would be feasible
> for 2.70, is to not run _AC_PATH_X_DIRECT when cross-compiling.
That seems realistic to me. The hardcoded paths are not useful in a
cross environment in the slightest.
>
On Thu, Oct 15, 2020 at 9:39 AM Ross Burton wrote:
>
> AC_PATH_X and friends are unusual in autoconf in that they
> *explicitly* look into /usr/ for files (see _AC_PATH_X_DIRECT).
> Notable this is the *only* macro in autoconf that explicitly looks
> into /usr.
>
> To w
Hi,
AC_PATH_X and friends are unusual in autoconf in that they
*explicitly* look into /usr/ for files (see _AC_PATH_X_DIRECT).
Notable this is the *only* macro in autoconf that explicitly looks
into /usr.
To write the logic out in English: iterate through a long list of
paths in /usr for a X11
David Roguin <[EMAIL PROTECTED]> writes:
> here's what configure says about X
> ...
> checking for X... libraries , headers
> ...
>
> Does anybody know what may be the problem?
There is nothing wrong with that line. It just means that both headers
and libraries are in the standard locations.
An
Hi,
I'm making a project an I need to know the presence of the X system.
I'm using the AC_PATH_X macro to do that, but it fails in finding
anything.
I'm using debian lenny/sid amd64 distro
here's what configure says about X
...
checking for X... libraries , headers
...
Do
Does AC_PATH_X work with version 2.53?
My configure output is:
checking for X... libraries /usr/X11r6/lib, headers /usr/X11R6/include
Which makes me believe configure found the X11 libraries, but when I try
to link, I get hundreds of undefined references to X11 functions.
Any help would be
On a Linux-2.4 machine using the following
AC_PATH_X
AC_LANG_PUSH(C)
AC_CHECK_LIB(Xmu, XmuLookupStandardColormap,,, -lXt -lX11)
AC_CHECK_LIB(X11, XCreateWindow)
AC_LANG_POP(C)
I get
checking for X... libraries /usr/X11/lib, headers
checking for XmuLookupStandardColormap in -lXmu
