On Tue, 25 Sep 2012, Tim Jenness wrote:
> On Tue, Sep 25, 2012 at 9:48 AM, Peter W. Draper
> <[log in to unmask]> wrote:
>> On Mon, 24 Sep 2012, Tim Jenness wrote:
>>
>>> I can't get GAIA to build on mountain lion because the compiler can't
>>> find the X11 include files in /usr/X11/include. AC_PATH_X is used but the
>>> output from that search never makes its way into CFLAGS so the compiler
>>> never knows where to find X11.
>>>
>>> We had this fixed for most of Starlink with 8671b224a79 but I'm not really
>>> sure where to put $X_CFLAGS in the GAIA build since it doesn't really use
>>> automake (Linux and Lion have a soft link for X11 in /usr/include which is
>>> why it always used to work but Mountain Lion no longer puts it in
>>> /usr/include and is about to move it out of /usr completely to /opt/X11 but
>>> that's a different patch).
>>
>>
>>> Is XINCLUDES the equivalent of X_CFLAGS?
>>
>>
>> Probably, but it looks like that is always set by the tcl.m4 macros so
>> that may not actually work.
>>
>
> but as far as I can tell the AC_PATH_X macros in the GAIA build aren't
> doing anything useful since no-one actually uses the variables set by
> those macros.
>
>> If I where you I'd go to the Tk source and change tcl.m4 so that these
>> two directories are included in the search path for X includes. You'd
>> then need to regenerate the configure scripts and rebuild Tk.
>> Re-configuring Skycat and GAIA should then make use of this.
>>
>
> So in order for GAIA to know where the X include path is I need to hack
> Tcl/Tk?
Yes. Skycat and GAIA use the Tcl/Tk macros for X11 configuration.
At least that seems to work after all.
Cheers,
Peter.
|