Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Wrong pathnames in libtool and pkgconfig files
Date: Sun, 21 Jan 2007 11:43:50 +0100	[thread overview]
Message-ID: <20070121104350.GH23354@aon.at> (raw)
In-Reply-To: <20061002221905.GA10942@codepoet.org>

On Mon, Oct 02, 2006 at 04:19:05PM -0600, Erik Andersen wrote:
>On Mon Oct 02, 2006 at 05:18:03PM -0400, Andrew E. Mileski wrote:
>> I'm repeatedly having problems with pathnames in *.la and *.pc files,
>> since packages are built for / but installed in $(STAGING_DIR).  This
>> breaks packages that rely on these files being accurate.
>> 
>> So far I've resorted to sed'in them, which mostly works:
>>     sed -i filename -e 's#/usr#$(STAGING_DIR)/usr#g'
>> but is sure to cause problems if not prevented from being repeated.
>> 
>> This effects all packages built using libtool and pkgconfig.
>> 
>> Is there a more correct way to handle this?
>
>Ugh.  I'd never considered this, but yeah you are right.  I do
>not know of any way to teach libtool about a cross compiling
>setup, so unless someone else has a better idea I think your
>idea to use sed is the best thing we have going.

In the meantime Erik did fix those up, so if you experience trouble with
individual packages that still get this wrong, please let us know.

cheers,

      reply	other threads:[~2007-01-21 10:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-02 21:18 [Buildroot] Wrong pathnames in libtool and pkgconfig files Andrew E. Mileski
2006-10-02 22:19 ` Erik Andersen
2007-01-21 10:43   ` Bernhard Fischer [this message]

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=20070121104350.GH23354@aon.at \
    --to=rep.dot.nop@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox