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

Show any error messages from dlopen #123

Open
tkelman opened this issue Jan 16, 2015 · 1 comment · May be fixed by #126
Open

Show any error messages from dlopen #123

tkelman opened this issue Jan 16, 2015 · 1 comment · May be fixed by #126

Comments

@tkelman
Copy link
Contributor

tkelman commented Jan 16, 2015

Mostly a reminder to myself to figure out how to do this, if no one else gets to it before I can.

Dependency problems (like libgfortran not having a certain symbol, in my case) are virtually impossible to debug from just LoadError: Provider BinDeps.BuildProcess failed to satisfy dependency libfoo. If the problem is coming from a dlopen error, would be best to show the full error instead of relying on manually trying dlopen (and even knowing to try that as a debugging option) to figure out what's wrong.

@staticfloat
Copy link
Member

It would be nice to auto-run BinDeps.debug() when something fails. That's what we want to do 50% of the time, and the other 50% we just want to see the errors from dlopen().

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants