From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2017-02-09
Date: Fri, 10 Feb 2017 11:51:31 +0100 [thread overview]
Message-ID: <20170210115131.4894e96b@free-electrons.com> (raw)
In-Reply-To: <2a83fc74-f8c8-639f-74bc-d5032d270b2d@andin.de>
Hello,
On Fri, 10 Feb 2017 11:47:03 +0100, Andreas Naumann wrote:
> > But this raises an even more fundamental issue: there is *nothing* in
> > poppler that indicates it can depend on Qt5. There is some logic for
> > Qt4, but nothing for Qt5.
>
> Ok, I see that we have some local patch that makes this explicit. I
> guess in the given failure it must have been by chance that qt5 was
> built before poppler and popplers configure automatically detected this.
Exactly.
> > So: the dependency on Qt5 should be made explicit, and should take care
> > of the fact that Qt5 needs C++11 support, and therefore a reasonably
> > recent C++ compiler.
> >
> > Could you work on this?
> >
> > Alternatively, if you don't care/use Qt5 support in Poppler, you can
> > also just pass the appropriate --disable-<foo> option to
> > unconditionally disable Qt5 support.
>
> Quite the opposite. I'll try to come up with something in the afternoon.
Excellent, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-02-10 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170210072859.4656F20BAB@mail.free-electrons.com>
[not found] ` <CALdGskLbBc1Vx9Ju8ZhUJvRa5r6q83=N-qukFygmS-eZz79i8Q@mail.gmail.com>
[not found] ` <20170210093759.33285cd1@free-electrons.com>
[not found] ` <A9140E91EDA627489354A41A7EE118CA33CCBD@sv08ultra002.ultratronik.de>
2017-02-10 10:26 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2017-02-09 Thomas Petazzoni
2017-02-10 10:47 ` Andreas Naumann
2017-02-10 10:51 ` Thomas Petazzoni [this message]
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=20170210115131.4894e96b@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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.