From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] nspr and aarch64 build issue
Date: Mon, 18 Mar 2013 16:20:33 +0100 [thread overview]
Message-ID: <20130318162033.30fbd920@skate> (raw)
In-Reply-To: <CABtOAfxeHbNeKc8eWfxaTLPgOeh10HmF2psbXnvZh9mLF0hKTg@mail.gmail.com>
Dear Alexander Khryukin,
On Mon, 18 Mar 2013 01:53:38 +0400, Alexander Khryukin wrote:
> drbg.c: In function 'RNG_RandomUpdate':
> *drbg.c:516:5: error: size of array 'arg' is negative*
> make[4]: ***
> [Linux2.6_aarch64_glibc_PTH_OPT.OBJ/Linux_SINGLE_SHLIB/drbg.o] Error 1
> make[4]: Leaving directory
> `/home/user/buildroot/output/build/libnss-3.12.9/mozilla/security/nss/lib/freebl'
I sent a patch that should hopefully fix this. The BR2_ARCH_IS_64 was
not selected on the AArch64 architecture, so the following bit of code
in libnss.mk was not being triggered:
ifeq ($(BR2_ARCH_IS_64),y)
LIBNSS_BUILD_VARS += USE_64=1
endif
However, I am rather surprised, because here, the build of libnspr
(which is a dependency of libnss) doesn't work. I get:
In file included from ../../../dist/include/nspr/prtypes.h:26:0,
from ../../../dist/include/nspr/pratom.h:14,
from ../../../dist/include/nspr/nspr.h:9,
from ../../../pr/include/private/primpl.h:39,
from prfdcach.c:6:
../../../dist/include/nspr/prcpucfg.h:817:2: error: #error "Unknown CPU architecture"
Have you fixed this?
Thanks,
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:[~2013-03-18 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 21:53 [Buildroot] nspr and aarch64 build issue Alexander Khryukin
2013-03-18 10:40 ` Alexander Khryukin
2013-03-18 15:09 ` Thomas Petazzoni
2013-03-18 15:20 ` Thomas Petazzoni [this message]
2013-03-18 17:56 ` Alexander Khryukin
2013-03-18 18:58 ` Alexander Khryukin
2013-03-18 19:25 ` Peter Korsgaard
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=20130318162033.30fbd920@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 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.