RSS/Atom feed Twitter
Site is read-only, email is disabled

Fwd: build problem related to libtool?

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

3 of 4 messages available
Toggle history

Please log in to manage your subscriptions.

Fwd: build problem related to libtool? Axel Wernicke 19 Feb 13:18
  Fwd: build problem related to libtool? Sven Neumann 19 Feb 17:54
   Fwd: build problem related to libtool? Axel Wernicke 23 Feb 23:04
43F84DB1.9060501@pogma.com 07 Oct 20:24
Axel Wernicke
2006-02-19 13:18:47 UTC (almost 19 years ago)

Fwd: build problem related to libtool?

Hi list,

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
Datum: 19. Februar 2006 11:51:29 MEZ An: Axel Wernicke
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:

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

hope that helps!

I'd really like to see GIMP running on OS X in the dev version.

Greetings, lexA ---
Live is like a chocolate box, you never know what you wanna get... GPG Signatur auf http://wernicke-online.net/Impressum/ prüfen

Sven Neumann
2006-02-19 17:54:24 UTC (almost 19 years ago)

Fwd: build problem related to libtool?

Hi,

Axel Wernicke writes:

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:

Such information absolutely needs to go to the bug-tracker or it will most likely be forgotten. However this looks very similar to bug #331677 so you may not have to open a new bug-report for it.

Sven

Axel Wernicke
2006-02-23 23:04:41 UTC (almost 19 years ago)

Fwd: build problem related to libtool?

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

Hi,

for some strange reason I didn't get your message through the list but had to find it more by accident on the NG...

Sven Neumann wrote:

Hi,

Axel Wernicke writes:

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:

Such information absolutely needs to go to the bug-tracker or it will most likely be forgotten. However this looks very similar to bug #331677 so you may not have to open a new bug-report for it.

Sven

filed the bug then.

lexA
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD/jF4R9mXLVsAbiQRAm9ZAKDNnpsxTTrVbvFPRu2uZD8N7ZdaBgCfc9Vt temhkxin8+CmI1rKeN/Df6k=
=JYnO
-----END PGP SIGNATURE-----