All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] B3+external kernel: not quite sure how to make these pieces fit ...
Date: Fri, 26 Jun 2015 01:06:10 +0200	[thread overview]
Message-ID: <558C8962.9080003@mind.be> (raw)
In-Reply-To: <07f701d0af37$5492bff0$fdb83fd0$@novadsp.com>

On 06/25/15 13:08, g4 at novadsp.com wrote:
> Arnout, apologies. Outlook simply replied to you and not the list.
> 
>>  Looks like your external toolchain is not installed correctly. Can 
>> you run
>> ~/rcn/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-
>> gnueabihf-gcc  -v
> 
> I will bow to superior knowledge here but it does produce a booting,
> running, kernel.

 I asked because the error you reported is based on this piece of code:

EXT_TOOLCHAIN_TARGET=`LANG=C $${__CROSS_CC} -v 2>&1 | grep ^Target | cut -f2 -d
' '` ; \
if ! echo $${EXT_TOOLCHAIN_TARGET} | grep -qE 'eabi(hf)?$$' ; then \
        echo "External toolchain uses the unsuported OABI" ; \
        exit 1 ; \
fi ; \

[snip]
> Target: arm-linux-gnueabihf

 ... but it does end in eabihf, so why doesn't this condition match?

 Could you modify toolchain/helpers.mk to echo the value of EXT_TOOLCHAIN_TARGET
in the command above?


[snip]
>>  Or to be safe, just select the Linaro 2014.09 toolchain as to be 
>> downloaded and installed.
> 
> Yes but working kernel trumps all ...

 It is not required to build the kernel with the same toolchain as userspace.


>>  You'll have to run 'make -C <linux_dir> INSTALL_MOD_PATH=$1 
>> modules_install'
>> from a post-build script. Or else, install the modules in some staging 
>> directory and copy them to the target directory in the post-build script.
>>
>>  Or alternatively, just build it in buildroot with 
>> BR2_LINUX_KERNEL_CUSTOM_LOCAL=y.
> 
> This last is promising. So you suggest cloning kernel repo in the buildroot
> tree? 

 No, I suggest letting buildroot build the kernel using the checked-out kernel
source code you have in another directory. _CUSTOM_LOCAL refers to a source tree.


 Regards,
 Arnout

> 
> Someone else must have had this problem? 
> 
> Thank you.
> 
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 
>  
>  
> ************************************************************************************
> This footnote confirms that this email message has been scanned by
> PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
> ************************************************************************************
> 
> 
> 
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

      reply	other threads:[~2015-06-25 23:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24 19:06 [Buildroot] B3+external kernel: not quite sure how to make these pieces fit g4 at novadsp.com
2015-06-24 21:05 ` Arnout Vandecappelle
2015-06-25 11:08   ` g4 at novadsp.com
2015-06-25 23:06     ` Arnout Vandecappelle [this message]

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=558C8962.9080003@mind.be \
    --to=arnout@mind.be \
    --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.