Skip Menu |

This queue is for tickets about the Prima CPAN distribution.

Report information
The Basics
Id: 18045
Status: resolved
Priority: 0/
Queue: Prima

People
Owner: Nobody in particular
Requestors: Tom.Schoonjans [...] Ugent.be
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Makefile.PL issue
Hi, When installing the Prima module I get the following error: Prima needs X11 headers for compilation! Set X11BASE='/path/to/X' if you have a non-standard path to X. (see also makefile.log for details) I checked the path to X on my system and it's /usr/X11R6 Setting X11BASE to this path didn't solve the problem. I've examined your Makefile.PL and it seems it needs files included in /usr/X11R6/include This directory exists on my system, but it contains no files. Maybe this is (part) of the problem? I use Perl v5.8.6 on a Fedora Core 4 system Any help would be appreciated :-) Kind regards
Show quoted text
> > Prima needs X11 headers for compilation! Set X11BASE='/path/to/X' if you > have a non-standard path to X. (see also makefile.log for details) >
Make sure that you have X header files (Xlib.h etc) in your X include directory. If these are present, look in makefile.log, there's a chance that the error might be not related to X , but to something else. Checking out makefile.log ( and posting it's content for the bug report ) is usually the best thing to do.
I solved the issue when upgrading my X. More specifically: I installed x-org-x11-tools.386 and imlib-devel.i386 with yum. Thanks for the support Kind regards Tom Schoonjans On Di. maa. 07 17:11:18 2006, KARASIK wrote: Show quoted text
> > > > Prima needs X11 headers for compilation! Set X11BASE='/path/to/X' if you > > have a non-standard path to X. (see also makefile.log for details) > >
> > Make sure that you have X header files (Xlib.h etc) in your X include > directory. If these are present, look in makefile.log, there's a chance > that the error might be not related to X , but to something else. > Checking out makefile.log ( and posting it's content for the bug report > ) is usually the best thing to do.