-
Notifications
You must be signed in to change notification settings - Fork 101
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
Package does not contain libs if local compilation has not been done #41
Comments
Yes, it should. Not sure I ever actually tested the contributed debian/ subdir. I think I did, but possibly not. If I did, I would have used 'debuild -rfakeroot' |
Hmm - I can't reproduce the failure you report: git clean -f -x -d drwxr-xr-x root/root 0 2015-12-18 00:26 ./ |
Can you try without running ./autogen.sh ? My understanding is that dpkg-buildpackage should be enough (and should run autogen), don't you agree ? |
I would not expect dpkg-buildpackage to run autogen.sh - that's normally a manual step that you only run when checking out from version control directly, and comes under different names. |
I agree, but then release tarballs should be made available (with the configure files generated with make dist), at least accordingly to http://stackoverflow.com/questions/31359171/git-buildpackage-doesnt-call-configure-why So there are 3 options
What do you think ? I think this is why the build process was failing (and that's why i added || true) : i was not running autogen before dpkg-buildpackage, so that's why the la failes were never generated and failed to delete. Maybe it would be better to revert my pull request (it's somewhat better to fail building the package rathe than building an empty one... even if no message indicates why it fails). |
Oh actually I have a fix for this in my pull request. :) |
After patching gst-rpicamsrc/debian/rules with || true so that the find|xargs doesn't fail, the following will produce an empty package:
The package didn't install the libs at all:
However, if i do:
This time, the package does contain the libs !
Shouldn't dpkg-buildpackage compile on it's own ?
The text was updated successfully, but these errors were encountered: