After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 332377 - build problem on OS X
build problem on OS X
Status: RESOLVED DUPLICATE of bug 331677
Product: GIMP
Classification: Other
Component: General
2.3.x
Other All
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2006-02-23 21:58 UTC by Axel Wernicke
Modified: 2008-01-15 14:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
complete build logfile (977.80 KB, text/plain)
2006-02-23 22:01 UTC, Axel Wernicke
Details

Description Axel Wernicke 2006-02-23 21:58:19 UTC
Please describe the problem:
there is a problem with building GIMP on OS X since version 2.3.6 (2.3.5 still
worked well). At the first look it seemed to be related to libtool, so I had a
conversation with them. Peter gave me then some information that might help some
enlighted gimp dev to wipe the problem out:

Anfang der weitergeleiteten E-Mail:

Von: Peter O'Gorman <peter@pogma.com>
Datum: 19. Februar 2006 11:51:29 MEZ
An: Axel Wernicke <axel.wernicke@gmx.de>
Kopie: libtool@gnu.org
Betreff: Re: build problem related to libtool?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter O'Gorman wrote:
| Axel Wernicke wrote:
| | Hi list,
| |
| | while trying to build the latest development version of GIMP on OS X  I
| | got some errors. I tried to solve them with the gimp developers,  but
| | they told me that my problem is rather related to libtool then to  the
| | gimp itself. That is why I'd like to ask for your help.
| | The command that crashes the make is:

The problem is here:
<http://cvs.gnome.org/viewcvs/gimp/app/Makefile.am?r1=1.355&r2=1.356>

I think they want to check for gnu binutils to use -rpath $ORIGIN/../lib,
but I'm not sure. Right now they try to do this for OS != windows. Ick!

To make an app relocatable on Mac OS X, you have to do more work than this.
You need to link your libraries with an install_name (soname) of
@executable_path/../lib/libfoo.dylib, by far the easiest thing to do to make
apps relocatable is to build as normal with -Wl,-headerpad_max_install_names
~ in LDFLAGS, then you can fix things to have the @executable_path/ bit after
build using install_name_tool(1).

Not libtool's fault, sorry, now you've got to go back to the gimp developers.

Peter

btw. there is a complete build log at
http://wernicke-online.net/temp/gimp2.3.7_build.log

Steps to reproduce:
The problem can be reproduced by ./configure; make; on OS X 10.4

Actual results:
mkdir .libs
gcc -g -O2 -Wall -o .libs/gimp-2.3 -Wl,-rpath -Wl,\$ORIGIN/../lib app_procs.o
main.o batch.o errors.o sanity.o units.o  -L/opt/local/lib gui/libappgui.a
actions/libappactions.a dialogs/libappdialogs.a menus/libappmenus.a
display/libappdisplay.a tools/libapptools.a widgets/libappwidgets.a
pdb/libapppdb.a vectors/libappvectors.a plug-in/libappplug-in.a
core/libappcore.a paint/libapppaint.a xcf/libappxcf.a text/libapptext.a
file/libappfile.a config/libappconfig.a paint-funcs/libapppaint-funcs.a
composite/libappcomposite.a base/libappbase.a
../libgimpwidgets/.libs/libgimpwidgets-2.0.dylib
/opt/local/var/db/dports/build/_Users_axelwernicke/work/gimp-2.3.7/libgimpconfig/.libs/libgimpconfig-2.0.dylib
-L/usr/X11R6/lib ../libgimpmodule/.libs/libgimpmodule-2.0.dylib
../libgimpcolor/.libs/libgimpcolor-2.0.dylib
../libgimpthumb/.libs/libgimpthumb-2.0.dylib
../libgimpmath/.libs/libgimpmath-2.0.dylib
../libgimpconfig/.libs/libgimpconfig-2.0.dylib
/opt/local/var/db/dports/build/_Users_axelwernicke/work/gimp-2.3.7/libgimpbase/.libs/libgimpbase-2.0.dylib
/opt/local/var/db/dports/build/_Users_axelwernicke/work/gimp-2.3.7/libgimpcolor/.libs/libgimpcolor-2.0.dylib
/opt/local/var/db/dports/build/_Users_axelwernicke/work/gimp-2.3.7/libgimpmath/.libs/libgimpmath-2.0.dylib
../libgimpbase/.libs/libgimpbase-2.0.dylib ../regexrepl/libregex.a
/opt/local/lib/libgtk-x11-2.0.dylib /opt/local/lib/libgdk-x11-2.0.dylib
/opt/local/lib/libatk-1.0.dylib /opt/local/lib/libgdk_pixbuf-2.0.dylib
/opt/local/lib/libtiff.dylib /opt/local/lib/libjpeg.dylib
/opt/local/lib/libpangocairo-1.0.dylib /opt/local/lib/libcairo.dylib
/opt/local/lib/libXrender.dylib -lX11 -lpng12 /opt/local/lib/libart_lgpl_2.dylib
/opt/local/lib/libpangoft2-1.0.dylib /opt/local/lib/libpango-1.0.dylib -lm
/opt/local/lib/libgobject-2.0.dylib /opt/local/lib/libgmodule-2.0.dylib
/opt/local/lib/libfontconfig.dylib /opt/local/lib/libexpat.dylib
/opt/local/lib/libfreetype.dylib -lz /opt/local/lib/libgthread-2.0.dylib
/opt/local/lib/libglib-2.0.dylib /opt/local/lib/libintl.dylib
/opt/local/lib/libiconv.dylib -lc
/usr/bin/ld: unknown flag: -rpath
collect2: ld returned 1 exit status
make[3]: *** [gimp-2.3] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Expected results:


Does this happen every time?


Other information:
Comment 1 Axel Wernicke 2006-02-23 22:01:02 UTC
Created attachment 60023 [details]
complete build logfile
Comment 2 Manish Singh 2006-02-23 23:03:09 UTC

*** This bug has been marked as a duplicate of 331677 ***