From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Daily results for 2019-09-17
Date: Mon, 23 Sep 2019 21:02:29 +0200 [thread overview]
Message-ID: <20190923210229.0d90432a@gmx.net> (raw)
In-Reply-To: <d68e4895-611b-7a34-0d22-3bb5efbe8cce@mind.be>
Hello Arnout,
On Sat, 21 Sep 2019 13:26:00 +0200, Arnout Vandecappelle <arnout@mind.be> wrote:
> On 18/09/2019 22:56, Peter Seiderer wrote:
> > Hello,
> >
> > On Wed, 18 Sep 2019 06:16:20 -0000, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> >
> > [...]
> >>
> >> Results for branch 'master'
> >> ===========================
> > [...]
> >
> >> x86_64 | ffmpeg-4.2 | NOK | http://autobuild.buildroot.net/results/061fd3cd6e29c86f49ebfe47b4abb7497ee17fa5 |
> >
> > The ffmpeg configure step fails with:
> >
> > ERROR: gnutls not found using pkg-config
> >
> > From build/ffmpeg-4.2/ffbuild/config.log:
> >
> > .../host/bin/../x86_64-buildroot-linux-gnu/sysroot/usr/lib/libgnutls.so: undefined reference to `__get_cpuid_count'
> >
> > From build/gnutls-3.6.9/lib/accelerated/x86/x86-common.c:
> >
> > 41 #ifdef HAVE_CPUID_H
> > 42 # include <cpuid.h>
> > 43 #else
> > 44 # define __get_cpuid(...) 0
> > 45 # define __get_cpuid_count(...) 0
> > 46 #endif
> >
> > The given toolchain cpuid.h file is missing the get_cpuid_count definition (for
> > an cpuid.h file with it see e.g. [1])...
> >
> > The gnutls search for cpuid.h can be disabled by the
> > '--disable-hardware-acceleration' configure option, so the build could
> > be fixed by the following patch:
> >
> > --- a/package/gnutls/gnutls.mk
> > +++ b/package/gnutls/gnutls.mk
> > @@ -27,7 +27,8 @@ GNUTLS_CONF_OPTS = \
> > --with-librt-prefix=$(STAGING_DIR) \
> > --without-tpm \
> > $(if $(BR2_PACKAGE_GNUTLS_OPENSSL),--enable,--disable)-openssl-compatibility \
> > - $(if $(BR2_PACKAGE_GNUTLS_TOOLS),--enable-tools,--disable-tools)
> > + $(if $(BR2_PACKAGE_GNUTLS_TOOLS),--enable-tools,--disable-tools) \
> > + --disable-hardware-acceleration
> > GNUTLS_CONF_ENV = gl_cv_socket_ipv6=yes \
> > ac_cv_header_wchar_h=$(if $(BR2_USE_WCHAR),yes,no) \
> > gt_cv_c_wchar_t=$(if $(BR2_USE_WCHAR),yes,no) \
> >
> >
> > Unconditionally disabling hardware acceleration seems to be overkill, but
> > did not spot the right condition (yet)...
> >
> > Or alternatively patch configure to check not only for cpuid.h header,
> > but although check for __get_cpuid/__get_cpuid_count presence...
>
> Fixed by http://patchwork.ozlabs.org/patch/1157883/ I guess?
Yes, I can confirm the ffmpeg 'gnutls not found using pkg-config' failure
is fixed by the above patch (which is already applied on master)...
Regards,
Peter
>
> Regards,
> Arnout
>
> >
> > Regards,
> > Peter
> >
> > [1] https://github.com/gcc-mirror/gcc/blob/master/gcc/config/i386/cpuid.h
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot
> >
next prev parent reply other threads:[~2019-09-23 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 6:16 [Buildroot] [autobuild.buildroot.net] Daily results for 2019-09-17 Thomas Petazzoni
2019-09-18 20:56 ` Peter Seiderer
2019-09-21 11:26 ` Arnout Vandecappelle
2019-09-23 19:02 ` Peter Seiderer [this message]
2019-09-19 18:35 ` Peter Seiderer
2019-09-21 9:33 ` Arnout Vandecappelle
2019-09-19 19:35 ` Peter Seiderer
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=20190923210229.0d90432a@gmx.net \
--to=ps.report@gmx.net \
--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