Paul Onions wrote:
>
> > On 24 Jan 2016, at 14:26, Waldek Hebisch <[email protected]> wrote:
> >
> > Paul Onions wrote:
> >>
> >> In case anyone is interested I thought I'd post my experience of building
> >> FriCAS on OSX. For reference this is FriCAS 1.2.7 on OSX 10.11.2 (El
> >> Capitan). To do this I needed the Xcode command line tools [1] and the
> >> XQuartz package [2] to be installed. Then I could build FriCAS from
> >> source using the following configure invocation:-
> >>
> >> ./configure --x-includes=/usr/X11/include
> >>
> >> I'm not sure why I need to specify the x-includes directory, it would be
> >> nice if it was autodetected I had a look at the build machinery but
> >> quickly got lost :-(
> >
> > Thanks for info. Detection of X11 is done by autoconf macros.
> > There was a typo in FriCAS 'configure.ac' which could affect this.
> > I have commited corrected version to trunk, but I an not sure
> > if it makes difference. It seems that changes in El Capitan
> > caused troubles not only for FriCAS but for many free programs.
>
> Hi Waldek,
>
> Thanks for looking into this, unfortunately the change made no difference.
> Though I have discovered something interesting I think. The build errors out
> with:
>
> ---
> /Users/pdo/Projects/FriCAS/build/config ../../../fricas/src/lib/pixmap.c -o
> pixmap.o
> ../../../fricas/src/lib/pixmap.c:38:10: fatal error: 'X11/Xos.h' file not
> found
> #include <X11/Xos.h>
> ^
> 1 error generated.
> make[2]: *** [pixmap.o] Error 1
> make[1]: *** [all-lib] Error 2
> make: *** [all-src] Error 2
> ---
>
> but looking in Xos.h I see the following includes:-
You mean in pixmap.c?
> ---
> #include <X11/Xlib.h>
> #include <X11/Xutil.h>
> #include <X11/Xos.h>
> ---
>
> which seems to imply that it found Xlib.h and Xutil.h okay.
Yes. However, this only suggests that Xlib.h and Xutil.h can
be found in some other place.
> Then looking inside the configure script I see some special code mentioning
> X11/Xos.h, but to be honest that's as far as I've got as I'm not too familiar
> with the build process. I'm hoping this might give you some clue as to what
> is really happening.
This part in configure is essentially copied from autoconf. More
precisely, this is expansion of autoconf macro AC_PATH_XTRA.
So we are debugging autoconf now...
AFAIKS the first step consists of running xmkmf program,
which is part of standard X11 installation and is supposed
to know where X headers and X libraries live. In detail,
first we create file called Imakefile with content below:
--------------<Imakefile start, cut here>---------------
incroot:
@echo incroot=${INCROOT}
usrlibdir:
@echo usrlibdir=${USRLIBDIR}
libdir:
@echo libdir=${LIBDIR}
--------------<Imakefile end, cut here>---------------
(note that like in a Makefile there are tabs at start
of indented lines). Running xmkmf is supposed to
produce Makefile which after running make prints
values of variables. The autoconf macro uses sed
to extract values of variables. So something during
this went wrong...
--
Waldek Hebisch
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/fricas-devel.
For more options, visit https://groups.google.com/d/optout.
