From: Hans-Christian Egtvedt <hcegtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] staging_dir/usr/lib vs staging_dir/lib
Date: Wed, 01 Aug 2007 07:59:56 +0200 [thread overview]
Message-ID: <1185947996.20419.8.camel@localhost.localdomain> (raw)
In-Reply-To: <07c301c7d3a1$ebb2fdc0$2600a8c0@engineering5>
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 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/.
> Where should those libs be? Are they being installed in the wrong
> directory or are they trying to remove them from the wrong directory?
Normal libs should (IMHO) be in /usr/lib.
> Can someone clarify this? Same thing happened when trying to build
> libpng as well when it was trying to cp libs over and it was copying
> from a directory where they were not installed.
I will have a look at libungif, libpng and fbv to see if anything is
wrong. IIRC fbv was my first try at adding a package to buildroot, it
could have used some reviewing.
--
With kind regards,
Hans-Christian Egtvedt
next prev parent reply other threads:[~2007-08-01 5:59 UTC|newest]
Thread overview: 5+ 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 [this message]
2007-08-01 7:48 ` [Buildroot] [PATCH] " Hans-Christian Egtvedt
2007-08-02 8:34 ` [Buildroot] " Bernhard Fischer
-- strict thread matches above, loose matches on Subject: below --
2007-08-02 13:37 Ulf Samuelsson
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=1185947996.20419.8.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