Hi, I use a Debian system to run autoreconf and bootstrap/make dist releases for various projects (e.g. reSIProcate)
When using the release tarball on a system like Fedora, issues with hard-coded rpath have been discovered. Apparently I am not alone, and this discussion has come up before in RPM packaging. On the RPM packaging request for reSIProcate, I've gathered links to a few different discussions about the issue: https://bugzilla.redhat.com/show_bug.cgi?id=892625#c11 One proposed solution appears to involve using sed to hack the configure script into shape. A more elegant solution appears to be re-running autoreconf during the rpmbuild (before the call to configure) Is there any other way to deal with this issue without any hacks? Am I potentially doing something wrong when I bootstrap the releases? Regards, Daniel
