Opened 6 years ago

Closed 6 years ago

#56808 closed defect (duplicate)

gource 'configure' fails to find libGL.dylib

Reported by: chucko58 (Chuck Fry) Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.5.3
Keywords: Cc: ryandesign (Ryan Carsten Schmidt)
Port: gource

Description

On a MacBook Pro (Retina, 15-inch, Early 2013) running macOS Sierra 10.12.6:

MacPorts 2.5.3 is installed without root privileges, with prefix=/Users/cfry

'port install gource' fails with the following output:

Fetching distfiles for gource
--->  Attempting to fetch gource-0.47.tar.gz from https://distfiles.macports.org/gource
--->  Verifying checksums for gource
--->  Extracting gource
--->  Configuring gource
Error: Failed to configure gource, consult /Users/cfry/var/macports/build/_Users_cfry_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_gource/gource/work/gource-0.47/config.log
Error: Failed to configure gource: configure failure: command execution failed
Error: See /Users/cfry/var/macports/logs/_Users_cfry_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_gource/gource/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port gource failed
rdnzl:plexil-4 cfry$ 

The tail of the build log shows:

:info:configure configure: error: Could not link against -lGL !
:info:configure Command failed:  cd "/Users/cfry/var/macports/build/_Users_cfry_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_gource/gource/work/gource-0.47" && ./configure --prefix=/Users/cfry --disable-sdltest 
:info:configure Exit code: 1
:error:configure Failed to configure gource, consult /Users/cfry/var/macports/build/_Users_cfry_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_gource/gource/work/gource-0.47/config.log
:error:configure Failed to configure gource: configure failure: command execution failed
:debug:configure Error code: NONE
:debug:configure Backtrace: configure failure: command execution failed
:debug:configure     while executing
:debug:configure "$procedure $targetname"
:error:configure See /Users/cfry/var/macports/logs/_Users_cfry_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_gource/gource/main.log for details.

On this system libGL.dylib is in /Users/cfry/lib (i.e. $prefix/lib), but isn't present in /usr/lib.

I'm attaching macports.conf and the gzipped build log file. I'm happy to provide any other information requested.

Attachments (2)

gource_install_log.gz (4.3 KB) - added by chucko58 (Chuck Fry) 6 years ago.
Install log, gzipped
macports.conf (8.3 KB) - added by chucko58 (Chuck Fry) 6 years ago.
MacPorts configuration file on this installation

Download all attachments as: .zip

Change History (5)

Changed 6 years ago by chucko58 (Chuck Fry)

Attachment: gource_install_log.gz added

Install log, gzipped

Changed 6 years ago by chucko58 (Chuck Fry)

Attachment: macports.conf added

MacPorts configuration file on this installation

comment:1 Changed 6 years ago by mf2k (Frank Schima)

Port: gource added; gource-0.47 removed

comment:2 Changed 6 years ago by chucko58 (Chuck Fry)

I did find a libGL.dylib in /System/Library/Frameworks:

rdnzl:Downloads cfry$ find /System/Library/Frameworks -name 'libGL.*'
/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
rdnzl:Downloads cfry$ 

comment:3 in reply to:  description Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign added
Resolution: duplicate
Status: newclosed

Replying to chucko58:

:error:configure Failed to configure gource, consult /Users/cfry/var/macports/build/_Users_cfry_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_gource/gource/work/gource-0.47/config.log

Please attach this config.log file.

I'm not convinced that the problem relates to OpenGL. The "Could not link against" error message only appears in files that relate to boost, so I am more inclined to believe that the error relates to Boost, and that the error message just contains the wrong library name.

The problem might be fixed if we tell the configure script where to find boost.

In fact this is a duplicate of a very old ticket, #43608.

Note: See TracTickets for help on using tickets.