GNOME Bugzilla – Bug 331677
Cannot link Gimp with Solaris linker
Last modified: 2008-01-15 14:05:45 UTC
Please describe the problem: Since app/Makefile.am contains few GNU ld option, Gimp cannot be build using solaris linker. Steps to reproduce: 1. bunzip2 -c gimp-2.3.7.tar.bz2 | tar xf - && cd gimp-2.3.7 2. ./configure 3. make Actual results: Gimp build ends with the following message: ld: fatal: file $ORIGIN/../lib: open failed: No such file or directory make[3]: *** [gimp-2.3] Error 1 make[3]: Leaving directory `/tmp/newgimp/gimp-2.3.7/app' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/newgimp/gimp-2.3.7/app' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/newgimp/gimp-2.3.7' make: *** [all] Error 2 Error while installing gimp Expected results: A fresh Gimp binary Does this happen every time? Yes. Other information: Backing out the following lines in app/Makefile allow the linker to do its job. I found out in CVS comments that it is related to relocation but I can't imagine what it is supposed to do (include a variable in an ELF library search path?) if OS_UNIX munix = -Wl,-rpath '-Wl,$$ORIGIN/../lib' endif
Created attachment 59646 [details] Complete output for the target in app
Since relocation only works on Linux, we should probably only use the extra linker flags if relocatibility has been explicitly requested.
2006-02-19 Manish Singh <yosh@gimp.org> * m4macros/binreloc.m4: introduce automake conditional USE_BINRELOC. * app/Makefile.am: ... and use the above here, so that -rpath is only specified when binreloc functionality is enabled. Fixes bug #331677.
*** Bug 332377 has been marked as a duplicate of this bug. ***