All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-networking][PATCH 4/6] waf-cross-answers: Add cross-answers-riscv64.txt
Date: Mon, 19 Mar 2018 20:59:58 -0700	[thread overview]
Message-ID: <20180320040000.29408-4-raj.khem@gmail.com> (raw)
In-Reply-To: <20180320040000.29408-1-raj.khem@gmail.com>

RISC-V is newly added to OE-Core, waf needs to know
about it during cross compile

Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
 .../waf-cross-answers/cross-answers-riscv64.txt    | 39 ++++++++++++++++++++++
 1 file changed, 39 insertions(+)
 create mode 100644 meta-networking/files/waf-cross-answers/cross-answers-riscv64.txt

diff --git a/meta-networking/files/waf-cross-answers/cross-answers-riscv64.txt b/meta-networking/files/waf-cross-answers/cross-answers-riscv64.txt
new file mode 100644
index 000000000..1023f6aff
--- /dev/null
+++ b/meta-networking/files/waf-cross-answers/cross-answers-riscv64.txt
@@ -0,0 +1,39 @@
+Checking uname sysname type: "Linux"
+Checking uname version type: "# Wed May 20 10:34:39 UTC 2015"
+Checking simple C program: "hello world"
+rpath library support: OK
+-Wl,--version-script support: OK
+Checking getconf LFS_CFLAGS: NO
+Checking correct behavior of strtoll: NO
+Checking for working strptime: OK
+Checking for C99 vsnprintf: "1"
+Checking for HAVE_SHARED_MMAP: OK
+Checking for HAVE_MREMAP: OK
+Checking for HAVE_SECURE_MKSTEMP: OK
+Checking for HAVE_IFACE_GETIFADDRS: NO
+Checking for HAVE_IFACE_IFCONF: NO
+Checking for HAVE_IFACE_IFREQ: NO
+Checking for large file support without additional flags: OK
+Checking for HAVE_INCOHERENT_MMAP: NO
+Checking value of NSIG: "65"
+Checking value of _NSIG: "65"
+Checking value of SIGRTMAX: "64"
+Checking value of SIGRTMIN: "34"
+Checking whether the WRFILE -keytab is supported: OK
+Checking for kernel change notify support: OK
+Checking for Linux kernel oplocks: OK
+Checking for kernel share modes: OK
+Checking whether POSIX capabilities are available: OK
+Checking if can we convert from CP850 to UCS-2LE: OK
+Checking if can we convert from UTF-8 to UCS-2LE: OK
+vfs_fileid checking for statfs() and struct statfs.f_fsid: OK
+Checking whether we can use Linux thread-specific credentials: OK
+Checking whether fcntl locking is available: OK
+Checking for the maximum value of the 'time_t' type: OK
+Checking whether the realpath function allows a NULL argument: OK
+Checking for ftruncate extend: OK
+getcwd takes a NULL argument: OK
+Checking for small off_t: NO
+Checking whether blkcnt_t is 32 bit: NO
+Checking whether blkcnt_t is 64 bit: OK
+Checking whether fcntl lock supports open file description locks: OK
-- 
2.16.2



  parent reply	other threads:[~2018-03-20  4:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20  3:59 [meta-networking][PATCH 1/6] ndisc6: gold does not work for risc-v here Khem Raj
2018-03-20  3:59 ` [meta-oe][PATCH 2/6] krb5: Add -D_REENTRANT -pthread to CFLAGS on risc-v Khem Raj
2018-03-20  3:59 ` [meta-oe][PATCH 3/6] krb5: Correctly specify configure option --with-crypto-impl Khem Raj
2018-03-20  3:59 ` Khem Raj [this message]
2018-03-20  3:59 ` [meta-oe][PATCH 5/6] libqb: Upgrade to 1.0.3 Khem Raj
2018-03-31  6:04   ` Martin Jansa
2018-06-13  7:08     ` Martin Jansa
2018-06-13 13:42       ` Khem Raj
2018-03-20  4:00 ` [meta-gnome][PATCH 6/6] libgnome-keyring, gnome-keyring: Add build dep on glib-2.0-native 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=20180320040000.29408-4-raj.khem@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.