All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Linux driver load failure with BR 2018.05
Date: Tue, 23 Oct 2018 09:03:50 +0200	[thread overview]
Message-ID: <874ldd4015.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <VI1PR0802MB222117E26BBCC677A6F52306EAF50@VI1PR0802MB2221.eurprd08.prod.outlook.com> (Fabrice Mousset's message of "Tue, 23 Oct 2018 06:34:39 +0000")

>>>>> "Fabrice" == Fabrice Mousset | GEOCEPT GmbH <fabrice.mousset@geocept.com> writes:

Hi,

 >> I would suggest you to use mainline kernel if you can.

 > Yes I know this is not an "up to date" Kernel Version, but it is the
 > used by the board manufacturer which we are using.
 > I have ported a Yocto/Poky BSP to BuildRoot, to not have to use
 > multiple build tools... and in my eyes, Yocto is too big and complex.

 > I have notice a strange something which looks strange to me in the kernel build command.
 > After the "make -j9" then is a HOSTCC="/usr/bin/gcc -02  -I/opt/crosstools/sitec-s4/include ..."

 > Why HOSTCC is using /usr/bin/gcc and not /opt/crosstools/sitec-s4/bin/arm-geocept-linux-gnueabihf-gcc ?

Because HOSTCC is the compiler used to build stuff for the host
machine.

The -I/opt/crosstools/sitec-s4/includes looks as if you have configured
the Host directory (BR2_HOST_DIR) to that location. This is normally
only done if you want to build toolchain once and then store it there
for later reuse (notice that we now have 'make sdk' to handle such
things instead).

When you do your normal build using that toolchain you should NOT set
BR2_HOST_DIR to that location.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-10-23  7:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22 13:46 [Buildroot] Linux driver load failure with BR 2018.05 Fabrice Mousset | GEOCEPT GmbH
2018-10-22 20:25 ` Fabio Estevam
2018-10-23  6:34   ` Fabrice Mousset | GEOCEPT GmbH
2018-10-23  7:03     ` Peter Korsgaard [this message]
2018-10-23  8:59       ` Fabrice Mousset | GEOCEPT GmbH
2018-10-22 22:43 ` Arnout Vandecappelle

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=874ldd4015.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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.