Re: to build xdiv
Re: to build xdiv
- Subject: Re: to build xdiv
- From: Jeremy Huddleston <email@hidden>
- Date: Sun, 19 Feb 2012 10:49:34 -0800
Did you try my suggestion? Please just use their configure script with the following:
./configure --x-include=/usr/X11/include --x-lib=/usr/X11/lib
You're in for a world of hurt if you want to try updating older configure scripts.
On Feb 19, 2012, at 09:16, James K. Lowden wrote:
> On Sun, 19 Feb 2012 02:35:29 +0100
> Martin Costabel <email@hidden> wrote:
>
>>>>> It's sad that they're not using pkg-config ...
>>>>
>>>> They are using xmkmf, which is still the standard tool used by gnu
>>>> autotools for detecting the path to X libraries.
>>>
>>> The standard tool for finding X11 using autotools has been
>>> pkg-config since around 2004. It has been almost a decade since we
>>> gave xmkmf the boot.
>>
>> If you create a configure script with current autoconf, it uses (or
>> tries to use) xmkmf to find the X library directory.
>
> I was not able to generate a configure script from the xdiv
> distribution using autoconf 2.61 and automake 1.10. The configure.in
> was too old, lacking/misusing macros that current autotools need.
>
> I began updating it, renaming configure.in to configure.ac, fixing m4
> quoting issues, and so on. I arrived at a point where I generate a
> configure script that ends with
>
> checking for waitpid... yes
> ../configure: line 10559: syntax error: unexpected end of file
>
> I sent a detailed message to the autoconf mailing list; we'll see what
> they say.
>
>> The issue that started this thread, namely that configure is lead to
>> think that executables have a *.dsym suffix. Newer versions of
>> autoconf know about dsym, the 6 year old one that Apple ships
>> doesn't.
>
> That's not the case. Please see
> http://www.schemamania.org/xdvi-22.85/build/config.log.
>
> configure:2764: checking for suffix of executables
> configure:2771: gcc -o conftest conftest.c >&5
> configure:2774: $? = 0
> configure:2798: result:
>
> The configure script that comes with the distribution tarball did
> seem confused about the executable extension. It might have been
> generated by an older autoconf.
>
>>> The standard tool for finding X11 using autotools has been
>>> pkg-config since around 2004. It has been almost a decade since we
>>> gave xmkmf the boot.
>>
>> If you create a configure script with current autoconf, it uses (or
>> tries to use) xmkmf to find the X library directory.
>
> That is true; I see references to xmkmf in the configure script I
> generated. Because the xdiv configure.in doesn't mention xmkmf, though,
> I have to think autoconf has some built-in functionality to reference
> xmkmf.
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> X11-users mailing list (email@hidden)
>
> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden