-
Notifications
You must be signed in to change notification settings - Fork 47
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
fixes for git, autotools and library lookup #52
Conversation
There are a set f generic ignore patterns, mostly generated by tools like editors, autotools and build tools. Separate these generic patterns from the project-specific ones. Also remove patterns with a path, if they are already covered by patterns without path (e.g. Makefile covers src/Makefile). Signed-off-by: Holger Dengler <dengler@linux.ibm.com>
Signed-off-by: Holger Dengler <dengler@linux.ibm.com>
Ignore patterns for files, which are created by the dist or distcheck targets. Signed-off-by: Holger Dengler <dengler@linux.ibm.com>
Add missing files to the distclean and maintainer-clean make targets. Signed-off-by: Holger Dengler <dengler@linux.ibm.com>
Failed the gcc build with this in the debug log: |
Ok, let me check that. On my local test machine, the dlopen() with the so-name works properly. |
Weird, the library load with only the so-name is workling properly on my debian unstable test env. I will now setup an ubuntu test system first, to check whats going wrong. I decided to drop the two last commits until I have fixed them. Sorry for the noise. |
Ok, do you want to just merge the current commits and defer the path issue to a different PR? |
I will create another PR for the soname stuff. You can merge this one as it is, if you're ok with the changes. |
Sure, I edited the PR description and dropped mention of the softoken path check from there given those patches have been retired. |
As I started to work with the project, I realized some missing git ignore patterns and files the base automake targets. This series contains some fixes for these issues.
I decided to split my changes into multiple commits, just to make it more clear, what I've changed. But I'm open to merge some of them, if you prefer it.