Error installing xpdf with openmotif
Ryan Schmidt
ryandesign at macports.org
Thu Dec 25 19:05:54 PST 2008
On Dec 25, 2008, at 18:16, Jeremy Huddleston wrote:
> On Dec 25, 2008, at 14:47, Ryan Schmidt wrote:
>
>> On Dec 25, 2008, at 16:24, Ryan Schmidt wrote:
>>
>>> On Dec 21, 2008, at 03:19, spam.spam.spam.spam at free.fr 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_x1
>>>> 1_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...
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. 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}?
More information about the macports-users
mailing list