From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2018-09-14
Date: Sat, 6 Oct 2018 09:39:18 +0200 [thread overview]
Message-ID: <20181006093918.750d4197@windsurf> (raw)
In-Reply-To: <CAGrGpJDdVmD6PkhrZJgpTJut7vdvbxhS0m5Tg2DXPJZS90Vv6g@mail.gmail.com>
Hello,
On Fri, 5 Oct 2018 14:59:36 -0600, Peter Thompson wrote:
> Sorry I am so slow getting back. I was on holidays most of Sept.
No problem.
> This problem (AFAIK) is the Buildroot configure which is failing is trying
> to build both SDL and SDL2 which are two incompatible versions of the same
> thing.
> 881 BR2_PACKAGE_SDL=y
> 904 BR2_PACKAGE_SDL2=y
>
> What is being attempted to be configured and built here would never work
> (in my opinion).
>
> We could try to automate buildroot so only one or the other is selectable.
> It would mean adding "depends on !BR2_PACKAGE_SDL2" and "depends on
> !BR2_PACKAGE_SDL" to each of the packages Config.in.
I don't see any actual error in the autobuild report at
http://autobuild.buildroot.net/results/552817141d7eb0c5037114a4bc7d2d76de871285
that you're replying to.
Also, I believe SDL and SDL2 libraries have different names, so they
can co-exist in the same system. Hence, it doesn't seem like there is a
good reason to make them mutually exclusive.
Could you explain what in the autobuild report above makes you think it
is a SDL/SDL2 conflict ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next parent reply other threads:[~2018-10-06 7:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180915060039.533E3207D4@mail.bootlin.com>
[not found] ` <CAGrGpJDdVmD6PkhrZJgpTJut7vdvbxhS0m5Tg2DXPJZS90Vv6g@mail.gmail.com>
2018-10-06 7:39 ` Thomas Petazzoni [this message]
2018-10-06 22:26 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2018-09-14 Peter Thompson
[not found] <20180915060039.36CDD207B0@mail.bootlin.com>
[not found] ` <CALURroTZCjCkEw5-CjQDLju74tZqO2nkcPuT0KwG0UVq7YBEAA@mail.gmail.com>
2018-09-18 7:28 ` Thomas Petazzoni
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=20181006093918.750d4197@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 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.