All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferry Toth <ftoth@telfort.nl>
To: yocto@yoctoproject.org
Subject: Problems building U-Boot for x86_64
Date: Wed, 23 Aug 2017 06:41:35 +0000 (UTC)	[thread overview]
Message-ID: <onj82v$64m$1@blaine.gmane.org> (raw)

I am having trouble building a specific U-Boot version with Yocto. 
Outside of Yocto on 64 bit Ubuntu 17.04 with multilib it builds fine.

I am extending meta-intel-edison to build a 64 bit Poke Morty, with a 
vanilla 64-bit kernel (4.12). This is working quite well.

My host is x86_64, the target is core2 with tune=core-64.

Without 64bit tune I can build U-Boot fine. With 64bit it can not link, 
appearently because it needs lbgcc.a

I attempted to add multilib, but although that immediately exposed bugs 
in other recipes but actually adds libgcc.a, it does that for the target 
sysroot only.

And for some reason, U-Boot is built with the native gcc (x86_64-linux), 
and multilib does not add libgcc.a to that sysroot.

So, how do I add multilib to -native sysroot, preferably only to -native 
and not to the target, as the target has not further use for it?

Strangest thing is in u-boot.inc there is: 
EXTRA_OEMAKE = 'CROSS_COMPILE=${TARGET_PREFIX} CC="${TARGET_PREFIX}gcc 
${TOOLCHAIN_OPTIONS}" V=1'
EXTRA_OEMAKE += 'HOSTCC="${BUILD_CC} ${BUILD_CFLAGS} ${BUILD_LDFLAGS}"'

But when I check my log file:
NOTE: make -j8 CROSS_COMPILE=x86_64-poky-linux- CC=x86_64-poky-linux-
gcc  ......

So TARGET_PREFIX resolves to x86_64-poky-linux, but I think my target is 
core2_64 (or something like that). Is that normal for U-Boot?

I am a little lost, so any help would be greatly appreciated!

Ferry 



             reply	other threads:[~2017-08-23  6:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23  6:41 Ferry Toth [this message]
2017-08-23 18:51 ` Problems building U-Boot for x86_64 Khem Raj
2017-08-23 20:11   ` Ferry Toth
2017-08-23 21:29     ` Ferry Toth
2017-08-23 21:51       ` Khem Raj
2017-08-23 22:40         ` Ferry Toth
2017-08-24  4:07           ` Khem Raj
2017-08-24  6:51             ` Ferry Toth
2017-08-24 10:40               ` Stefano Babic
2017-08-24 13:09                 ` Ferry Toth
2017-08-24 15:48                   ` Stefano Babic
2017-08-24 16:35                     ` Ferry Toth
2017-08-24 21:34                       ` Ferry Toth
2017-08-25  8:18                         ` Ferry Toth
2017-08-25 19:22             ` Ferry Toth
2017-08-25 22:30               ` Ferry Toth
2017-10-08 16:50                 ` Solved : " Ferry Toth
2017-11-30  8:03                   ` Stefan Roese
2018-01-27 21:45                     ` Ferry Toth

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='onj82v$64m$1@blaine.gmane.org' \
    --to=ftoth@telfort.nl \
    --cc=yocto@yoctoproject.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.