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 failed in step 'Installing m4 for build' #1097

Closed
asalfo opened this Issue Nov 20, 2018 · 5 comments

Comments

Projects
None yet
6 participants
@asalfo
Copy link

asalfo commented Nov 20, 2018

I got this error when building:
/usr/local/Cellar/crosstool-ng/1.23.0_2/lib/crosstool-ng-1.23.0/scripts/functions: line 297: 69886 Segmentation fault: 11 "${@}" 2>&1

Crosstool-NG version crosstool-ng-1.23.0
macOS version 10.14.1 (Mojave)
Darwin Kernel Version 18.2.0: Fri Oct 5 19:41:49 PDT 2018; root:xnu-4903.221.2~2/RELEASE_X86_64 x86_64

build.log
config.txt

Thanks

@stevielavern

This comment has been minimized.

Copy link

stevielavern commented Nov 22, 2018

Exact same issue here.

@stilor

This comment has been minimized.

Copy link
Contributor

stilor commented Nov 24, 2018

All I can say from the build.log is that apparently, the make utility that crosstool-NG built right before the m4 crashed for some reason. You can try to use the hst make, if one is installed. You can also try crosstool-NG from master to see if it has been fixed. If that doesn't work - sorry, I don't have a macOS system to debug the issues like this, and Apple hasn't been very friendly to let people run their OS in virtual machines.

As I mentioned elsewhere, macOS is now officially unsupported. I'll review/pick up the patch if one posts a PR for this issue but won't attempt to guess the root cause myself. Closing this issue.

@stilor stilor closed this Nov 24, 2018

@brandon-powell

This comment has been minimized.

Copy link

brandon-powell commented Dec 31, 2018

This appears to be caused by invalid binutils binaries. I had the same issue but was able to isolate it to the binutils package installed through homebrew. The fix is to uninstall and reinstall binutils via brew (you may have to use the --ignore-dependencies flag) or recompile binutils if you built them from source.

I can't test this now since I've already reinstalled my binutils, but my best guess is that Homebrew didn't automatically update the binutils to the Mojave bottle when we upgraded from High Sierra to Mojave (because there haven't been any actual binutils version changes since then), and there was an ABI difference that affected binutils.

@scr34m

This comment has been minimized.

Copy link

scr34m commented Feb 1, 2019

I can confirm this.

These two commands fix the issue reported by @asalfo

brew uninstall --ignore-dependencies binutils
brew install binutils
@axos88

This comment has been minimized.

Copy link

axos88 commented Mar 13, 2019

I can confirm this, it @scr34m's suggestion fixed it for me too. I recently upgraded to mojave, might've been the reason why my binutils broke.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.