Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 692244

Summary: x11-libs/libva-intel-media-driver-18.4.1 : cc1plus: error: -Werror= argument -Werror=implicit-function-declaration is not valid for C++ [-Werror]
Product: Gentoo Linux Reporter: Toralf Förster <toralf>
Component: Current packagesAssignee: Gentoo Media-video project <media-video>
Status: RESOLVED OBSOLETE    
Severity: normal CC: bugzilla, cjgibb, ivan, pascal.rebreyend, stoffepojken, whissi
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: emerge-info.txt
emerge-history.txt
environment
etc.portage.tbz2
logs.tbz2
temp.tbz2
x11-libs:libva-intel-media-driver-18.4.1:20190815-010144.log
patch for libva-intel-media-driver-18.4.1.ebuild

Description Toralf Förster gentoo-dev 2019-08-15 17:17:41 UTC
cc1plus: error: ‘-Werror=’ argument ‘-Werror=implicit-function-declaration’ is not valid for C++ [-Werror]
cc1plus: all warnings being treated as errors
make[2]: *** [media_driver/CMakeFiles/iHD_drv_video_OBJ.dir/build.make:63: media_driver/CMakeFiles/iHD_drv_video_OBJ.dir/agnostic/common/cm/cm_array.cpp.o] Error 1
make[2]: Leaving directory '/var/tmp/portage/x11-libs/libva-intel-media-driver-18.4.1/work/libva-intel-media-driver-18.4.1_build'

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.1_developer-abi32+64-20190810-161025

  -------------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-gnu-9.2.0 *

Available Python interpreters, in order of preference:
  [1]   python3.6
  [2]   python2.7 (fallback)
Available Ruby profiles:
  [1]   ruby24 (with Rubygems) *
Available Rust versions:
  [1]   rust-1.36.0 *
java-config:
The following VMs are available for generation-2:
*)	IcedTea JDK 3.12.0 [icedtea-bin-8]
Available Java Virtual Machines:
  [1]   icedtea-bin-8  system-vm

emerge -qpvO x11-libs/libva-intel-media-driver
[ebuild  N    ] x11-libs/libva-intel-media-driver-18.4.1
Comment 1 Toralf Förster gentoo-dev 2019-08-15 17:17:43 UTC
Created attachment 586930 [details]
emerge-info.txt
Comment 2 Toralf Förster gentoo-dev 2019-08-15 17:17:46 UTC
Created attachment 586932 [details]
emerge-history.txt
Comment 3 Toralf Förster gentoo-dev 2019-08-15 17:17:49 UTC
Created attachment 586934 [details]
environment
Comment 4 Toralf Förster gentoo-dev 2019-08-15 17:17:51 UTC
Created attachment 586936 [details]
etc.portage.tbz2
Comment 5 Toralf Förster gentoo-dev 2019-08-15 17:17:54 UTC
Created attachment 586938 [details]
logs.tbz2
Comment 6 Toralf Förster gentoo-dev 2019-08-15 17:17:57 UTC
Created attachment 586940 [details]
temp.tbz2
Comment 7 Toralf Förster gentoo-dev 2019-08-15 17:17:59 UTC
Created attachment 586942 [details]
x11-libs:libva-intel-media-driver-18.4.1:20190815-010144.log
Comment 8 Will Simoneau 2019-11-25 14:08:06 UTC
Created attachment 597480 [details, diff]
patch for libva-intel-media-driver-18.4.1.ebuild

The cmake files seem overly aggressive about setting -Werror* flags. This change does the trick for me.

Signed-off-by: Will Simoneau <bugzilla@hangar16.net>
Comment 9 MrPenguin07 2019-12-23 17:17:46 UTC
(In reply to Will Simoneau from comment #8)
> Created attachment 597480 [details, diff] [details, diff]
> patch for libva-intel-media-driver-18.4.1.ebuild
> 
> The cmake files seem overly aggressive about setting -Werror* flags. This
> change does the trick for me.
> 
> Signed-off-by: Will Simoneau <bugzilla@hangar16.net>

>>> Unpacking intel-media-18.4.1.tar.gz to /var/tmp/portage/x11-libs/libva-intel-media-driver-18.4.1/work
>>> Source unpacked in /var/tmp/portage/x11-libs/libva-intel-media-driver-18.4.1/work
>>> Preparing source in /var/tmp/portage/x11-libs/libva-intel-media-driver-18.4.1/work/media-driver-intel-media-18.4.1 ...
 * Applying builderror.patch ...
 *     /etc/portage/patches/x11-libs/libva-intel-media-driver-18.4.1/builderror.patch: patch failed to apply without a fuzz factor, please rebase
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/x11-libs/libva-intel-media-driver/libva-intel-media-driver-18.4.1.ebuild b/x11-libs/libva-intel-media-driver/libva-intel-media-driver-18.4.1.ebuild
|index e08e05733d2..d4592edaf68 100644
|--- a/x11-libs/libva-intel-media-driver/libva-intel-media-driver-18.4.1.ebuild
|+++ b/x11-libs/libva-intel-media-driver/libva-intel-media-driver-18.4.1.ebuild
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
Comment 10 Will Simoneau 2019-12-23 17:25:02 UTC
(In reply to Clint from comment #9)
> /etc/portage/patches/x11-libs/libva-intel-media-driver-18.4.1/builderror.
> patch: patch failed to apply without a fuzz factor, please rebase
> can't find file to patch at input line 5

My patch is against the ebuild itself, not libva-intel-media-driver. To use it locally, you need to apply it to a copy of the ebuild in a local overlay.
Comment 11 Pavel 2020-04-26 23:00:52 UTC
Upstream tracking

https://github.com/intel/media-driver/issues/712

https://github.com/shawnli2/media-driver/blob/0c3126c1f6e818aaa8e1b2269283aa71535593c7/media_driver/cmake/linux/media_compile_flags_linux.cmake

The patch is very simple, but I think we are 2 major versions behind the upstream.

19.0 and 20.0 had so many crash fixes that I don't think that waiting till libva 2.6 stabilises makes sense when you have daily crashes on new GPUs with 18.0.
Comment 12 Thomas Deutschmann (RETIRED) gentoo-dev 2020-05-18 19:35:46 UTC
I am closing this as obsolete. Please move to 20.1.1 which just appeared in repository and which should contain the fix.