Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <hcegtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] staging_dir/usr/lib vs staging_dir/lib
Date: Wed, 01 Aug 2007 09:48:35 +0200	[thread overview]
Message-ID: <1185954515.32541.15.camel@localhost.localdomain> (raw)
In-Reply-To: <1185947996.20419.8.camel@localhost.localdomain>

On Wed, 2007-08-01 at 07:59 +0200, Hans-Christian Egtvedt wrote:
> On Tue, 2007-07-31 at 13:38 -0500, Christopher Reder wrote:
> > It seems like there may be some confusion over what directories to use
> > when installing/hosting/storing libs.
> 
> Probably my bad (-:

I cleaned up libpng, libungif and fbv. Although my upstream snapshot is
some days old.

> > I just pulled down the latest and enabled fbv which selected libungif.
> > In doing so, it fails when it tries to remove libs from
> > staging_dir/lib because the libs are actually in
> > staging_dir/usr/lib.  
> 
> Weird, because staging_dir/usr is a symlink to staging_dir/.

Actually, removing libungif.la is not something that should have been
done when installing (I think, anybody know the reason?). I have
replaced it with a SED fixing the libdir in the included patch.

<snipp>

-- 
With kind regards,
Hans-Christian Egtvedt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: br2-clean-libpng-libungif-and-fbv.patch
Type: text/x-patch
Size: 3855 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20070801/5be1e4ce/attachment.bin 

  reply	other threads:[~2007-08-01  7:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31 18:38 [Buildroot] staging_dir/usr/lib vs staging_dir/lib Christopher Reder
2007-08-01  5:59 ` Hans-Christian Egtvedt
2007-08-01  7:48   ` Hans-Christian Egtvedt [this message]
2007-08-02  8:34   ` Bernhard Fischer

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=1185954515.32541.15.camel@localhost.localdomain \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox