FEAP User Forum

FEAP => FEAPpv => Topic started by: M. Kurdi on December 28, 2014, 08:00:35 PM

Title: x11c compilation error
Post by: M. Kurdi on December 28, 2014, 08:00:35 PM
Hello,

I would like to install feappv on Mac Mavrick. The compilation fails and issues this error.

x11u.c:65:10: fatal error: 'X11/Xlib.h' file not found

The makefile.in has the statement for X11R6 uncommented as specified to Apple. I tested new installation of feap8_4 and everything works fine. However for feappv3_1 the program cannot find Xlib.h. I made copy of Xlib.h into the /ver31 directory to see if it finds Xlib.h but to no avail. Tried switching x11u.c code from feap8_4 to check if there is something corrupt but didn't work as well. Any idea what might be causing this error?

Thanks!
Title: Re: x11c compilation error
Post by: FEAP_Admin on December 28, 2014, 10:11:31 PM
perform a search on your computer to find Xlib.h and then properly set the location in the makefile.
Title: Re: x11c compilation error
Post by: FEAP_Admin on December 28, 2014, 10:12:40 PM
Optionally you could try using the experimental CMAKE setup that comes with the FEAPpv zipfile.  It should be able to locate all the libraries etc for you.
Title: Re: x11c compilation error
Post by: M. Kurdi on December 29, 2014, 10:36:23 AM
The file exists in /usr/X11R6/Include/X11/Xlib.h. I verified this. Additionally the makefile.in is included in the correct directory (/usr/X11R6/include). The problem is that for some reason it is unable to process this file. Even when commenting the include <X11/Xlib.h> statement in the x11.c file, the error moved to the following include file. Could it a read permission or that sort?
Title: Re: x11c compilation error
Post by: FEAP_Admin on December 29, 2014, 01:07:46 PM
I can think of no reason that FEAP8.4 finds the files and compiles and FEAPpv will not.  The are using the exact same compilation setup and the exact same system routines.
Title: Re: x11c compilation error
Post by: jmsancho on February 04, 2015, 12:45:22 AM
I confirm the same  compilation error.

To solve simply add -I$(CINCLUDE) in the c compile rule in the makefile for unix directory.

Otherwise CINCLUDE remains unused.