Error installing xpdf with openmotif

[Jeremy Huddleston]

On Dec 25, 2008, at 19:05, Ryan Schmidt wrote:

>>>>> --->  Building openmotif
>>>>> Error: Target org.macports.build returned: shell command " cd
>>>>> "/opt/local/var/macports/build/ 
>>>>> _opt_local_var_macports_sources_rsync 
>>>>> .macports.org_release_ports_x11_openmotif/work/openmotif-2.3.1"
>>>>> && make all " returned error 2
>>>>> Command output: /usr/X11R6/include/X11/Xft/Xft.h:191: error:  
>>>>> parse error before
>>>>> '*' token
>>>>> /usr/X11R6/include/X11/Xft/Xft.h:257: warning: type defaults to  
>>>>> 'int' in
>>>>> declaration of 'XftGlyphSpec'
>>>>> /usr/X11R6/include/X11/Xft/Xft.h:257: error: parse error before  
>>>>> '*' token
>>>>
>>>> [snip]
>>>>
>>>> Looks like this ticket:
>>>>
>>>> http://trac.macports.org/ticket/17631
>>>
>>> ...although that ticket seems to be for Leopard and you're on  
>>> Tiger. I'm on Tiger too and it builds for me. Could you "sudo port  
>>> selfupdate" to make sure everything's up to date, then "sudo port  
>>> clean openmotif" and "sudo port -d install openmotif 2>&1 | tee ~/ 
>>> Desktop/openmotif.txt" to generate a complete log? If it fails  
>>> again, compress the log with "bzip2 ~/Desktop/openmotif.txt" then  
>>> attach openmotif.txt.bz2 from your desktop to your reply and I'll  
>>> compare it with the output I got from building on my system.
>>
>> I wonder if /usr/X11R6/include/X11/Xft/Xft.h is seeing headers from  
>> macports' freetype instead of X11SDK freetype and getting  
>> flustered...
>
> We want freetype in ${prefix} to be used instead of freetype in $ 
> {x11prefix}, as per our standing policy, because MacPorts freetype  
> is newer...

Right, I understand that.  I was drawing the line for "from macports"  
at png, pixman, cairo, freetype, and fontconfig.  Everything in /usr/ 
X11 from x.org was being used if it is compatible.

> If Xft2 in ${x11prefix} gets confused by using freetype in ${prefix}  
> then we should be using Xft2 in ${prefix}, which I would think we  
> should be doing anyway because it's newer too.

Well then where do you draw the line?  Should we start forcing libX11  
in macports because it's newer?  I'd be all for forcing Macports X11  
libs over system X11 libs, since it would throw all of these issues  
(.la-fu, dependencies pulling in conflicting libX11s (#17558), header- 
mixup-fu, ...) out the window!

We could still add a +system_x11 variant to all of the X11 lib  
packages which would cause them to just be stubs, so people could  
continue to use their system X11 by enabling that variant...

> But in r43207 you changed the port, Jeremy, from requiring the  
> MacPorts Xft2 to accepting an Xft2 in ${x11prefix}. I do have the  
> Xft2 port installed. Do you, "spam.spam.spam.spam", or are you using  
> Xft2 in ${x11prefix}?

Everything that I changed from using port:Xft2 to lib:libXft:Xft2  
(including openmotif), I tested with no Xft2 port installed on both  
Tiger and Leopard.

Unfortunately, I don't have my Tiger box with me over holiday, so I  
can't be much help with this right now, but I'll be able to diagnose  
it further next week.