public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: Gentoo-Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Gnome2 libtoolization
Date: 02 Jun 2002 22:41:52 +0200	[thread overview]
Message-ID: <1023050516.25244.84.camel@nosferatu.lan> (raw)
In-Reply-To: <20020601151835.549ec18a.spider@gentoo.org>

On Sat, 2002-06-01 at 15:18, Spider wrote:
> well,
>  as the moment of release prances forward I'm looking at the current
> state of ebuilds.
> 
>   right now we libtoolize a lot of gnome 2 except the core parts that is
> glib atk gtk+ and pango, simply because they break with libtoolize...
> fun isn't it?
> 
> Now, checking around a bit for libtoolize and asking some other gnome2
> packagers, I got this reference: 
> http://www.redhat.com/mailing-lists/rpm-list/msg07002.html
> 
> odd.. isn't it?
> 
> I vote for dropping libtoolize along with debug info in or around the
> 20th 
> 

Ok, this is a sticky problem.  The reason Redhat/Mandrake and
now we libtoolize many packages, is because with the default
libtool as used by most things have a bug, which I refer to
as the "relink" bug.  This is fixed by having a patched
version of libtool, and what libtoolize then basically do
is to install our patched version of libtool for the specific
package to user, thus fixing the bug.

A good example of the "relink" bug, is gdk-pixbuf.  If not
libtoolized, if build for the first time on a system, none
of the loaders in /usr/lib/gdk-pixbuf/loaders/ are installed.

Why this happens, are hard to explain, as I researched it
some time ago.  The basic principal, is that because we
build it with "--prefix=/usr", and then install into
"prefix=${D}/usr", libtool thinks it should relink some
of the components.  In the relinking, the "libdir" (defined
in the .la files) is defined as "/usr/lib...", and thus
the components/libraries do not get installed (if memory
serves).

Also, ${D} gets into .la files, and when the library of
that .la gets used, libtool tries to link in
${D}/usr/lib/libfoo.so instead of /usr/lib/libfoo.so like
it should.

This all is fixed in our version of libtool after much
research and testing.

Now what I propose, is that if we do not libtoolize Gnome2,
then we should at least write an eclass that patches all
"ltmain.sh" 's with the relink patch, and with our own
libtool-portage patch.

Anyhow, comments and suggestions appreciated.

NB: BCC me if you reply.


Greetings,

-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop Team Developer
Cape Town, South Africa




  reply	other threads:[~2002-06-02 20:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-01 13:18 [gentoo-dev] Gnome2 libtoolization Spider
2002-06-02 20:41 ` Martin Schlemmer [this message]
2002-06-02 22:17   ` Spider

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1023050516.25244.84.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox