Re: to build xdiv
Re: to build xdiv
- Subject: Re: to build xdiv
- From: Jeremy Huddleston <email@hidden>
- Date: Wed, 22 Feb 2012 19:45:51 -0800
On Feb 21, 2012, at 9:43 AM, Martin Costabel <email@hidden> wrote:
> On 19/02/12 18:16, James K. Lowden wrote:
> []
>>> 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:
>
> In your original message, you showed
>
>> checking for executable suffix... rm: conftest.dSYM: is a directory
>> .dSYM
> []
>> $ tail config.log
>> configure:1252: gcc -o conftest.dSYM -g -O2 conftest.c -lXt 1>&5
>
> This is what I meant; it believed ".dSYM" was the executable suffix.
> This does no longer happen with configure scripts created with current auto tools.
This also doesn't happen with configure scripts generated with old autoconf (including ones that used to ship with Xcode). The problem is that the configure script in xdvi is generated with *ancient* autoconf (2.13) which was released 16 years ago, before OS X was even released.
>
>> 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.
>
> I looked at the build process of xdvi as xdvik inside the texlive distribution. There the configure scripts are automatically generated from configure.ac by running whichever "autoconf" shows up in the PATH.
Which is probably where the problem lies since autoconf-2.1x is not compatible with >=autoconf-2.50
>>>> 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.
>
> Yes. If the configure.ac file contains a line
> AC_PATH_XTRA
> or something similar, then autoconf will put code into configure that looks for xmkmf in order to find the X11 libraries. If it doesn't find xmkmf, it falls back to some other mechanism which, in general, does not work.
> That's just how these things are currently (not) working. It is annoying, but it is not going to be fixed, because the people responsible for it don't believe that there is a problem.
File a bug with xdvi to update their build system.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden