From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] lib files
Date: Tue, 31 Jan 2012 17:22:42 +0100 [thread overview]
Message-ID: <20120131172242.3a84c018@skate> (raw)
In-Reply-To: <CAPeX=+vjLjg2vZL50NgSD-TozqDXtq8R3Anj=PNvCoCtTd0+EA@mail.gmail.com>
Le Tue, 31 Jan 2012 18:01:01 +0200,
Ozgun <ozgun.gunay@gmail.com> a ?crit :
> I built rootfs with opengl and QT without problem. (The compiled examples
> of QT also run in ubuntu without problem)
> But when I tried to run these qt examples in created rootfs, it gives "file
> not found" error. (I both tried these examples static and shared compiled.)
Can you show exactly how this error appears? If it appears when you try
to run the application, then it usually means that the kernel can't
find your dynamic library loader.
I never use Buildroot to generate a filesystem in which I'm chroot-ing.
If the target architecture is the same as the host, it should work, but
there might be issues, it's not the common use case for Buildroot
(usually, you take the generated root filesystem image and put it on a
target device).
> Then I cheked the dependency of application, you can see results below.
> The /usr/lib folder has the lib files but in a .a format.
> For example libm.a is exist but libm.so absent.
The shared versions of the C library and related libraries (libm, etc.)
are in /lib, not in /usr/lib.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-01-31 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 16:01 [Buildroot] lib files Ozgun
2012-01-31 16:22 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-01 7:58 Ozgun
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=20120131172242.3a84c018@skate \
--to=thomas.petazzoni@free-electrons.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