Now that we have recipe-specific-sysroots we don't need to exclude recipes from
world builds because they conflict with other recipes, as they'll all be built
with their own sysroots.
(From OE-Core rev: b2f3ac4d994a1921791f6bd0cdb3591586733694)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
(From OE-Core rev: 77fb72c76c8a5b2229a32f36a913a3293e9d2b56)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
(From OE-Core rev: 0cff8ae54066b25ffbe1efaa3f0a1d84aa89ebe1)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
(From OE-Core rev: 625be3dd6e3069333a3c94ca8f23129b23e4425b)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
(From OE-Core rev: 020ef81aa072c79f427111e5057d29ded849c48c)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
(From OE-Core rev: 385d26b7f0aeb6085bd7d96332b760057bd24537)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
(From OE-Core rev: 320f03b8492e5259c45e7c59b62571d5a827ee59)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is a minor release, announced in March 5th, 2018, which includes
following changes:
,----
| Andrey Grodzovsky (1):
| amdgpu: Fix mistake in initial hole size calculation.
|
| Christian König (3):
| amdgpu: mostly revert "use the high VA range if possible v2"
| amdgpu: add AMDGPU_VA_RANGE_HIGH
| amdgpu: fix "add AMDGPU_VA_RANGE_HIGH"
|
| Chunming Zhou (1):
| test/amdgpu: disable bo eviction test by default
|
| Eric Engestrom (1):
| meson: add configuration summary
|
| Heiko Becker (1):
| *-symbol-check: Don't hard-code nm executable
|
| Igor Gnatenko (1):
| meson: do not use cairo/valgrind if disabled
|
| Jonathan Gray (1):
| meson/configure.ac: pthread-stubs not present on OpenBSD
|
| Marek Olšák (2):
| meson: bump the version number
| RELEASING: mention meson
|
| Michel Dänzer (1):
| tests/amdgpu: Fix misspellings of "suite"
|
| Rob Clark (2):
| freedreno: add interface to get buffer address
| bump version for release
|
| Rob Herring (4):
| android: revert making handle magic and version members const
| android: fix mis-named alloc_handle_t
| android: add helper to convert buffer_handle_t to gralloc_handle_t ptr
| android: fix gralloc_handle_create() problems
|
| Thierry Reding (2):
| drm/fourcc: Fix fourcc_mod_code() definition
| drm/tegra: Sanitize format modifiers
`----
(From OE-Core rev: eef14164fb663d722234dbaf98611cf7ff0043d9)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
(From OE-Core rev: 453a433768bff76e4d3ad9bf40fd9d8210b0950e)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
(From OE-Core rev: a9f9ca73840d1e6911e496a32ee862a724615b50)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The patch tool will apply patches by default with "fuzz", which is where if the
hunk context isn't present but what is there is close enough, it will force the
patch in.
Whilst this is useful when there's just whitespace changes, when applied to
source it is possible for a patch applied with fuzz to produce broken code which
still compiles (see #10450). This is obviously bad.
We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For
that to be realistic the existing patches with fuzz need to be rebased and
reviewed.
(From OE-Core rev: 4a3d8806d25e146be40eaf640bc6da8bdd1b6e05)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some implementations of GBM, like the one included with
libMali, do not have gbm_bo_map() nor gbm_bo_unmap().
This patch enables kmscube to work with those implementations
even if it doesn't work as great.
(From OE-Core rev: 54615151da5e8c77c803947ce5760d06c1691c58)
Signed-off-by: Daniel Díaz <daniel.diaz@linaro.org>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Because I didn't really want python3-native to be at the bottom of the
entire X11 stack this recipe jumps through a small hoop to use the host
Python to run some modules it installs into the sysroot.
The Makefile compiles the Python module, which is good as the cache file
is recorded in the sstate manifest so when the package is removed from the
sysroot all of it is removed.
However in an enviroment where the sstate is shared between multiple hosts
it is possible that a different Python is used and this will generate a
new cache when the code is executed, which is not recorded in the manifest.
Eventually you'll end up with ownerless cache files in a sysroot which
conflict with the same file coming from a sstate upgrade.
Solve this with a SSTATE_INST_POSTRM which is ran when sstate is removed
to ensure that there are no Python cache files left behind.
[ YOCTO #11809 ]
(From OE-Core rev: 6f6a2b5ff7ec23bd3782f0c3521f3576101cbc9d)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Build date ends up embbedded in binary images, breaking reproducibility
of jpeg-tools and libturbojpeg. To enable reproducible builds, build date can be
specified during configuration, via "--with_build_date=<date>".
If SOURCE_DATE_EPOCH is specified we configure libjpeg-turbo with this value as
build date. Although the build date is a generic string, we keep it in the same
format YYYYMMDD.
[YOCTO #12526]
(From OE-Core rev: 46a39fe9fa2bc8f58ec822434b9ace9ab5572c82)
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
dlvsym() is used by the libepoxy test suite, but this is glibc-specific and
isn't present in musl.
Instead of adding an option to control whether dlvsym is available (which could
be detected by Meson), as we don't install the test suite simply add an option
to disable the entire test suite (and submit the patch upstream).
Also remove the build dependency on util-macros as that is a remnant of the
autotools build.
(From OE-Core rev: 80cee6088fa60eb5197f8ed9d135986b8e7d471a)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libepoxy 1.4.3 did not compile successfully because of
implicit symbol definitions and link-time errors.
Patch to disable 'dlvsym' has also been forward-ported
to be applicable to version 1.5.0.
The patch 'Add-fallback-definition-for-EGL-CAST.patch' is
mainline now; thus it can be safely removed.
Also, the patch
0001-Define-MESA_EGL_NO_X11_HEADERS-before-including-eglp.patch
is no longer required since mainline fixed this too.
(From OE-Core rev: b72154eccfbcc178a2c09c7c7d4cd0264d4cf0f6)
Signed-off-by: Francesco Giancane <francescogiancane8@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Major changes:
* Refine gtest conformance cases
* vp9enc: add support low power mode
* vavpp: add support for RGBA/RGBX surface
* vainfo: add support new profile/entrypoint pairs
(From OE-Core rev: a289787a80099d5029daab84625453cd3e2471b1)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Major changes:
* Bump VA-API version to 1.1.0
* Add API for multi-frame processing
* Add entrypoint VAEntrypointStats for Statistics
* Add data structures for HEVC FEI support
* Add new attributes for decoding/encoding/video processing
* Add new VPP filter for Total Color Correction
* Add blending interface in VPP
* Add rotation interface in VPP
* Add mirroring interface in VPP
* Add Chroma siting flags in VPP
* Add new color standard definitions
* Add new interface for exporting surface
* Add message callbacks for drivers to use
(From OE-Core rev: f8c01917594892be366580873618fa20272d2423)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Remove the do_install_append to create the Python 2 pyc files, as nothing in the
build is using Python 2 anymore (libxcb is the only user, and that uses Python
3).
Also use variables instead of a patch to control what Python binary and path the
modules are installed to.
(From OE-Core rev: c27c60fe012bf42ea3b22fc1b4496450dc68b50b)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
No need to inherit pkgconfig as configure doesn't use it, remove commented
DEPENDS which clearly came from another recipe, stop deploying an empty PN.
(From OE-Core rev: 1ae5ede208c82733293492a6eb836ff8b1197f4e)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The 2.4.90 was announced in Feb 17th 2018 and had following changes
are listed:
,----
| Andrey Grodzovsky (2):
| amdgpu: Update deadlock test to not assert on ECANCELED
| amdgpu: Fix segfault in deadlock test.
|
| Anuj Phogat (1):
| intel: Add more Coffeelake PCI IDs
|
| Bas Nieuwenhuizen (1):
| drm: Fix 32-bit drmSyncobjWait.
|
| Christian König (5):
| amdgpu: fix 32bit VA manager max address
| headers: sync up amdgpu_drm.h with drm-next
| amdgpu: use the high VA range if possible v2
| test/amdgpu: fix compiler warnings
| amdgpu: fix high VA mask
|
| Christoph Haag (1):
| meson: fix the install path of amdgpu.ids
|
| Chunming Zhou (5):
| fix return value for syncobj wait
| amdgpu: fix inefficient vamgr algorithm
| amdgpu: clean up non list code path for vamgr
| tests/amdgpu: add bo eviction test
| amdgpu: clean up non list code path for
| vamgr v2
|
| Dylan Baker (7):
| Add meson build system
| autotools: Include meson.build files in tarball
| README: Add note about meson
| meson: set proper pkg-config version for
| libdrm_freedreno
| meson: set the minimum version correctly
| meson: fix libdrm_nouveau pkgconfig include directories
| meson: include headers in root directory in ext_libdrm
|
| Emil Velikov (1):
| tests/amdgpu: add missing config.h include
|
| Eric Engestrom (25):
| remove unnecessary double-semicolon
| tests/amdgpu: add parentheses to make operation priority explicit
| tests/amdgpu: drop unused variables
| tests/util: fix signed/unsigned comparisons
| tests/util: drop unused parameters
| tests/etnaviv: drop unused `return 0`
| meson: add missing HAVE_RADEON
| configure: remove unused HAVE_CUNIT define
| configure: remove unused HAVE_INSTALL_TESTS define
| meson,configure: remove unused HAVE_OMAP define
| meson,configure: remove unused HAVE_TEGRA define
| meson,configure: remove unused HAVE_FREEDRENO define
| meson,configure: remove unused HAVE_ETNAVIV define
| meson,configure: always define HAVE_{INTEL,VMWGFX,NOUVEAU,EXYNOS,VC4,RADEON}
| always define HAVE_FREEDRENO_KGSL
| always define HAVE_CAIRO
| always define HAVE_VALGRIND
| meson: sort HAVE_* defines
| xf86atomic: fix -Wundef warning
| meson: cleanup whitespace
| meson,configure: add warning when using undefined preprocessor tokens
| xf86drmHash: remove always-false #if guards
| configure: always define HAVE_LIBDRM_ATOMIC_PRIMITIVES and HAVE_LIB_ATOMIC_OPS
| exynos/tests: use #ifdef for never-defined token
| meson,configure: turn undefined preprocessor tokens warnings into errors
|
| Hawking Zhang (3):
| tests/amdgpu: execute write linear on all the available rings
| tests/amdgpu: execute const fill on all the available rings
| tests/amdgpu: execute copy linear on all the available rings
|
| Marek Olšák (2):
| amdgpu: add amdgpu_query_sw_info for querying high bits of 32-bit address space
| configure.ac: bump version to 2.4.90
|
| Michel Dänzer (7):
| amdgpu: Don't print error message if parse_one_line returned -EAGAIN
| amdgpu: Don't dereference device_handle after
| amdgpu_device_deinitialize
| amdgpu: Symlink .editorconfig to tests/amdgpu
| amdgpu: Disable deadlock test suite by default for SI ASICs
| amdgpu: Disable VM test suite by default for SI ASICs
| Revert "amdgpu: clean up non list code path for vamgr"
| amdgpu: Add amdgpu_query_sw_info to amdgpu-symbol-check
|
| Rob Clark (1):
| freedreno: clamp priority based on # of rings
|
| Robert Foss (5):
| android: Move gralloc handle struct to libdrm
| android: Add version variable to gralloc_handle_t
| android: Mark gralloc_handle_t magic variable as const
| android: Remove member name from gralloc_handle_t
| android: Change gralloc_handle_t members to be fixed width
|
| Seung-Woo Kim (2):
| amdgpu: fix not to add amdgpu.ids when building without amdgpu
| modetest: Fix to check return value of asprintf()
`----
(From OE-Core rev: d4a16bab687cc27473ec22e727f23bb4106322a3)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The 1.9.4 fixes a number of issues in the Go compiler and is important
to get in before we start working on 1.10 inclusion.
- go1.9.1 (released 2017/10/04) includes two security fixes.
- go1.9.2 (released 2017/10/25) includes fixes to the compiler,
linker, runtime, documentation, go command, and the crypto/x509,
database/sql, log, and net/smtp packages. It includes a fix to a
bug introduced in Go 1.9.1 that broke go get of non-Git
repositories under certain conditions.
- go1.9.3 (released 2018/01/22) includes fixes to the compiler,
runtime, and the database/sql, math/big, net/http, and net/url
packages.
- go1.9.4 (released 2018/02/07) includes a security fix to “go get”.
(From OE-Core rev: 150d9d3215bf5d3a21c3f141d4ce837557c5f9f1)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This helps in compiling on graphics drivers which use
this define to differentiate between eglfs and x11 headers
e.g. mali or mesa
(From OE-Core rev: 2638482c3b2a5766d2a1377a589245664140e270)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the case of fontconfig, version x.x.9x are release candidates
for next version.
(From OE-Core rev: 6e14211b9dba6703aedf0a79100070430a47549c)
Signed-off-by: Maxin B. John <maxin.john@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This helps when libepoxy is compiled with egl but glx is disabled
it also depends on GL implementation provided eglplatform.h to be
using MESA_EGL_NO_X11_HEADERS to exclude X11 headers, e.g. mesa,
mali-userland implementations use this define to exclude x11
headers
(From OE-Core rev: 2655f7d26847424ac207e6e468a78a4ad293c4e9)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Major changes:
* Add option '--device <device>' to vainfo
* Add vp9enc for VP9 encoding
* Add vavpp for video processing
* Add FEI gtest cases
* Fix segmentation fault in putsurface_wayland
* Fix GCC 7.1.1 warnings/errors
* Fix libva version printed out by vainfo
Updated recipe to point to release tarball instead of git. Also, updated
github URLs to point to renamed Intel repository.
(From OE-Core rev: f355e40c84de55a7f71165873dbe7ef1ea870b83)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libva 2.0 bumps the VA-API version to 1.0.0 and deletes egl and
tpi backends. The header files va_egl.h and va_tpi.h are still
packaged in -dev to ensure packages that still use them don't fail.
Major changes:
* Bump VA-API version to 1.0.0
* Add new API for H264 FEI support
* Add definition of VA_FOURCC_I420
* Add functions for converting common enums to strings
* Deprecate H.264 baseline profile and FMO support
* Deprecate packed misc packed header flag
* Delete libva-tpi and libva-egl backends
* Refine VASliceParameterBufferHEVC, VAEncMiscParameterBuffer
* Fix errors in VAConfigAttribValEncROI, VAEncMacroblockParameterBufferH264
* Fix race condition in wayland support
* Rename vaMessageCallback to VAMessageCallback
* Make logging callbacks library-safe
Updated recipe to point to release tarball instead of git. Also, updated the
github URLs to point to renamed Intel repository.
(From OE-Core rev: 6c4c321bdd6b34def6b77e1d6a0bed03779254cd)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Use relative path to generate .pyc files could remove build host
references which leads to non-reproducible builds.
(From OE-Core rev: 230890227304e27acd074a3c748812d7a603d511)
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We need to ensure that all xorg modules are linked with
SECURITY_X_LDFLAGS to ensure that they will be able to resolve their run
time dependencies. The approach of listing each driver in
security_flags.inc lets less frequently used drivers be run-time
broken. Move the flag logic into xorg-driver-common.inc so that all
xorg modules from all layers will have the correct security flags used.
Cc: Khem Raj <raj.khem@gmail.com>
(From OE-Core rev: 27fce6ec277788f8fad0c9799e784df80f791120)
Signed-off-by: Tom Rini <trini@konsulko.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These functions were moved to meta/lib/oe in 2010 and the base_* functions in
utils.bbclass were intended to be a short-term compatibility layer. They're
still used in a few places, so update the callers to use the new functions.
(From OE-Core rev: c97acbd034532895ce57c6717ed1b3ccc7900b0d)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With glibc 2.27 memfd_create() is behind a _GNU_SOURCE guard, so use
AC_USE_SYSTEM_EXTENSIONS to define it.
(From OE-Core rev: 88b3d730021107985ea749c92e52a323690f87dc)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2.8.1 -> 2.9
Change in LIC_FILES_CHKSUM is due to change of URL www.freetype.org
from http to https.
(From OE-Core rev: 5545685f0d27d1b7ed840ebf695544d2562c7c0e)
Signed-off-by: Maxin B. John <maxin.john@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Cherry-pick fix from mesa upstream:
23ce168048 link mesautil with pthreads
link mesautil with pthreads to avoid:
../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function `u_thread_setname':
/builddir/build/BUILD/mesa-17.3.1/src/util/../../src/util/u_thread.h:66: undefined reference to `pthread_setname_np'
../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function `thrd_join':
/builddir/build/BUILD/mesa-17.3.1/src/util/../../include/c11/threads_posix.h:336: undefined reference to `pthread_join'
../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function `u_thread_create':
/builddir/build/BUILD/mesa-17.3.1/src/util/../../src/util/u_thread.h:48: undefined reference to `pthread_sigmask'
../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function `thrd_create':
/builddir/build/BUILD/mesa-17.3.1/src/util/../../include/c11/threads_posix.h:296: undefined reference to `pthread_create'
../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function `u_thread_create':
/builddir/build/BUILD/mesa-17.3.1/src/util/../../src/util/u_thread.h:50: undefined reference to `pthread_sigmask'
/builddir/build/BUILD/mesa-17.3.1/src/util/../../src/util/u_thread.h:50: undefined reference to `pthread_sigmask'
../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function `call_once':
/builddir/build/BUILD/mesa-17.3.1/src/util/../../include/c11/threads_posix.h:96: undefined reference to `pthread_once'
../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function `u_thread_get_time_nano':
/builddir/build/BUILD/mesa-17.3.1/src/util/../../src/util/u_thread.h:84: undefined reference to `pthread_getcpuclockid'
collect2: error: ld returned 1 exit status
(From OE-Core rev: f878741d22fbd1582039738c21cf86942fb94327)
Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The new name is much more consistent with what this actually means. We put
the pieces in place to rename everything a while back but looks like we
forgot to actually do it! Fix that now.
(From OE-Core rev: af9612f5d6b848fceea22d10ee964437299be776)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Sort the output to ensure reproducibility.
Fixes [YOCTO #12479]
(From OE-Core rev: 287446f5c0f3108efc0429bf84be45413970b7a8)
Signed-off-by: Maxin B. John <maxin.john@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The 2.4.89 version has been released in Dec 18, 2017, and has a great
set of features and improvements, as seen in the announcement summary:
,----
| libdrm release with leasing and syncobj api updates,
| updated amdgpu marketing ids, amdgpu tests,
| updated uapi headers
| etnaviv updates.
`----
The full announcement can be seen at:
https://lists.freedesktop.org/archives/dri-devel/2017-December/160530.html
(From OE-Core rev: a776a8190d5abee97da8684d4c448e3ed7bb7fb8)
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
