[MacPorts] #50868: _CGLGetCurrentContext not found when building ruby2.3 extensions
#50868: _CGLGetCurrentContext not found when building ruby2.3 extensions ---------------------+-------------------------------- Reporter: david@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: ---------------------+-------------------------------- Attempting to build wpscan ruby2.3 dies with the dreaded + recurring "dyld: Symbol not found: _CGLGetCurrentContext" error. Build log for ffi + mkmf attached. Did a deinstall + reinstall + port select on Ruby. Likely overkill. Paths for ruby + gem look correct... {{{ imac> port select --list ruby Available versions for ruby: none ruby23 (active) imac> ruby --version ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-darwin15] imac> ruby2.3 --version ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-darwin15] imac> gem --version 2.5.1 imac> gem2.3 --version 2.5.1 }}} -- Ticket URL: <https://trac.macports.org/ticket/50868> MacPorts <https://www.macports.org/> Ports system for OS X
#50868: _CGLGetCurrentContext not found when building ruby2.3 extensions ----------------------+-------------------------------- Reporter: david@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: | ----------------------+-------------------------------- Comment (by david@…): Unable to modify header to set port=ruby + owner=raimue@macports.org -- Ticket URL: <https://trac.macports.org/ticket/50868#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#50868: _CGLGetCurrentContext not found when building ruby2.3 extensions ----------------------+-------------------------------- Reporter: david@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: | ----------------------+-------------------------------- Comment (by david@…): This ticket appears to be a duplicate of https://trac.macports.org/ticket/50806 so likely can be closed + worked in the first ticket. My apologies for missing the first ticket, when I opened this one. -- Ticket URL: <https://trac.macports.org/ticket/50868#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#50868: _CGLGetCurrentContext not found when building ruby2.3 extensions ------------------------+-------------------------------- Reporter: david@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: duplicate | Keywords: Port: | ------------------------+-------------------------------- Changes (by mf2k@…): * status: new => closed * resolution: => duplicate Comment: #50806 -- Ticket URL: <https://trac.macports.org/ticket/50868#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#50868: _CGLGetCurrentContext not found when building ruby2.3 extensions ----------------------+-------------------------------- Reporter: david@… | Owner: macports-tickets@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: ruby | ----------------------+-------------------------------- Changes (by mojca@…): * cc: mf2k@…, chlangley@…, kimuraw@… (added) * status: closed => reopened * resolution: duplicate => * port: => ruby Comment: I'm reopening this ticket because what was added to #50806 doesn't seem to be related to gnuplot at all and I have no clue where to look; gnuplot seems to work for so many others and I also suspect some `DYLD_LIBRARY_PATH` being set from some random place. According to Clemens:
my guess is that this is caused by ruby's build system setting `DYLD_LIBRARY_PATH`. I've seen the problem when a ruby thingy I tried to compile was calling `pkg-config`, which crashed because of `DYLD_LIBRARY_PATH` I worked around it at the time by replacing `${prefix}/bin/pkg-config` with `"unset DYLD_LIBRARY_PATH; exec ./pkg-config.bin "$@""`, but for this specific instance it's not really clear where that would have to be fixed.
David, please repeat the relevant parts that you wrote to #50806 because I'll close that other ticket. -- Ticket URL: <https://trac.macports.org/ticket/50868#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X
#50868: _CGLGetCurrentContext not found when building ruby2.3 extensions --------------------------+----------------------- Reporter: david@… | Owner: kimuraw@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: ruby ruby23 | --------------------------+----------------------- Changes (by mojca@…): * cc: kimuraw@… (removed) * status: reopened => new * port: ruby => ruby ruby23 * owner: macports-tickets@… => kimuraw@… -- Ticket URL: <https://trac.macports.org/ticket/50868#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X
#50868: _CGLGetCurrentContext not found when building ruby2.3 extensions --------------------------+----------------------- Reporter: david@… | Owner: kimuraw@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: ruby ruby23 | --------------------------+----------------------- Changes (by kimuraw@…): * status: new => closed * resolution: => fixed Comment: I fixed this problem at r148654 (port:ruby23 2.3.1_1). Try `gem install ffi` after `port upgrade ruby23`. I think this is a bug in mkmf.rb and reported to ruby core-team about this problem. https://bugs.ruby-lang.org/issues/12379 (ja) -- Ticket URL: <https://trac.macports.org/ticket/50868#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X
#50868: _CGLGetCurrentContext not found when building ruby2.3 extensions --------------------------+----------------------- Reporter: david@… | Owner: kimuraw@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: ruby ruby23 | --------------------------+----------------------- Comment (by kimuraw@…): This problem was fixed in upstream ruby's trunk and 2.3-branch The next release version (ruby-2.3.2) will work fine without this patch. -- Ticket URL: <https://trac.macports.org/ticket/50868#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts