Skip to content
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

Build fails on OSX 10.10.2 #10

Closed
aptituz opened this issue Apr 19, 2015 · 8 comments
Closed

Build fails on OSX 10.10.2 #10

aptituz opened this issue Apr 19, 2015 · 8 comments

Comments

@aptituz
Copy link

aptituz commented Apr 19, 2015

Hi there,

when trying to build and install beaker I've noticed that unf_ext fails to build:

uilding native extensions. This could take a while...
ERROR: Error installing unf_ext:
ERROR: Failed to build gem native extension.

/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby extconf.rb

checking for main() in -lstdc++... yes
creating Makefile

make "DESTDIR="
compiling unf.cc
In file included from unf.cc:1:
In file included from ./unf/normalizer.hh:4:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/vector:265:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/__bit_reference:15:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/algorithm:628:
In file included from /Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/memory:604:
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/iterator:341:10: fatal error: '__debug' file not found

include <__debug>

     ^

1 error generated.
make: *** [unf.o] Error 1

Gem files will remain installed in /Library/Ruby/Gems/2.0.0/gems/unf_ext-0.0.7.1 for inspection.
Results logged to /Library/Ruby/Gems/2.0.0/gems/unf_ext-0.0.7.1/ext/unf_ext/gem_make.out

Any change to fix this? Tell me, if you need further information.

Thanks and best Regards,
Patrick

@knu
Copy link
Owner

knu commented Apr 20, 2015

It doesn't reproduce for me with OS X 10.10.3 and Xcode 6.3, but there seem to be some people in the same boat as you. Try fixing your installation as described here: http://stackoverflow.com/questions/29529455/missing-c-header-debug-after-updating-osx-command-line-tools-6-3

@aptituz
Copy link
Author

aptituz commented Apr 20, 2015

Thanks for the hint. I'll first try, if the missing update of my system
will already fix it. Otherwise I'll have a look at the described stuff.

2015-04-20 5:44 GMT+02:00 Akinori MUSHA notifications@github.com:

It doesn't reproduce for me with OS X 10.10.3 and Xcode 6.3, but there
seem to be some people in the same boat as you. Try fixing your
installation as described here:
http://stackoverflow.com/questions/29529455/missing-c-header-debug-after-updating-osx-command-line-tools-6-3


Reply to this email directly or view it on GitHub
#10 (comment).

@aptituz
Copy link
Author

aptituz commented Apr 20, 2015

Upgrading OSX did not work. Downgrading to Xcode 6.2 worked. JFTR.

2015-04-20 8:11 GMT+02:00 Patrick Schönfeld patrick.schoenfeld@gmail.com:

Thanks for the hint. I'll first try, if the missing update of my system
will already fix it. Otherwise I'll have a look at the described stuff.

2015-04-20 5:44 GMT+02:00 Akinori MUSHA notifications@github.com:

It doesn't reproduce for me with OS X 10.10.3 and Xcode 6.3, but there
seem to be some people in the same boat as you. Try fixing your
installation as described here:
http://stackoverflow.com/questions/29529455/missing-c-header-debug-after-updating-osx-command-line-tools-6-3


Reply to this email directly or view it on GitHub
#10 (comment).

@espen
Copy link

espen commented Apr 23, 2015

Apple updated Command Line Tools to version 6.3 which fixes this.

@aptituz
Copy link
Author

aptituz commented Apr 26, 2015

Good to know. Thanks for the hint.

@gertig
Copy link

gertig commented Sep 20, 2015

This may also be due to not having agreed to the Xcode license agreements. I had this same issue and after launching Xcode and agreeing to the license agreement the problem was solved.

@pioto
Copy link

pioto commented Oct 1, 2015

I'm using ruby from MacPorts, and found the fix for this issue was to also install GCC from MacPorts:

sudo port install apple-gcc42
sudo port select gcc apple-gcc42

@peterc
Copy link

peterc commented Nov 10, 2015

I had the same problem, but found it was simply because I hadn't accepted the T&Cs after Xcode updated itself without me noticing. So if you have this issue, try running gcc -v first to make sure it runs..

@knu knu closed this as completed Apr 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants