New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

compiling Gem on Mac OS X fails - configure: error: GL (headers) not found! #153

Closed
popesz opened this Issue Sep 7, 2017 · 13 comments

Comments

Projects
None yet
3 participants
@popesz

popesz commented Sep 7, 2017

I want to compile Gem from github on Mac OS X but already at configure I got the error:

configure: error: GL (headers) not found! you need openGL!!

however
glxinfo says:

glxinfo | grep "OpenGL version"

OpenGL version string: 2.1 ATI-1.51.8

How can I compile with success?
Any hints?

Best,
Popesz

Mac OS X 10.12.6
MacBook Pro (Retina, 15-inch, Mid 2015)
Processor: 2,5 GHz Intel Core i7
Graphics: AMD Radeon R9 M370X 2048 MB
Intel Iris Pro 1536 MB
OpenGL missing.zip

@umlaeute

This comment has been minimized.

Show comment
Hide comment
@umlaeute

umlaeute Sep 7, 2017

Owner

please attach the logfiles as plain text files (zipped if need be). please do not use doc, ods or rtf.
It's pretty easy to create text-files, just redirect the output from the scripts to a file:

 ./configure --with-whatever-flags > configure.log
Owner

umlaeute commented Sep 7, 2017

please attach the logfiles as plain text files (zipped if need be). please do not use doc, ods or rtf.
It's pretty easy to create text-files, just redirect the output from the scripts to a file:

 ./configure --with-whatever-flags > configure.log
@umlaeute

This comment has been minimized.

Show comment
Hide comment
@umlaeute

umlaeute Sep 7, 2017

Owner

Also the output of glxinfo is irrelevant in two aspects:

  • on OSX we don't use GLX (which is OpenGL for X-Servers) but the native OpenGL framework
  • the success of glxinfo (or similar), only shows that you have the runtime libraries for OpenGL installed. It doesn't tell us anything about the presence of Developer headers/libraries.

Please also include the generated config.log file.

Owner

umlaeute commented Sep 7, 2017

Also the output of glxinfo is irrelevant in two aspects:

  • on OSX we don't use GLX (which is OpenGL for X-Servers) but the native OpenGL framework
  • the success of glxinfo (or similar), only shows that you have the runtime libraries for OpenGL installed. It doesn't tell us anything about the presence of Developer headers/libraries.

Please also include the generated config.log file.

@popesz

This comment has been minimized.

Show comment
Hide comment
@popesz

popesz Sep 7, 2017

Here you are:

config.log.zip
Thanks for your help:
Popesz

popesz commented Sep 7, 2017

Here you are:

config.log.zip
Thanks for your help:
Popesz

@megrimm

This comment has been minimized.

Show comment
Hide comment
@megrimm

megrimm Sep 7, 2017

Contributor

could it be possible your command line tools are not installed or not installed properly? you ran i assume:

$ xcode-select --install

what do these tell you:
$ xcode-select -p
$ xcode-select -v

Contributor

megrimm commented Sep 7, 2017

could it be possible your command line tools are not installed or not installed properly? you ran i assume:

$ xcode-select --install

what do these tell you:
$ xcode-select -p
$ xcode-select -v

@popesz

This comment has been minimized.

Show comment
Hide comment
@popesz

popesz Sep 7, 2017

popesz commented Sep 7, 2017

@megrimm

This comment has been minimized.

Show comment
Hide comment
@megrimm

megrimm Sep 8, 2017

Contributor

well thats right...

hmmm... not sure if it has any relation to #26

it also seems like you are compiling against a 32bit version of Pd?

i have attached my log file from successful ./configure.... maybe there is something there to look for? you can do something like:

diff -u your.config.log my.config.log | mate

which pipes diff output to textmate if you have that installed.

also... curious... have you tried to build after configure?

config.log.zip

Contributor

megrimm commented Sep 8, 2017

well thats right...

hmmm... not sure if it has any relation to #26

it also seems like you are compiling against a 32bit version of Pd?

i have attached my log file from successful ./configure.... maybe there is something there to look for? you can do something like:

diff -u your.config.log my.config.log | mate

which pipes diff output to textmate if you have that installed.

also... curious... have you tried to build after configure?

config.log.zip

@popesz

This comment has been minimized.

Show comment
Hide comment
@popesz

popesz Sep 9, 2017

popesz commented Sep 9, 2017

@megrimm

This comment has been minimized.

Show comment
Hide comment
@megrimm

megrimm Sep 9, 2017

Contributor

i remember having trouble such as this a couple years ago but I do not remember the steps I took to resolve. I do not think it is Gem (since mine has been building fine for quite a while) but likely how your system is set up. You might want to try uninstalling pkg-config, gettext, automake, libtool and then reinstall in the correct order....

i remember getting this all setup and working can be really finicky. can you uninstall homebrew stuff and follow this closely after uninstalling homebrew stuffs?

Contributor

megrimm commented Sep 9, 2017

i remember having trouble such as this a couple years ago but I do not remember the steps I took to resolve. I do not think it is Gem (since mine has been building fine for quite a while) but likely how your system is set up. You might want to try uninstalling pkg-config, gettext, automake, libtool and then reinstall in the correct order....

i remember getting this all setup and working can be really finicky. can you uninstall homebrew stuff and follow this closely after uninstalling homebrew stuffs?

@popesz

This comment has been minimized.

Show comment
Hide comment
@popesz

popesz Sep 9, 2017

popesz commented Sep 9, 2017

@megrimm

This comment has been minimized.

Show comment
Hide comment
@megrimm

megrimm Sep 9, 2017

Contributor

wow... quite the ordeal here :)

if you do:

$ ./configure --help

you get a bunch of command line options. you can try a bunch out just at least to get it to build correctly... then maybe we figure out what the initial error is all about.

so for example:

$ ./configure --without-glfw3

disables glfw3 (GLFW3 windowing).... so keep finding what is causing your hang ups, disable, and try again. process of elimination i guess... :)

Contributor

megrimm commented Sep 9, 2017

wow... quite the ordeal here :)

if you do:

$ ./configure --help

you get a bunch of command line options. you can try a bunch out just at least to get it to build correctly... then maybe we figure out what the initial error is all about.

so for example:

$ ./configure --without-glfw3

disables glfw3 (GLFW3 windowing).... so keep finding what is causing your hang ups, disable, and try again. process of elimination i guess... :)

@popesz

This comment has been minimized.

Show comment
Hide comment
@popesz

popesz Sep 11, 2017

popesz commented Sep 11, 2017

@umlaeute

This comment has been minimized.

Show comment
Hide comment
@umlaeute

umlaeute Sep 11, 2017

Owner
Owner

umlaeute commented Sep 11, 2017

@popesz

This comment has been minimized.

Show comment
Hide comment
@popesz

popesz Sep 11, 2017

popesz commented Sep 11, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment