[MacPorts] #50305: gtkglext configure error on El Capitan
#50305: gtkglext configure error on El Capitan --------------------+-------------------------------- Reporter: me@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: gtkglext --------------------+-------------------------------- After upgrading to El Capitan and reinstalling macports, while reinstalling previously requested ports, gtkglext fails to configure. I don't see any obviously fatal errors in the attached configure log. -- Ticket URL: <https://trac.macports.org/ticket/50305> MacPorts <https://www.macports.org/> Ports system for OS X
#50305: gtkglext @1.2.0 +quartz: error: X development libraries not found -----------------------+------------------- Reporter: me@… | Owner: jd@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: gtkglext | -----------------------+------------------- Changes (by ryandesign@…): * owner: macports-tickets@… => jd@… Comment: Looks like the error is: {{{ configure:22945: checking for X configure:23169: result: disabled configure:24261: error: X development libraries not found }}} Looks like the port's +quartz variant not only enables quartz support, but also disables X11 support, but gtkglext apparently requires X11. You can work around the problem for now by not attempting to use the +quartz variant. -- Ticket URL: <https://trac.macports.org/ticket/50305#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#50305: gtkglext @1.2.0 +quartz: error: X development libraries not found -----------------------+------------------- Reporter: me@… | Owner: jd@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: gtkglext | -----------------------+------------------- Comment (by me@…): I'm using the same variants that were installed before the upgrade. That doesn't sound like something that would work before a Mac OS upgrade but not after. Can someone confirm whether this problem occurs on other systems? -- Ticket URL: <https://trac.macports.org/ticket/50305#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts