Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] beaglebone_qt5 does not build since commit a7914499b80
Date: Sun, 13 Oct 2019 15:42:23 +0200	[thread overview]
Message-ID: <20191013154223.60ede697@windsurf> (raw)
In-Reply-To: <cbf93c1c-0a4a-79d4-6ebd-5d26f37d3c23@gmail.com>

On Sun, 13 Oct 2019 11:29:14 +0200
Romain Naour <romain.naour@gmail.com> wrote:

> There is an old patch [2] [3] in patchwork bumping the kernel (to 4.9) used in
> this defconfig but it's marked "Changes Requested" due to issues.
> 
> If we really want to keep this defconfig (as is), we have to use an external
> toolchain old enough to build the kernel and TI's modules.

The right way to fix this defconfig is certainly not to use an older
toolchain, but rather to use a more modern kernel. It's BeagleBone,
definitely not a legacy/ancient platform, it's still in widespread use,
there is quite certainly a kernel + SGX OpenGL stuff that is reasonably
recent ?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-10-13 13:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11  2:03 [Buildroot] beaglebone_qt5 does not build since commit a7914499b80 Carlos Santos
2019-10-11 16:21 ` Yegor Yefremov
2019-10-13  9:29 ` Romain Naour
2019-10-13 13:42   ` Thomas Petazzoni [this message]
2019-10-13 13:57     ` Romain Naour
2019-10-13 14:57       ` Carlos Santos
2019-10-15 21:30         ` Lothar Felten
2019-10-16  1:07           ` Carlos Santos
2019-10-31  1:30             ` Carlos Santos
2019-10-31  8:12               ` 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=20191013154223.60ede697@windsurf \
    --to=thomas.petazzoni@bootlin.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