From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2017-02-26: librsvg failure
Date: Tue, 28 Feb 2017 15:48:08 +0100 [thread overview]
Message-ID: <87innujrrr.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170228100542.2536f1d0@free-electrons.com> (Thomas Petazzoni's message of "Tue, 28 Feb 2017 10:05:42 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Hello,
> On Tue, 28 Feb 2017 10:00:14 +0100, Peter Korsgaard wrote:
>> Is that the complete strace output? Where is fd 3 getting opened? I
>> would imagine the problem is caused by some kind of host/target
>> libraries mixup.
> No, that's only the end of the strace output. I've posted the full
> strace output at:
> http://code.bulix.org/elused-120071
> File descriptor 3 is:
> open("/lib/x86_64-linux-gnu/libm.so.6", O_RDONLY|O_CLOEXEC) = 3
> Which looks correct to me, when running a host binary on the host machine.
Yes, but the part where it loads a library from the target-librsvg
doesn't:
stat("/home/thomas/projets/buildroot/output/build/librsvg-2.40.16/gdk-pixbuf-loader", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat("/home/thomas/projets/buildroot/output/build/librsvg-2.40.16/gdk-pixbuf-loader/./libpixbufloader-svg.la", {st_mode=S_IFREG|0644, st_size=3987, ...}) = 0
open("/home/thomas/projets/buildroot/output/build/librsvg-2.40.16/gdk-pixbuf-loader/./libpixbufloader-svg.la", O_RDONLY) = 3
read(3, "# libpixbufloader-svg.la - a lib"..., 4000) = 3987
futex(0x7fb04bc20488, FUTEX_WAKE_PRIVATE, 2147483647) = 0
read(3, "", 4000) = 0
close(3) = 0
futex(0x7fb04b3480a8, FUTEX_WAKE_PRIVATE, 2147483647) = 0
open("/home/thomas/projets/buildroot/output/build/librsvg-2.40.16/gdk-pixbuf-loader/./.libs/libpixbufloader-svg.so", O_RDONLY|O_CLOEXEC) = 3
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-02-28 14:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 7:28 [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-26 Thomas Petazzoni
2017-02-27 13:28 ` [Buildroot] Analysis of build " Thomas Petazzoni
2017-02-27 15:54 ` Yann E. MORIN
2017-02-27 15:57 ` Thomas Petazzoni
2017-02-27 16:54 ` Frank Hunleth
2017-02-27 20:20 ` Thomas Petazzoni
2017-02-27 22:38 ` [Buildroot] Analysis of build results for 2017-02-26: libsidplay issue on PowerPC64 Thomas Petazzoni
2017-02-28 0:41 ` Sam Bobroff
2017-02-27 22:38 ` [Buildroot] Analysis of build results for 2017-02-26: classpath issue Thomas Petazzoni
2017-02-27 23:01 ` [Buildroot] Analysis of build results for 2017-02-26: librsvg failure Thomas Petazzoni
2017-02-28 9:00 ` Peter Korsgaard
2017-02-28 9:05 ` Thomas Petazzoni
2017-02-28 14:16 ` Thomas Petazzoni
2017-02-28 14:48 ` Peter Korsgaard [this message]
2017-02-28 15:37 ` Thomas Petazzoni
2017-02-28 16:10 ` Peter Korsgaard
2017-02-28 15:34 ` [Buildroot] Analysis of build results for 2017-02-26 Vlad Zakharov
2017-02-28 16:02 ` Thomas Petazzoni
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=87innujrrr.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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.