Re: pfaedit errors

Would you recommend me nuking my X11 and X11SDK and reinstalling them? 
Would you recommend me nuking DP and reinstalling it? Just so you know, 
I even popped my Panther cdroms into the machine and had it check and 
repair disk permissions and the disk itself (3 files had incorrect 
permissions (none of which looked applicable to what is going wrong 
here) and the drive showed as having an incorrect amount of files); 
nothing major, so it had no problem fixing the problem. Thanks for your 
help in this matter.
-Anthony

On Feb 26, 2004, at 9:21 PM, Bryan Blackburn wrote:

> Nothing I do to attempt to reproduce this error works (aka, all works
> fine here).  I've tried a new DP install, putting the tree on HFS+ 
> (since
> it's normally on UFS here), and no problems.  A few comments/questions
> below.
>
>
> On Feb 26, 2004 14:26 -0700, Anthony Agelastos exclaimed:
> > To summarize the problem so the message is not too long, I tried to
> > install pfaedit with DarwinPorts' freetype, and received an error.
> > Then, I was consulted that the freetype supplied from Apple is better
> > than the one from DP, so I cleaned and uninstalled freetype, and then
> > tried installing pfaedit and still get an error (which is below). I 
> > did
> > verify that the X11SDK is installed. My computer's information is as
> > follows:
> > Mac OS X 10.3.2 (7D24) (fully updated)
> > PowerBook G4 / 400 MHz / 640 MB RAM
> > Thanks again for everyone's assistance.
> >
> > -Anthony
> >
> > --->  Building pfaedit with target all
> > Error: Target com.apple.build returned: shell command "cd
> > "/Users/iqgrande/darwinports/dports/graphics/pfaedit/work/pfaedit
> > -040204" && make all" returned error 2
> > Command output: freetype.c:620: error: parse error before "slot"
> What's interesting here is that autoconf must have determined freetype
> is available, and that the compiler didn't encounter an error finding
> the headers, but items defined in the freetype headers end up being
> unknown.  One of two things I can think of are that somehow 
> FT_FREETYPE_H
> is being defined incorrectly, overriding the definition by freetype 
> itself,
> or something is seriously hosed with the freetype headers.
>
> Anyone have any thoughts on this?
>
> Bryan
>
>
> > freetype.c:621: error: `ftc' undeclared (first use in this function)
> > freetype.c:621: error: parse error before ')' token
> > freetype.c:634: error: `_FT_Set_Char_Size' used prior to declaration
> [...]
> > make[1]: *** [freetype.o] Error 1
> > make: *** [pfaedit] Error 2
> _______________________________________________
> Darwinports mailing list
> Darwinports@xxxxxxxxxxxxxx
> http://www.opendarwin.org/mailman/listinfo/darwinports