Error upgrading xrender on Panther

Mon Dec 15 12:52:40 PST 2008

Uh... eh...  my bad.

I "fixed" this last week in r43377 but I forgot to svn add the files  
dir... so you should be able to get it now with r43828

On Dec 15, 2008, at 11:19, Frank J. R. Hanstick wrote:

> Hello,
> 	i am get the following error many times (4) when trying to execute  
> "sudo port upgrade installed":
>
> --->  Building xrender
> 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_xrender/work/libXrender-0.9.4" &&  
> make all " returned error 2
> Command output: make  all-recursive
> Making all in src
> /bin/sh ../libtool --tag=CC   --mode=compile /usr/bin/gcc-4.0 - 
> DHAVE_CONFIG_H -I. -I..   -I/opt/local/include -I/opt/local/include - 
> I/opt/local/var/macports/sources/rsync.macports.org/release/ports/ 
> x11/xrender/files/include -I/opt/local/include   -I/usr/X11R6/ 
> include -DXTHREADS -I.. -I../include/X11/extensions  -O2 -MT  
> Picture.lo -MD -MP -MF .deps/Picture.Tpo -c -o Picture.lo Picture.c
> /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I.. -I/opt/local/include -I/ 
> opt/local/include -I/opt/local/var/macports/sources/ 
> rsync.macports.org/release/ports/x11/xrender/files/include -I/opt/ 
> local/include -I/usr/X11R6/include -DXTHREADS -I.. -I../include/X11/ 
> extensions -O2 -MT Picture.lo -MD -MP -MF .deps/Picture.Tpo -c  
> Picture.c  -fno-common -DPIC -o .libs/Picture.o
> Picture.c:29:25: error: X11/Xregion.h: No such file or directory
> Picture.c: In function 'XRenderSetPictureClipRegion':
> Picture.c:177: error: 'BOX' undeclared (first use in this function)
> Picture.c:177: error: (Each undeclared identifier is reported only  
> once
> Picture.c:177: error: for each function it appears in.)
> Picture.c:177: error: 'pb' undeclared (first use in this function)
> Picture.c:182: error: dereferencing pointer to incomplete type
> Picture.c:184: error: dereferencing pointer to incomplete type
> Picture.c:184: error: dereferencing pointer to incomplete type
> Picture.c:191: error: dereferencing pointer to incomplete type
> Picture.c:193: error: dereferencing pointer to incomplete type
> make[2]: *** [Picture.lo] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
> Error: Unable to upgrade port: 1
>
> There is no /opt/local/lib/libX11/dylib on my system; but, Apple's  
> X11R6 is installed in /usr.  The file Xrender.h is in /opt/local/ 
> include/extensions.  I notice in the -I path designation for the  
> extensions is -I../include/extensions instead of /opt/local/include/ 
> extensions.  This is different from the other -I designations where / 
> opt/local precedes the directory.  This could be a problem if the  
> working directory is not ../ relative away from the include/ 
> extensions directory.
> Frank
>
> On Dec 15, 2008, at 12:12 AM, Jeremy Huddleston wrote:
>
>> The actual issue of that ticket is resolved meaning things are no  
>> more broken with xrender now than they were before (which means,  
>> they're still not too great).  If you sync, you should be able to  
>> install xrender without pulling in xorg-libX11 (assuming you can  
>> satisfy the lib:libX11.6 dependency some other way).
>>
>> The problem lies in some sort of conflict when both /usr/X11R6/lib/ 
>> libX11.dylib and /opt/local/lib/libX11/dylib are linked to by your  
>> executable... so... yeah... my short term solution to offer you is  
>> either
>>
>> 1) use all macports for your X11 dependencies (maybe setting  
>> x11prefix to /opt/local in macports.conf will be enough... you  
>> should probably then install xorg-libX11 so you don't accidently  
>> pull in XFree86)
>>
>> or
>>
>> 2) use none of the xorg-* ports in macports
>>
>> Sorry I can't offer you a better solution right now.
>>
>> On Dec 14, 2008, at 23:06, David Epstein wrote:
>>
>>>
>>>
>>> Jeremy Huddleston-5 wrote:
>>>>
>>>> Can you please see:
>>>> http://trac.macports.org/ticket/17429#comment:
>>>> I think if you pull in xorg-libX11 first, it'll be fine, but I need
>>>> someone to test that first...
>>>>
>>>
>>> I just tried sudo port upgrade installed (I should have said  
>>> outdated
>>> instead of installed, but nothing seemed to go wrong) and I hit  
>>> this xrender
>>> problem. I looked at the conversation over the ticket, but didn't  
>>> understand
>>> much of it. Also, I was surprised to find that the bug report was  
>>> closed,
>>> because that would indicate to me that the problems with porting  
>>> xrender
>>> have been removed. But I am continuing to get exactly the same  
>>> errors as
>>> those originally reported. How should one interpret a "bug closed"  
>>> message?
>>>
>>> I run Mac Os X 10.4.11, so I should have changed the name of the  
>>> thread from
>>> Panther to Tiger, but I didn't know how to do that.
>>>
>>> Could someone post advice on how to proceed, directed at  
>>> uneducated users?
>>> Thanks very much. I would have tried installing xorg-libX11,  
>>> except that
>>> Jeremy says, in the email I quote, that the solution is untested,  
>>> and,
>>> furthermore, the discussion on the ticket seems a little equivocal.
>>> Furthermore, I saw the comment in that discussion that installing
>>> xorg-libX11 brings in a lot of other stuff, so I don't want to do  
>>> it, unless
>>> it's necessary.
>>> -- 
>>> View this message in context: http://www.nabble.com/Error-upgrading-xrender-on-Panther-tp20758046p21009181.html
>>> Sent from the MacPorts - Users mailing list archive at Nabble.com.
>>>
>>> _______________________________________________
>>> macports-users mailing list
>>> macports-users at lists.macosforge.org
>>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>>
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>