[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Apache headers and other ones such as Xft



On Mon, 2003-11-10 at 23:51, Owen Taylor wrote:
> On Mon, 2003-11-10 at 16:31, Razvan Corneliu C.R. "d3vi1" VILT wrote:
> > On Mon, 2003-11-10 at 23:17, Razvan Corneliu C.R. "d3vi1" VILT wrote:
> > > While building a module for apache I've noticed the following problem
> > > Out of pages of errors the most important lines are:
> > > (...)
> > > /usr/include/httpd/ap_config.h:58:17: apr.h: No such file or directory
> > > (...)
> > > There are similar ones for other .h files in /usr/include/apr-0
> > > The work-around was to move all the file from /usr/include/apr-0 to
> > > /usr/include
> > > Someone rearanged the header files in apr but forgot to update the
> > > apache headers with the new location... ntz...ntz...ntz...
> > > 
> > I've noticed this problem for Xft but in redhat 9, I'm not sure if they
> > are still present in fedora core... Some X11 lib (namely
> > /usr/include/X11/Xft/Xft.h) wanted some Xft1 headers
> > (/usr/include/freetype/freetype.h) but in my case it wanted freetype 1
> > which was not there at the time... now apparently it works better due to
> > a link from freetype to freetype2
> 
> * Xft always has used freetype2
> 
> * In order to link to freetype2, you need to use freetype-config to
>   find the correct -I flags for freetype2
> 
> * 'pkg-config --cflags xft' will already include that -I directory,
> 
>   $ pkg-config --cflags xft
>   -I/usr/X11R6/include -I/usr/include/freetype2
> 
It was a bug which I've found on RHLinux9 while compiling gdkxft.
It's not here anymore...
It was only another example of header file stuff which I've been a
witness of...
Using the same sources (ver1.5) it works out of the box now on fedora
because of that link from /usr/include/freetype to
/usr/include/freetype2/freetype

Also while compiling nvidia kernel module source-code due to some other
weird stuff I had to make a link from
/usr/lib/gcc-lib/i386-redhat-linux/3.2.2 to
/usr/lib/gcc-lib/i386-redhat-linux/3.2.3. Don't really know where it
still thought that it was 3.2.2, forgot to report-it when I had the logs
in sight...

I assume that this is the right place to report problems caused by
header files... right???
> Regards,
> 						Owen
> 
> 
> 
> --
> fedora-devel-list mailing list
> fedora-devel-list redhat com
> http://www.redhat.com/mailman/listinfo/fedora-devel-list




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]