All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <hcegtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Libtool relinking problem
Date: Tue, 12 Feb 2008 07:11:53 +0100	[thread overview]
Message-ID: <1202796713.26099.5.camel@localhost> (raw)
In-Reply-To: <46a136670802111753w4b6a7fbar93030a13b101eb28@mail.gmail.com>

On Mon, 2008-02-11 at 20:53 -0500, John Voltz wrote:
> I'm wondering if anyone else has noticed problems when installing some
> libraries to the staging_dir, sometimes libtool will place a  random
> dependency reference as /usr/lib/xxx.la instead of
> $(STAGING_DIR)/usr/lib/xxx.la.
> 

Unsure why some libraries fail to install with correct path while others
manage to do $(DESTDIR)/$(PREFIX)/lib/libxxx.la.

I usually add a $(SED) to the Buildroot Makefile to correct the
libxxx.la file.

$(SED) "s,^libdir=.*,libdir=\'$(STAGING_DIR)/usr/lib\',g" $(STAGING_DIR)/usr/lib/libxxx.la

> This appears to be caused by the libtool re-linking during install.
> Anybody know what to do to fix this? I tried adding
> LDFLAGS="-L$(STAGING_DIR)/usr/lib" to make install, but it didn't
> help.
> 

Fiddling with LDFLAGS, CFLAGS, etc to solve an issue is seldom the right
solution.

-- 
With kind regards,
Hans-Christian Egtvedt, Applications Engineer

  parent reply	other threads:[~2008-02-12  6:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12  1:53 [Buildroot] Libtool relinking problem John Voltz
2008-02-12  2:12 ` Dan Nicolaescu
2008-02-12  6:11 ` Hans-Christian Egtvedt [this message]
2008-02-12 16:38   ` John Voltz

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=1202796713.26099.5.camel@localhost \
    --to=hcegtvedt@atmel.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.