Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] defconfig build issues
Date: Sun, 06 May 2018 08:34:52 +0200	[thread overview]
Message-ID: <87zi1dthpv.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180505215257.6745fc2f@windsurf> (Thomas Petazzoni's message of "Sat, 5 May 2018 21:52:57 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

Hi,

 > s6lx9_microboard_defconfig
 > ==========================

 > make[1]: *** No rule to make target 'simpleImage.'.  Stop.

 > https://gitlab.com/buildroot.org/buildroot/-/jobs/66561794

 > No idea about this one. I don't think it was failing before, and I
 > don't think this defconfig has been changed recently. Do we have a
 > regression in the Linux kernel build logic ?

Yes, looks like it. The make target it tries to call is
'simpleImage. lx9_mmu', E.G. a space has been added before the list of
dtbs. I've sent a patch fixing it.

 > raspberrypi3_qt5we_defconfig
 > ============================

 > Your Buildroot configuration needs a compiler capable of building 32 bits binaries.
 > If you're running a Debian/Ubuntu distribution, install the g++-multilib package.
 > For other distributions, refer to their documentation.

 > https://gitlab.com/buildroot.org/buildroot/-/jobs/66561791

 > This defconfig includes WebKit, which wants a C++ multilib compiler on
 > the host, which isn't present in our Docker image used for the gitlab
 > CI builds. Should we add this to our Docker image ? Should we exclude
 > this defconfig from the gitlab CI testing ?

I would say yes, we want the defconfigs to be tested.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2018-05-06  6:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-05 19:52 [Buildroot] defconfig build issues Thomas Petazzoni
2018-05-05 22:59 ` Fabio Estevam
2018-05-06  6:34 ` Peter Korsgaard [this message]
2018-05-06 13:50   ` Martin Bark
2018-05-06 15:27     ` Arnout Vandecappelle
2018-05-06 19:22       ` 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=87zi1dthpv.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox