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
Firefox and shlib analysis #403
Comments
Scott Hetzel: This same issue with firefox was reported in this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=131237 And included a simple fix which was rejected by the firefox maintainer |
Unfortunately it seems to be a fairly common effect in some large projects. Other packages showing the same symptoms: thunderbird (yeah -- that one was predictable...) ... and that's just out of what's installed on my desktop: by no means comprehensive. As far as I can tell from a quick check, openjdk6 doesn't rely on setting LD_LIBRARY_PATH in the environment. |
this is a firefox problem not our it should use -Wl,-R,'$ORIGIN/.. as a ldflag at build time. see https://bugzilla.mozilla.org/show_bug.cgi?id=259945 |
On 13/12/2012 08:41, Baptiste Daroussin wrote:
Hmmm.... lots of discussion about Solaris there. Is there an official Also I need to look into the other examples which seem to be seeing a |
No need a policy, what is important is that LD_LIBRARY_PATH tweaks are tweaks and can lead to failures where -Wl,-R,'$ORIGIN is clean that is what is used in libreoffice |
On 15/12/2012 14:16, ajtiM wrote:
Thank you for the report. I'll add it to issue #403 at the pkgng github I'm slowly collecting examples of applications where the shlib analysis
Dr Matthew J Seaman MA, D.Phil. |
On 15/12/2012 18:23, Walter Hurry wrote:
Thanks. Added to the list. It always has to be the really big projects
Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey |
found' error messages as an aide to debugging.
found' error messages as an aide to debugging.
Here's a special case that needs to be handled properly:
$ORIGIN = installation directory of that shlib / elf binary |
Substitute dirname of the file being analysed for the special token $ORIGIN in RPATH. Change the declaration of action to match the new function prototype
Substitute dirname of the file being analysed for the special token $ORIGIN in RPATH. Change the declaration of action to match the new function prototype
library (indicated by the presence of a DT_SONAME tag) and not all the NEEDED resolve to files successfully. Shared libraries can legitimately use dynamic link information from the applications that link against them in order to resolve all their dependencies correctly.
library (indicated by the presence of a DT_SONAME tag) and not all the NEEDED resolve to files successfully. Shared libraries can legitimately use dynamic link information from the applications that link against them in order to resolve all their dependencies correctly.
activation status check. Confusion was possible because'-n' was already used extensively elsewhere on the command lines to mean 'dry-run', whereas '-N' is otherwise currently unused. Polish the wording in pkg.8 a little while here.
For the case of firefox, shlib analysis is working just fine now:
|
activation status check. Confusion was possible because'-n' was already used extensively elsewhere on the command lines to mean 'dry-run', whereas '-N' is otherwise currently unused. Polish the wording in pkg.8 a little while here.
Reported by Walter Hurry:
On 12/12/2012 23:17, Walter Hurry wrote:
Ah -- that would be a bug. At a guess, it's not finding the shlibs
because they're in a location not on the usual path and there's
something odd about the RPATH settings in the binaries. I shall
investigate further.
The text was updated successfully, but these errors were encountered: