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

[funfuzz] compileShell fails on Fedora due to autoconf 2.13 binary name discrepancy #9

Closed
nth10sd opened this issue Jul 10, 2015 · 3 comments
Labels

Comments

@nth10sd
Copy link
Contributor

nth10sd commented Jul 10, 2015

compileShell fails on Fedora because it is "autoconf-2.13" there, not "autoconf2.13" as per Ubuntu.

Thanks :Waldo for helping to test here.

@nth10sd nth10sd added the bug label Jul 10, 2015
@nth10sd nth10sd self-assigned this Jul 10, 2015
@jruderman
Copy link
Contributor

client.mk solves this by calling "which autoconf-2.13 autoconf2.13 autoconf213" to find out which one exists on PATH:

https://dxr.mozilla.org/mozilla-central/source/client.mk#60

@nth10sd
Copy link
Contributor Author

nth10sd commented Jul 10, 2015

I worked around this issue in rev eafec98 but I agree that this should be fixed the way client.mk does it.

@nth10sd nth10sd removed their assignment Jul 15, 2015
@nth10sd
Copy link
Contributor Author

nth10sd commented Jul 15, 2015

Worked around, patches accepted for now.

@nth10sd nth10sd changed the title compileShell fails on Fedora due to autoconf 2.13 binary name discrepancy [funfuzz] compileShell fails on Fedora due to autoconf 2.13 binary name discrepancy Feb 10, 2017
nth10sd added a commit to nth10sd/funfuzz that referenced this issue Apr 27, 2018
@nth10sd nth10sd closed this as completed in d95208a May 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants