On Thu, 20 Mar 2014 10:10:26 -0500
rhubarbpie...@gmail.com wrote:

> 
> On 03/20/14 09:00, Andrew Warshall wrote:
> > On Thu, 20 Mar 2014 08:03:26 -0500
> > rhubarbpie...@gmail.com wrote:
> >
> >> On 03/19/14 16:40, Armin K. wrote:
> >>> On 03/19/2014 10:20 PM, rhubarbpie...@gmail.com wrote:
> >>>> I receive "rmdir: failed to remove
> >>>> '/usr/include/freetype2/freetype/config': No such file or
> >>>> directory" when compiling freetype.
> >>>>
> >>>> I have /usr/include/freetype2/config but not
> >>>> /usr/include/freetype2/freetype/config.  I assume I've something
> >>>> wrong (which isn't much of a stretch), but I've removed my
> >>>> commands and don't see it.  Thoughts?
> >>>>
> >>> Ignore that. It's just there to make sure there aren't any
> >>> leftovers of old freetype headers which were installed in that
> >>> location.
> >>>
> >> Darn, I was hoping that was a problem.  What about:
> >>
> >> "rmdir: failed to remove '/usr/include/freetype2/freetype': No such
> >> file or
> >> directory /sources/freetype-2.5.2/builds/unix/install.mk:32:
> >> recipe for target 'install' failed"
> >>
> >> I ask this as I built xorg seemingly without problems but noticed
> >> xclock didn't work.  I traced the problem back to libXft, which I
> >> traced back to freetype.
> >>
> >>   From my libXft compilation:
> >>
> >> "xftglyphs.c:24:30: fatal error: freetype/ftoutln.h: No such file
> >> or directory"
> >>
> >> I see no error referenced to ftoutln in my freetype log.
> >>
> >>    
> >>
> >>
> > Do you have ftoutln.h anywhere? On my system, it's
> > freetype2/ftoutln.h. Do you have that?
> > (i.e. /usr/include/freetype2/ftoutln.h)
> >
> >                  -Andrew Warshall
> Yes, I have /usr/include/freetyp2/ftoutln.h
> 
> 

Did you apply the required patch: 
http://www.linuxfromscratch.org/patches/blfs/svn/libXft-2.3.1-freetype_fix-1.patch
 ? 

       -Andrew Warshall
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to