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

autoreconf ? #3

Closed
MatMaul opened this issue Sep 20, 2017 · 3 comments
Closed

autoreconf ? #3

MatMaul opened this issue Sep 20, 2017 · 3 comments

Comments

@MatMaul
Copy link
Collaborator

MatMaul commented Sep 20, 2017

Any reason to explicitly force autoreconf on most of the libs ?
I have nothing of the sort in my build and all is working.

@TingPing
Copy link
Member

Some of the libraries had too old autoconf files for arm so that fixed it. To avoid tracking them down one by one and dealing with the builders it was just done to all of them as it is generally harmless (Debian runs it on every single package they have for example).

@MatMaul
Copy link
Collaborator Author

MatMaul commented Sep 20, 2017

Ok fine for me thanks for the explanation.

@cosimoc
Copy link
Collaborator

cosimoc commented Sep 20, 2017

Yeah, I actually don't usually do it unconditionally for the dependencies I add, but I don't think it's worth going over them right now.

@cosimoc cosimoc closed this as completed Sep 20, 2017
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

No branches or pull requests

3 participants