-
Notifications
You must be signed in to change notification settings - Fork 281
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
Tests don't set rpath #21
Comments
Doing 'make check' for base already runs the base testsuite on the uninstalled library, which is usually what you want. I looked up -rpath online and found that the order of precedence for library search is:
I added a couple of lines to build the testcases with -rpath as it seems harmless, but I'm not at all sure it actually resolves either of those two issues most of the time since LD_LIBRARY_PATH takes precedence, though it clearly fixes them in the case you are building/testing a library for the first time (ie there is no installed version). So if you run testcases using gnustep-tests or even directly in a gnustep environment, I expect the LD_LIBRARY_PATH will cause the installed version to be used (if it exists), but the uninstalled version (pointed to by -rpath) to be used otherwise. On the other hand, if you run them using 'make check' the normal code to set LD_LIBRARY_PATH to point to the uninstalled library for the duration of the tests will still be used. |
Does it? I encountered this problem running
This is pretty much a minimum if I'm trying to debug a failing test, yes. |
eg. $ cd Tests
One option if you don't want to alter your normal shell is to put the LD_LIBRARY_PATH setup into TestInfo for the directory your testcases are in, then you can use gnustep-tests --debug to debug any failing testcases. |
…to-lock-mutex Fix NSLock issue
The GNUstep Base test suite doesn't set the rpath to point to the built library. This means that you need to juggle
LD_LIBRARY_PATH
directives if you want to run the tests against the just-build -base, without having to install it.The text was updated successfully, but these errors were encountered: