[Xquartz-dev] MacPorts - Howto

[Jeremy Huddleston]

I finally got to looking through your install log, and one hunch I had  
is now disproved (meaning I'm back to having no clue).  I changed to  
using -Os instead of -O2 sometime around 2.3.2_betaXX , but you're  
seeing this with -O2 as well in your MacPorts install.

Chris, what version of xorg-server are you "happy" with in that early  
2.3.2 beta you're using?  Try editing the MacPorts Portfile to install  
that version instead of the latest.  I forget what the default  
location is for MacPorts Portfiles... Just 'cd /opt/local/var/ 
macports/; find . -name xorg-server' and it'll pop up.  Assuming that  
one works, try stepping forward one version and verify that it  
breaks.  Then we'll try narrowing down from there.

On Feb 5, 2009, at 14:16, Christof Wolf wrote:

> On Thursday 05 February 2009, you wrote:
>> And for those not wanting to click links and read, here's something
>> you should be able to copy/paste:
>>
>> svn co https://svn.macosforge.org/repository/macports/trunk/base
>> cd base
>> ./configure && make && sudo make install
>
> Hi Jeremy,
> I did the link but it stopped because tcl was compiled with no  
> headers :-) so
> I installed the binary of macports - it went through smoothly, setup
> my .profile and updated
>
> $MacPorts base version 1.700 installed
> $Downloaded MacPorts base version 1.700
>
>>
>> Setup your /etc/profile or whatever to add /opt/local/bin to PATH
>> then... (ok, maybe you can't "copy/paste" this)
>> sudo port -v selfupdate
>> sudo port -v install xorg
>
> that took a long time - if you're curious - I have attached the  
> install
> log :-)
>
> and I tried X11 in macports - it says 2.3.2 xorg server 1.4.2- 
> apple32 -
>
> the first time the X11 just hung (sample attached) I killed it and  
> restarted
> it, interestingly the CPU would not go crazy - but I could not  
> activate any
> of the X11 apps, terminal, kmail, which I had openend, though the  
> "force app
> window" nor the "activity monitor" showed that X11 was "not  
> responding" I had
> to kill it. the third time it is back again to the "normal" abnormal
> behavior - as long I am in X11 its fine  - any other time the CPU  
> goes up to
> 100%.
>
> ciao
> christof
>
> -- 
> public key www.hfph.mwn.de/~chwolf/chwolf.asc
>
> Please respect my privacy and do not make my contact information
> available to third parties.
> <install_log.txt.zip><Sample of X11.txt>