Red Hat Bugzilla – Bug 253872
hardcoded rpath in emacs
Last modified: 2009-07-14 11:16:38 EDT
Description of problem: Please remove rpath from emacs binary. On x86_64 (and possibly other architectures) it has rpath /usr/lib64. http://fedoraproject.org/wiki/Packaging/Guidelines#head-7cea8c7aa96400a4687e843156354476434ff883 Version-Release number of selected component (if applicable): emacs-22.1-2.fc8 Steps to Reproduce: 1. objdump -x /usr/bin/emacs | grep RPATH Actual results: RPATH /usr/lib64 Expected results:
i386 builds correctly w/o RPATH. The root of the problem is in _AC_PATH_X_XMKMF in autoconf. The following code in the configure script sets $ac_x_libraries as '' on i386 and '/usr/lib64' on x86_64: # Screen out bogus values from the imake configuration. They are # bogus both because they are the default anyway, and because # using them would break gcc on systems where it needs fixed includes. case $ac_im_incroot in /usr/include) ac_x_includes= ;; *) test -f "$ac_im_incroot/X11/Xos.h" && ac_x_includes=$ac_im_incroot;; esac case $ac_im_usrlibdir in /usr/lib | /lib) ;; *) test -d "$ac_im_usrlibdir" && ac_x_libraries=$ac_im_usrlibdir ;; esac fi cd .. rm -f -r conftest.dir Later this code sets the RPATH linker switch: if test "${x_libraries}" != NONE; then if test -n "${x_libraries}"; then LD_SWITCH_X_SITE=-L`echo ${x_libraries} | sed -e "s/:/ -L/g"` LD_SWITCH_X_SITE_AUX=-R`echo ${x_libraries} | sed -e "s/:/ -R/g"` fi Adding /usr/lib64 to 'case $ac_im_usrlibdir in /usr/lib | /lib)' fixes the RPATH.
Created attachment 302963 [details] workaround to disable RPATH on x86_64
(In reply to comment #2) > Created an attachment (id=302963) [edit] > workaround to disable RPATH on x86_64 > I'm not sure this is the right approach. Really, it looks more like a bug in autoconf than emacs. Patching "configure" instead of "configure.in" means that the changes will get clobbered by a subsequent "autoconf". Chip
Yeah, fixing autoconf's definitely the ideal solution. 'autoreconf' and 'autoconf --force 'from autoconf-2.62 still produce a buggy configure script. 2.62 does fix the infinite loop in the 'mktime' check, though. I emailed the autoconf bug mailing list about the problem: http://lists.gnu.org/archive/html/bug-autoconf/2008-04/msg00061.html
Eric Blake wrote on the autoconf list (http://lists.gnu.org/archive/html/bug-autoconf/2008-04/msg00077.html): emacs won't benefit from the patch until it upgrades to using the as-yet-unreleased autoconf 2.63, so you will have to continue to carry an emacs-specific patch for some time I think the workaround (attachment (id=302963)) is good for now. Once the fix from autoconf finally trickles upstream to emacs it'll differ enough that the patch will fail and remind you to remove it.
Created attachment 304522 [details] Upstream workaround to disable RPATH on x86_64 On May 3 2008 Glenn Morris committed this patch on emacs HEAD but not the emacs 22.2 branch. The diff patchs against the emacs-22.2 tarball and fixes the configure output and variables.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Ping? We were informed [1] that Chip has given up ownership of this package. [1] https://www.redhat.com/archives/fedora-devel-list/2008-November/msg00214.html
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.