All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] checkarmreloc error for AArch64 (using vexpress_aemv8a_defconfig)
Date: Tue, 21 Jul 2015 09:01:18 +0200	[thread overview]
Message-ID: <20150721090118.7e191891@lilith> (raw)
In-Reply-To: <360A224CA5291F458103405CD90949369634AC04@ORSMSX105.amr.corp.intel.com>

Hello David J,

On Mon, 20 Jul 2015 22:17:49 +0000, Chou, David J
<david.j.chou@intel.com> wrote:
> Hello Albert,
> 
> You are right.  it seems the "file' program in my Ubuntu- 12.04.5 LTS system doesn't have the aarch64 database of signatures as you said. But If I moved the 64 bit u-boot I built in my Ubuntu- 12.04.5 LTS system to an Ubuntu14.04.02 LTS system, the "file u-boot" shows " u-boot: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), statically  linked, not stripped".
> 
> So, can I conclude the way I build aarch64 u-boot by following is correct?
> $ make distclean
> $ make vexpress_aemv8a_juno_defconfig   
> $ make all ARCH=arm CROSS_COMPILE=aarch64-linux-gnu-

This is one way of building U-Boot, indeed, which should amount to the
same as the "Building the Software" instructions given in the README
file.

> Thanks.
> 
> Best Regards,
> David Chou

Amicalement,
-- 
Albert.

  reply	other threads:[~2015-07-21  7:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17 22:13 [U-Boot] checkarmreloc error for AArch64 (using vexpress_aemv8a_defconfig) Chou, David J
2015-07-18  8:43 ` Albert ARIBAUD
2015-07-18  8:58   ` Albert ARIBAUD
2015-07-20  4:15   ` Chou, David J
2015-07-20 19:23     ` Albert ARIBAUD
2015-07-20 22:17       ` Chou, David J
2015-07-21  7:01         ` Albert ARIBAUD [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-02-26  9:41 Guillaume Gardet

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=20150721090118.7e191891@lilith \
    --to=albert.u.boot@aribaud.net \
    --cc=u-boot@lists.denx.de \
    /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.