From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python-matplotlib: needs a toolchain with C++ support
Date: Fri, 02 Aug 2019 19:41:29 +0200 [thread overview]
Message-ID: <87ef23sbw6.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190802184610.3e9657aa@windsurf.home> (Thomas Petazzoni's message of "Fri, 2 Aug 2019 18:46:10 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> Hello,
> The commit title should start with package/python-matplotlib :-)
Ahh, indeed - Will fix.
> On Fri, 2 Aug 2019 18:22:26 +0200
> Peter Korsgaard <peter@korsgaard.com> wrote:
>> Matplotlib contains .cpp source code:
>>
>> ls src/*.cpp
>> src/_backend_agg.cpp
>> src/_backend_agg_wrapper.cpp
>> src/_contour.cpp
>> src/_contour_wrapper.cpp
>> src/ft2font.cpp
>> src/ft2font_wrapper.cpp
>> src/_image.cpp
>> src/_image_wrapper.cpp
>> src/mplutils.cpp
>> src/_path_wrapper.cpp
>> src/_png.cpp
>> src/py_converters.cpp
>> src/_tkagg.cpp
>> src/_ttconv.cpp
>> src/_windowing.cpp
>>
>> So add a dependency on C++ support in the toolchain to fix build errors like
>> (no autobuilder reference yet):
> Since when does it need C++ ? Was this package bumped recently ? If
> not, why don't we have autobuilder failures for this ?
Since always (the package only got added to next end of May). I'm not
sure why there isn't any autobuilder failures, possibly because we don't
test such combination of toolchain options? (wchar, threads, !static !c++)
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-08-02 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 16:22 [Buildroot] [PATCH] python-matplotlib: needs a toolchain with C++ support Peter Korsgaard
2019-08-02 16:46 ` Thomas Petazzoni
2019-08-02 17:41 ` Peter Korsgaard [this message]
2019-08-02 21:35 ` 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=87ef23sbw6.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