Re: configure error: "Can't find X11 headers and libs"
Re: configure error: "Can't find X11 headers and libs"
- Subject: Re: configure error: "Can't find X11 headers and libs"
- From: "Tom Scogland" <email@hidden>
- Date: Mon, 7 Jul 2008 15:04:43 -0500
This is not really my area, but was just working on some autoconf
scripts, and came across this in the manual
"— Macro: AC_PATH_X
Try to locate the X Window System include files and libraries. If
the user gave the command line options --x-includes=dir and
--x-libraries=dir, use those directories.
If either or both were not given, get the missing values by
running xmkmf (or an executable pointed to by the XMKMF environment
variable) on a trivial Imakefile and examining the makefile that it
produces. Setting XMKMF to `false' disables this method.
If this method fails to find the X Window System, configure looks
for the files in several directories where they often reside. If
either method is successful, set the shell variables x_includes and
x_libraries to their locations, unless they are in directories the
compiler searches by default.
If both methods fail, or the user gave the command line option
--without-x, set the shell variable no_x to `yes'; otherwise set it to
the empty string. "
Thereby, if xmkmf is not present, but the files are either in, or
symlinked to, a standardish directory, it should all work when using
the builtin macros meant for the job. I took the extra 30 seconds to
test it, it works fine on leopard with XQuartz 2.2.3...
if the problem is some package not using the macros from autoconf, or
using a depressingly old autoconf version, this seems like a problem
you should bring up with the package maintainer rather than this list.
For that matter, Mr Costabel, given that the above options would work
given where autoconf is finding my libraries, do you even have the X11
sdk installed?
-Tom
On Mon, Jul 7, 2008 at 2:42 PM, Martin Costabel <email@hidden> wrote:
> Jeremy Huddleston wrote:
>>
>> On Jul 7, 2008, at 04:55, Martin Costabel wrote:
>>
>>> With the current versions of xquartz, you cannot build any auto-tools
>>> based software by simply running ./configure; make; make install.
>>> You will always get
>>
>> That's not true. You can most certainly build auto-tools based software!
>> The entire x.org repository USES auto-tools, and we use auto-tools to build
>> all the X11 applications that we ship. The problem is when they try to use
>> xmkmf and imake. xmkmf and imake are horrifically broken and not supported.
>> If you package uses xmkmf or imake, I highly suggest you switch over to
>> using pkg-config.
>
> You are addressing the wrong public here. It is of course possible to
> hand-craft auto-tools to do anything you want. The fact is, however, that
> until now the standard way to detect an X11 installation uses xmkmf, and
> fails if xmkmf is not present.
>
> This means that mere users - not package creators - are left out in the cold
> if they want to do the usual configure; make; make install procedure for
> software that they can download *now*.
>
> Using configure flags is fine. But your answer and Piotr's answer show where
> the problem with this is: You have to spend time to find out how to do it.
> Gratuitous, unnecessary waste of time. You wrote
>
>> Try passing --with-x-include=/usr/X11/include --with-x-lib=/usr/X11/lib to
>> configure.
>
> Piotr wrote
>
>> CFLAGS="-I/usr/X11/inlude" LDFLAGS="-L/usr/X11/lib" ./configure
>
> Both of these *do not work*.
>
> --
> Martin
>
>
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> X11-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>
--
-N
AKA:Tom Scogland
I am enough of an artist to draw freely upon my imagination.
Imagination is more important than knowledge. Knowledge is limited.
Imagination encircles the world.
-Albert Einstein
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden