After upgrading my OS X Lion to Mavericks, I've encountered with strange problems.
At first, It gave me segmentation fault or bus error. After searching for a bit I've noticed that it's related to the readline library. The solution was described by bugs.python.org:
curl -O http://bugs.python.org/file32324/patch_readline_issue_18458.sh
openssl sha1 patch_readline_issue_18458.sh # the digest should be 7cb0ff57820a027dd4ca242eb2418930f8f46b4c
sudo sh ./patch_readline_issue_18458.sh
This will disable the readline library. The errors are gone now but I have another problem. In Python shell when I press arrow keys (up, down, left or right) it gives me these: ^[[A, [[C^, ^[[B, ^[[D. I think the problem is still related to the readline library but I don't know how to solve it.
Thanks in advance.
Regards
I'm no authority on the guts of Python, so take my advice with caution. But, having encountered the same problem after the Mavericks upgrade (and using Python 2.7), I just did a
easy_install readline
at the command line, and everything seems to be working again. No more segmentation error, and arrow keys in the Python shell appear to be functioning normally.
The (brand new) Python 3.3.3rc1 fixes the SegFault problem.
It's here: http://www.python.org/download/releases/3.3.3/
Related
I am trying to install Erlang in a Mac OS system with Mojave on it. However the installation hangs for no apparent reason:
$ asdf install erlang 22.2.8
asdf_22.2.8 is not a kerl-managed Erlang/OTP installation
The asdf_22.2.8 build has been deleted
Extracting source code
Building Erlang/OTP 22.2.8 (asdf_22.2.8), please wait...
I know the issue is not the network, as I have downloaded everything and the step that hangs forever is the Building step.
I have removed and re-installed both asdf and Erlang from scratch as well, but it didn't fix the issue.
I believe I have all necessary dependencies as well, otherwise the re-installation would have failed.
What can I do to fix this?
Go to ~/.asdf/plugins/erlang/kerl-home/builds/asdf_22.2.8 and look at the otp_build_22.2.8.log file. It should tell you what's going on.
Solution
Thanks to the post by #legoscia I went to ~/.asdf/plugins/erlang/kerl-home/builds/asdf_22.2.8 and looked at the otp_build_22.2.8.log while it was still being built.
By checking this I was actually able to find out that I had a problem with my brew installation, which in turn meant I was using a very outdated version of XCode and XTools.
By forcing an upgrade on my machine (and as a consequence fixing my broken brew installation), I was then able to smoothly run and install asdf install erlang.
I know this is the solution, but I will give credit to #legoscia, as without him/her I would not have been able to fix my issue.
I recently did an update/upgrade with homebrew, and now gv no longer opens any of my .ps files. The Ghostscript error window that comes up says "Unknown device: x11 Error: PostScript interpreter failed in main window".
If I try gs --help, it doesn't list x11 under available devices, and the Default output device is "bbox". I tried uninstalling and reinstalling through homebrew. I tried to reinstall adding "--with-x11" but that throws the error "invalid option: --with-x11" - apparently that's no longer allowed. I've upgraded my command line code through the app store, and tried all of this again - nothing changed. I'm on High Sierra 10.13.3, using Homebrew 2.0.6, ghostscript 9.26_1, and gv 3.7.4.
I'm not a Mac developer so I'm not completely familiar with Homebrew, but it does sound like the package has been built wiithout X11 support. The fact that --help doesn't list the device is pretty clear.
I do notice from the website that in the last 30 days there have been 2 downloads of --with-x11. So possibly they've removed X11 support recently.
The only other thing I can suggest (assuming you are comfortable with compiling yourself) is to get the sources from www.ghostscript.com, untar the source tarball, then in a terminal window, from the 'ghostpdl' directory, execute ./autogen.sh, then when that is complete, execute 'make'.
Assuming you have autotools, gcc and the X11 development package, that should build a version of Ghostscript which includes X support. Looking at the Homebrew forumla, and assuming this has worked for you in the past, I think you should be able to build Ghostscript that way.
You might want to add --disable-cups --disable-compile-inits --disable-gtk --disablefontconfig --without-libidn to the ./autogen.sh command line to mimic the Homebrew formula. I'm not sure why they disable CUPS, but whatever.
Other than that, this isn't really a Ghostscript question as such, you would need to contact whoever handles the Homebrew Ghostscript distribution, which isn't any of the Ghostscript development team.
For those searching for a solution, I've put together a custom Homebrew tap that allows you to easily install GV (commonly called Ghostview, but really a derivative of it):
brew install johnhcc/gs-x11/gv
This will automatically install a version of Ghostscript with X11 enabled in the process (it is a dependency). You can optionally install the dependency by itself, it you want:
brew install johnhcc/gs-x11/ghostscript-x11
The main page is here:
https://github.com/johnhcc/homebrew-gs-x11
I get the following error when trying to install valgrind on the version of macOS using brew:
valgrind: This formula either does not compile or function as expected
on macOS versions newer than Sierra due to an upstream
incompatibility. Error: An unsatisfied requirement failed this build.
I have tried to follow suggestions from all related posts on the issue, and even tried building valgrind using the ./configure option after downloading the source tarball. But that too fails with a gcc incompatibility error, which I am unable to overcome, despite following workaround suggestions on the Web.
Any help would be appreciated.
TIA
Vinod
brew install --HEAD valgrind seems to work now.
See this issue for more details.
You may wish to build it directly and install instead of using home-brew. I have created a port of valgrind 3.13.0 to work on macOS High Sierra (10.13.x). You can get it here: https://github.com/padiakalpesh/valgrind_3.13_high_sierra
Once you have obtained the source, run the following commands from inside the source directory:
./configure
make
sudo make install
I'm trying to install homebrew on my mac verison 10.7.5, error msg comes up: The requested URL returned error: 404 Error: Failed to download resource "openssl" Download failed: https://raw.githubusercontent.com/DomT4/LibreMirror/master/Open help! how do i fix?
Try update your brew
brew update
I have encountered the same issue on my mac (10.11 El Captian)
It's seems OpenSSL want to force users and package management softwares to update by removing their previous version.
I agree with #Webb Lu on this one.
Try brew update a few times. If this isn't working then try the command brew doctor to correct any errors.
If this fixes the issue, you may want to then run brew upgrade to upgrade anything that is out of date. For some reason I had to reinstall Xcode last night to run the upgrade command. Not sure what happened there, but it seemed to work for me.
I don't know if this is the solution for your issue, but I figured I'd throw my hat in the ring ha ha.
Best of luck!
After having installed Mavericks I got this problem on a code that compiled without problems before.
xcode-select --install triggers the installation without any strange problems,
yet when I try to build something with Eclipse it gives me
"Include path not found (/Applications/Xcode.app/Contents/Developer/usr/llvm-gcc-4.2/lib/gcc/i686-apple-darwin11/4.2.1/include)"
Infact in /Applications/Xcode.app/Contents/Developer/usr/ there's no llvm-gcc-4.2.
How can I fix this?
On my system in terminal:
/usr/bin/llvm-gcc-4.2
produces:
/usr/bin/llvm-gcc-4.2
/usr/bin/llvm-gcc-4.2
is linked to :
/usr/llvm-gcc-4.2/bin/llvm-gcc-4.2
Also
$ which llvm-gcc
produces:
/usr/bin/llvm-gcc
and
/usr/bin/llvm-gcc is linked to /usr/bin/clang
Note that Apple no longer provides llvm-gcc as an option in Xcode so perhaps it is no longer supplied as a command-line tool.
I had problems with the command line tools as well after upgrading to Mavericks, despite having updated Xcode, and I am quite sure I also installed the command line tools. Still, you can add them "by hand" downloading from apple site. I am not sure if it is any sort of bug of such, but anyway, I recommend you to download the latest Mavericks' Command Line Tools (late October) on Apple's developer site (needs free registration)