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

Fix bug "sh: autom4te: command not found" #1

Merged
merged 1 commit into from
Nov 26, 2013

Conversation

mebsout
Copy link
Contributor

@mebsout mebsout commented Nov 25, 2013

When building under Mavericks, user gets error:
sh: autom4te: command not found
although the sources compile perfectly fine by hand.
This patch fixes this bug (maybe the same needs to be done for 'pkg-config').

When building under Mavericks, user gets error:
sh: autom4te: command not found
although the sources compile perfectly fine by hand.
This patch fixes this bug (maybe the same needs to be done for 'pkg-config').
@railwaycat
Copy link
Owner

Thanks mebsout!

It's little confusing why :build cause the issue... Could you give me some time to reproduce it first? Another user also met this issue and mentioned it's on a fresh-installed mavericks.

https://github.com/railwaycat/emacs-mac-port/issues/36

@mebsout
Copy link
Contributor Author

mebsout commented Nov 25, 2013

No problem. Please take your time.

@railwaycat
Copy link
Owner

Hi mebsout, I tried on a fresh-installed 10.9 VM, it's easily reproduced. But I still not know why it says autom4te not found and why remove :build would solve this issue. I will appreciate if you could teach me how you find this solution:)

I will merge this pull and thanks again!

railwaycat added a commit that referenced this pull request Nov 26, 2013
Fix bug "sh: autom4te: command not found"
@railwaycat railwaycat merged commit 8808066 into railwaycat:master Nov 26, 2013
@railwaycat
Copy link
Owner

If similar issue occur on pkg-config in the future, I will remove :build for pkg-config too.

@arnested arnested mentioned this pull request Mar 15, 2015
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

Successfully merging this pull request may close these issues.

2 participants