From: Phil Blundell <pb@pbcl.net>
To: "Burton, Ross" <ross.burton@intel.com>,
Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: Koen Kooi <koen.kooi@linaro.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libbsd 0.8.3: BBCLASSEXTEND to native and nativesdk
Date: Sat, 05 Nov 2016 00:09:57 +0000 [thread overview]
Message-ID: <1478304597.3662.28.camel@pbcl.net> (raw)
In-Reply-To: <CAJTo0LZAGq8szm0vL0wyyR_rFVe1LBoMWYcoZh+VBMBcw5kW-Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
On Fri, 2016-11-04 at 23:24 +0000, Burton, Ross wrote:
> > No, I checked the files in /usr on the host, as this is a native
build it should be linking against the host libc.
>
> $ grep -r getrandom
> x86_64-linux-gnu/bits/syscall.h:#define SYS_getrandom __NR_getrandom
> x86_64-linux-gnu/bits/syscall.h:#define SYS_getrandom __NR_getrandom
> x86_64-linux-gnu/bits/syscall.h:#define SYS_getrandom __NR_getrandom
>
>
> Yes, looks like Debian headers are a bit broken.
>
>
>
That would happen if your glibc was compiled against a newer version of
the kernel headers than you actually have installed (bits/syscall.h is
auto-generated from the kernel headers at build time). If this is a
clean Debian install then it does sound like they have messed up the
packaging somehow.
p.
[-- Attachment #2: Type: text/html, Size: 1216 bytes --]
next prev parent reply other threads:[~2016-11-05 0:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 8:30 [PATCH] libbsd 0.8.3: BBCLASSEXTEND to native and nativesdk Koen Kooi
2016-10-20 11:05 ` Burton, Ross
2016-11-04 21:25 ` Nicolas Dechesne
2016-11-04 23:24 ` Burton, Ross
2016-11-04 23:47 ` Nicolas Dechesne
2016-11-05 0:09 ` Phil Blundell [this message]
2016-11-07 9:28 ` Burton, Ross
2016-11-07 9:30 ` Burton, Ross
2016-11-07 9:42 ` Nicolas Dechesne
2016-11-07 9:54 ` Burton, Ross
2016-11-05 0:04 ` Khem Raj
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=1478304597.3662.28.camel@pbcl.net \
--to=pb@pbcl.net \
--cc=koen.kooi@linaro.org \
--cc=nicolas.dechesne@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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