You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee='https://github.com/ned-deily'closed_at=<Date2014-09-23.19:57:16.829>created_at=<Date2014-09-23.19:39:40.213>labels= ['OS-mac', 'build']
title='Python build problems via Homebrew on Mac OS X when GNU core/find utils are default'updated_at=<Date2014-09-23.19:57:16.825>user='https://bugs.python.org/todddsm'
Installing Python via Homebrew on Mac OS X has build issues if the GNU core/find utils are set as defaults on the system. OS X is very common, on it Homebrew is very common, via Homebrew GNU utilities are among the first installations; EG: http://goo.gl/OodjHI
GNU core/find utils are likely the most common tools use on POSIX systems but Mac wants to keep rolling with UNIX tools. The Makefile is flexible. If it discovers the rm program in: /usr/local/opt/coreutils/libexec/gnubin/rm (where Homebrew would install it) the build 'could' break.
Testing is ad hoc but seen by many and confirmed as "likely" by ned_deily; he adds: "that particular problem is simple to fix: just change the Makefile to /usr/bin/rm."
This is the work-around for now.
Props to ned_deily; this is an old/annoying problem, now solved.
Thanks for the report! On further inspection, the whole rm thing isn't needed anymore with Python no longer maintained in svn. Fixed for release in 2.7.9, 3.4.3, and 3.5.0.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: