Skip to content


clang segmentation fault during mpfr install #15061

boriskro opened this Issue · 14 comments

6 participants


I cannot install mpfr. I have all the latest updates for Xcode/command-line tools/homebrew and 'brew doctor' runs cleanly.

Any ideas?


I got the same problem. It is possible that mpfr is broken with the new Xcode/command line tools because I successfully compiled it with the previous version. Probably new patches are needed.


For me adding the option --use-llvm to brew install worked.


You're right, adding --use-llvm worked. Apparently there was something wrong with make and that is why I got "Error: Failed executing: make" (build environment issue perhaps?) before. Thanks!


Adding --use-llvm worked here as well. Thanks!

@boriskro boriskro closed this
@adamv adamv reopened this

Reopening until we address this.


Confirmed. I also get the segmentation fault.

@adamv MacPorts adds --disable-thread-safe to configure. Not sure, if we want that.

Using --env=std fixes this segmentation fault for me. Here is the log of a successful build (you'll have to click "raw" because it's long).

So if anyone can confirm that --env=std solves this, I can add env :std into the formula.


I can confirm that "brew install --env=std mpfr" works for me on OSX 10.8.2 with Xcode 4.5.1.


@pvstodghill thanks. I did a PR.

Homebrew member

Superenv passes more flags to clang than stdenv, I guess in this case we expose a bug in clang because of it. Don't close this, I need to look into it.


Should I pull the pull request in the meantime?


Probably fixed in 137d488

@adamv adamv closed this

I need to look into it. -- @mxcl

Did you had the chance to do so already?


On 10.8.3 (Xcode-only) with Clang: 4.2 build 425 can build this with superenv.

@rghammonds rghammonds referenced this issue in mistydemeo/tigerbrew

mpfr failed to build on 10.4.11 #15

@nesv nesv added a commit to nesv/homebrew that referenced this issue
@samueljohn samueljohn mpfr: With clang build 425 it works in superenv
See #15061
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.