Martin,

You're not wrong about the user experience. So I installed XQuartz and  
the compile completed successfully. But when I launch gnucash, I get  
this:

Failed to load key /apps/gnucash/general/show_splash_screen: Failed to  
contact c
onfiguration server; some possible causes are that you need to enable  
TCP/IP net
working for ORBit, or you have stale NFS locks due to a system crash.  
See http:/
/www.gnome.org/projects/gconf/ for information. (Details -  1: Failed  
to get con
nection to session: dbus-launch failed to autolaunch D-Bus session:  
Autolaunch r
equested, but X11 support not compiled in.
Cannot continue.

Any ideas? Should I try again with the GnuCash list?

Ben

On 24 Dec 2008, at 11:54, Martin Costabel wrote:

> Benjamin So wrote:
>> Hi,
>> I tried again with XCode 3.1, but still got the familiar compile  
>> failure, although this time it complained about gtk:
>> "Building Dependency Tree...
>> Failed: phase compiling: gtk+2-2.14.5-1 failed
>> Before reporting any errors, please run "fink selfupdate" and
>> try again.  If you continue to have issues, please check to see if  
>> the
>> FAQ on fink's website solves the problem."
>> Searching further back in the logs, I found the following:
>> "You are attempting to build gtk+2 with version 3.1 of Xcode, which
>> requires an update to your installed version of X11.  Please download
>> and install X11 2.3.0 or later from
>>  http://xquartz.macosforge.org/trac/wiki/X112.3.0
>> Once you have installed X11 2.3.0, please re-attempt installation of
>> this package gtk+2."
>> So it looks like I need to install XQuartz after all?
>
> <rant> I think what we should have done long ago is to write  
> automatic bug reports to Apple each time such an error appears. They  
> need to be hit over the head until they give up the stupid idea of  
> having a separate X11SDK.pkg that serves no purpose apart from  
> making user's life miserable. They have even acknowlegded as much,  
> but their internal packaging policy seems to be impervious to  
> rational argument. </rant>
>
> The easiest way out is indeed to trash the X11 that comes with  
> Leopard and to install the xquartz version of X11. But in reality  
> the incompatibilities between X11SDK.pkg and X11User.pkg in their  
> many versions on Leopard (prior to xcode-3.1.2) are tiny  
> trivialities like wrong symlinks or wrong library versions mentioned  
> in some *.la files. All of these are easily user-fixable within  
> Leopard's X11. It is just a nuisance to find out each time which one  
> of the incompatibilities it is that is causing the failure. At least  
> the xquartz versions are internally consistent (even though they  
> don't come with xmkmf, just to make user's life a little miserable,  
> too).
>
> -- 
> Martin
>
>
>
>
>


------------------------------------------------------------------------------
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to