#18135: gimp2: no_x11 variant still links against X11 ---------------------------------+------------------------------------------ Reporter: simon@… | Owner: devans@… Type: defect | Status: assigned Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: no_x11 quartz | Port: gimp2 ---------------------------------+------------------------------------------ Changes (by devans@…): * keywords: gimp2 no_x11 quartz => no_x11 quartz * status: new => assigned Comment: I'm surprised to hear this as I spent the past weekend building the gimp port (including gimp2) from scratch in the native mode. The build went well with no tendency to install X11 related ports and gimp runs with no errors (including file-uri) and no references to X11 at all. Even gnome-vfs built without X11 references so this is possible. The key to success here is to make sure that not only gimp2 but all dependencies (and their dependencies, etc) are built without reference to X11 as any dependency that accidentally gets built with X11 will typically forward that X11 dependency upwards to its dependents via its pkg-config files. Because of this, it is, IMO, impractical to acheive this in a MacPorts installation that is trying to build both +x11 and +no_x11 ports. I, therefore, recommend using a separate installation of MacPorts for no_x11/quartz development using a different path than the default. I user /opt/local for X11 development and /opt/gtk for no_x11 development and switch between the two by changing my $path. Here is what I did to acheive success: * installed a fresh MacPorts installation (1.7.0) using path /opt/gtk and set shell search path to this. At this point, no ports installed at all. * in /opt/gtk/etc/macports/variants.conf add +no_x11 +quartz to apply these variants to all dependent ports. At this point both are needed as the use of these variants is still not completely consistent. * sudo port install gimp2 (or gimp if you want all the bells and whistles) * wait a long time (about 24 hours on my old G4). Is this consistent with what you did? What exactly were the symptoms that you experienced (compile time, run time, etc?). Is MacPorts finding and building X11 dependencies or is the build complaining it can't find a X11 reference (indicating a requirement forwarded by pkg-config typically). BTW, the build I did was just before the recent wholesale dependency changes concerning the xorg-* ports and references to them so I am rebuilding gimp2 now as we speak to make sure that that didn't introduce any new unwanted X11 dependencies. I'm considering the issue with gvfs to be a separate issue, that is, the relative merits of gvfs vs gnome-vfs as contrary to popular belief (as in Sven's reply to your bug report) gnome-vfs will build and run without X11 if its dependencies are X11 clean. The main culprit here is usually dbus which needs to be built without X11 support (now the default in the latest dbus port in MacPorts). Actually, I would prefer to use gvfs as part of a general move away from gnome specific functionality to GTK functionality where available but for the present case I think that change just masks the real problem of gnome-vfs and dependents being built with X11 when it should be without. I had gvfs as the default originally for the 2.6 branch but I received some reports that it didn't work in MacPorts so I reverted to gnome-vfs as the default. Is this working for you? If so I would prefer to make gvfs the default for all cases rather than just a requirement for no_x11. Thanks for your report and I appreciate your frustration. Looking forward to more details so we can get to the bottom of this. -- Ticket URL: <http://trac.macports.org/ticket/18135#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS