Paul Eggleton [Thu, 21 May 2015 12:16:34 +0000 (13:16 +0100)]
classes/buildhistory: ensure that git user email and name are set
The git user.email and user.name settings must be set or the commit to
the buildhistory repo (when BUILDHISTORY_COMMIT is set to "1") will
fail. If the user hasn't set these, set some dummy values since the
actual value is unlikely to be particularly useful and it's far worse
for the commit not to be done leaving the repository in a partially set
up state.
Prompted by [YOCTO #6973].
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Awais Belal [Thu, 21 May 2015 14:28:34 +0000 (19:28 +0500)]
initrdscripts: make boot drive detection more generic
The init script that invokes install and install-efi scripts
passes the first parameter that identifies the boot drive but
in cases when this disk is labeled and kernel configurations
allow disk labeling under /run/media/ this would pass the disk
label.
The earlier implementation considered that the drive name will
be passed and in case the label is passed it fails and provides
the boot drive as an option for installation driver.
We now use a more generic approach to identify the boot drive
which can handle both drive name as well as label if passed.
Signed-off-by: Awais Belal <awais_belal@mentor.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Peter Seebach [Thu, 21 May 2015 20:36:35 +0000 (15:36 -0500)]
rootfs.py: Make set -x not break rootfs creation
The rootfs logfile check errors out if it finds an "exit 1" in
a log. But consider the shell idiom:
if ! $command; then exit 1; fi
and consider a postinstall script with a "set -x" for debugging
purposes (to get log output in /var/log/postinstall.log.)
Solution: Ignore lines prefixed with a +, because those show shell
code even if a specific fragment won't be executed.
Signed-off-by: Peter Seebach <peter.seebach@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Andreas Müller [Thu, 21 May 2015 12:42:16 +0000 (14:42 +0200)]
libepoxy: make buildable for x11-less environments / update to latest version
* Make glx part configurable by PACKAGECONFIG enabled by 'x11' distro feature
* Major upstream enhancement is using pkgconfig for egl. This should make
those egl implementations happy that require compiler extra options for their
egl headers.
Example: meta-fsl-arm/imx-gpu-viv sets -DLINUX (and others) in egl.pc. These
are mandatory for proper builds.
Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Thu, 21 May 2015 18:40:45 +0000 (14:40 -0400)]
linux-yocto/3.19: NFC config, Braswell fixes and axxia support
Updating the 3.19 kernel SRCREVs for the following commits:
NFC:
727cfce45077 meta: intel-common: enable generic NFC support f3e890065903 meta: features/nfc: add generic configuration for NFC support
Braswell:
d3c0b958e688 drm/i915: New offset for reading frequencies on CHV. dac6babbba62 drm/i915/chv: Populate total EU count on Cherryview
Axxia:
c706cb356dea arch/arm/axxia: Remove the axxia zImage.fm build 45a1aaacf6cb drivers/hwmon: Remove adt75 redundant driver 7203ee166c01 arch/arm/mach-axxia: Fixed L2 power up failure a1541e9f0a4c kernel/irq/manage.c: Fix irq_set_affinity to allow use with buslocks d42c0bd1c8be arch/arm/mach-axxia: Reverse checkpatch compatibility 5dbd07431a7a arch/arm/mach-axxia: changed affinity parameter to cpu 23e4ebc66acb char: hwrng: AXXIA TRNG driver added for AXM55xx 61eb3c8ee1d7 arch/arm/mach-axxia: Updated Axxia 55xx PCIe driver to use correct Doorbell interrupt IRQs b03e0655094a AXM55xx RapidIO : Added support for Device revision and link down Monitor. 7577ad26cf73 rionet: Fix the corruption of tx_cnt during Transmit. 07fd2163ae56 arch/arm/mach-axxia: fixed NO SMP c9371e98cc80 arch/arm/mach-axxia: fixed compiler warning 0a814fe7e747 arch/arm/mach-axxia: Updated PCIe driver doorbell support cd3d9b46bea4 misc: lsi-ncr: Only use AMP lock on PPC platforms. 826c600c6ad6 fs: vmfs: Use generic mmap function e2d0047cb106 arch/arm/mach-axxia: Removed axxia_circular_queue f1ff06eaabed ARM: axxia: Add cluster and L2 power off in hotplug b98711344263 ARM: irq: Return error when set_affinity is called from hotplug 9fd9306a30ae arch/arm/mach-axxia: Enable L3 68989d446582 Revert "arch/arm/mach-axxia: Fixed affinity error on IRQ migration" 0be0ef90a887 Revert "arch/arm/mach-axxia: fixed failure to power up cluster" 1c6522a03e81 Revert "arch/arm/mach-axxia: fixed hang in preempt kernel" ef06a68393a3 fs/vmfs: Changes to add VMFS support for axxia. 3025e9deede6 drivers/usb/host: Changes to support the axxia BSP b128b4f0d4e8 drivers/tty: Changes to support the axxia BSP d1b60a7e62ef drivers/hwmon: Changes made to support the axxia BSP 2899ccbf1438 drivers/spi: Changes to support the axxia BSP 8e9cff566254 drivers/rapidio/devices: Changes to support axxia BSP 3424d2ca2653 drivers/net/ethernet: Changes to support the axxia BSP 2353dc816d6b drivers/mtd: Changes to support the axxia BSP 4b5fa2bf86cf drivers/misc: Changes made to support axxia BSP 8a5bd53ec241 drivers/i2c: Changes to support axxia BSP 02bfe1548d1a arch/arm/drivers/edac: Changes to support axxia BSP 2431db7c0c90 arch/arm/drivers/dma: Changes to support the axxia BSP 61fa3f268d5c arch/arm: arm changes to support the axxia BSP 22e0fb7be665 arch/arm/mach-axxia: add power management support 5cab63c5a1f2 arch/arm/mach-axxia: kernel files to support the mach-axxia 1336aba51616 arch/arm/boot: Changes to support the axxia BSP 97324fa920cb arch/arm/boot/dts: Files added to support axxia 5500 board
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Bruce Ashfield [Tue, 19 May 2015 20:59:39 +0000 (16:59 -0400)]
linux-yocto/3.19: CONFIG_ATA_BMDMA and gcc5 ARM64
Integrating the following commit to remove a ATA configuration warning:
common-pc-drivers: Enable CONFIG_ATA_BMDMA
Enabling the ATA_BMDMA re-enables ATA_PIIX which was getting
disabled
Signed-off-by: Saul Wold <sgw@linux.intel.com>
And the following to fix the ARM64 gcc5 boot:
arm64: psci: move psci firmware calls out of line
An arm64 allmodconfig fails to build with GCC 5 due to __asmeq
assertions in the PSCI firmware calling code firing due to mcount
preambles breaking our assumptions about register allocation of
function
arguments:
Bruce Ashfield [Fri, 15 May 2015 18:01:00 +0000 (14:01 -0400)]
linux-yocto/3.19: Braswell DRM fixes
Updating the 3.19 kernel SRCREVs to integrate the following Braswell
changes:
374b5d0e09ea drm/i915: Only wait for required lanes in vlv_wait_port_ready() fca99e8ee111 Revert "drm/i915: Hack to tie both common lanes together on chv" 00682f31b612 drm/i915: Work around DISPLAY_PHY_CONTROL register corruption on CHV 654b1a4497c5 drm/i915: Implement chv display PHY lane stagger setup
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Ross Burton [Wed, 20 May 2015 14:38:49 +0000 (15:38 +0100)]
zlib: clean up base_libdir symlink
libz.so symbolic link created in ${libdir} is
../../${base_libdir}/libz.so.1.2.8. This doesn't work if base_libdir or libdir
is changed, so use oe.path.relative to construct the correct path at build time.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Patrick Ohly [Wed, 20 May 2015 11:48:20 +0000 (13:48 +0200)]
combo-layer: handle unset dest_dir in sanity_check()
The previous "clean up dest_dir checking" patch (f8cdbe7497) improved
handling of empty dest_dir but made handling of unset dest_dir worse:
instead showing the "Option dest_dir is not defined for component ..."
error, it fails with a Python exception.
Avoid that by providing a sane fallback for the unset case. With that
change, dest_dir is no longer strictly required, but the check for it
is kept to ensure that a combo-layer.conf also works with older
combo-layer versions.
[Yocto #7773]
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ross Burton [Thu, 21 May 2015 09:19:22 +0000 (10:19 +0100)]
libxdmcp: make libbsd usage deterministic
libxdmcp can optionally use arc4random_buf() from libbsd instead of it's own
random key generation code. As this is an optional dependency add a
PACKAGECONFIG for it and default to not using libbsd.
Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Wed, 20 May 2015 12:05:03 +0000 (13:05 +0100)]
sstate: Add handling of do_shared_workdir task
Changing TMPDIR and rebuilding an image was resulting in rebuilds of
kernels due to dependencies on the shared_workdir task. If installed
from sstate, nothing needs this task so add it to the whitelisted
task patterns.
After this change, the kernel does not rebuild when a new TMPDIR and
hot sstate cache is used.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ross Burton [Tue, 19 May 2015 19:40:57 +0000 (20:40 +0100)]
midori: fix build with GLib 2.44
GLib 2.44 introduced a GListStore type which is ambiguous with GtkListStore when
using wildcard using statements. Use the full type name to fix builds.
Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
gstreamer 0.10 is still available from meta-openembedded/meta-multimedia
See also
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6294
http://lists.openembedded.org/pipermail/openembedded-core/2015-April/104276.html
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This allows removal of gstreamer 0.10 dependency from Qt4 recipe
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6294 Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
André Draszik [Mon, 18 May 2015 08:06:01 +0000 (09:06 +0100)]
icu-native: fix hard paths in native icu
The icu recipe installs icu-native twice, once in the usual location,
and once for cross builds into the path given by --with-cross-build.
This latter path is not included in the list of paths recognised by
chrpath.bbclass, hence the binaries in there retain the rpath as used
during compilation. This causes the package to not be relocateable
from sstate
[YOCTO #6851]
We use the infrastructure that is in place already, and simply set
PREPROCESS_RELOCATE_DIRS as necessary, and things start to work.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul Eggleton [Mon, 18 May 2015 15:15:08 +0000 (16:15 +0100)]
devtool: update-recipe: add option to write changes to bbappend
Quite often what you want to do having made customisations to a piece of
software is to apply those customisations in your own layer rather than
in the original recipe. Thus, add a -a/--append option to the
update-recipe subcommand which allows you to specify the layer to write
a bbappend into. The bbappend will be created at the appropriate path
within the specified layer directory (which may or may not be in your
bblayers.conf) or if one already exists it will be updated
appropriately.
(This re-uses code written for recipetool appendfile.)
Implements [YOCTO #7587].
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul Eggleton [Mon, 18 May 2015 15:15:07 +0000 (16:15 +0100)]
recipetool: add appendfile subcommand
Locating which recipe provides a file in an image that you want to
modify and then figuring out how to bbappend the recipe in order to
replace it can be a tedious process. Thus, add a new appendfile
subcommand to recipetool, providing the ability to create a bbappend
file to add/replace any file in the target system. Without the -r
option, it will search for the recipe packaging the specified file
(using pkgdata from previously built recipes). The bbappend will be
created at the appropriate path within the specified layer directory
(which may or may not be in your bblayers.conf) or if one already exists
it will be updated appropriately.
Fairly extensive oe-selftest tests are also provided.
Implements [YOCTO #6447].
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul Eggleton [Mon, 18 May 2015 15:15:06 +0000 (16:15 +0100)]
oe-selftest: move recipetool tests to their own module
These tests really belong in their own module; if we refactor
out a base class from DevtoolTests with shared functions then we can
move them out easily. Also create temp directory in setupLocal() so we
don't have to do that in individual tests anymore.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Most of the time when bb.note() gets called we want to see the output,
so ensure the level is set appropriately depending on the command line
options instead of being fixed at warning. (We don't want to see the
notes for fetch/unpack/patch though as they are too verbose).
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A buffer overflow flaw was found in the way glibc's gethostbyname_r() and
other related functions computed the size of a buffer when passed a
misaligned buffer as input. An attacker able to make an application call
any of these functions with a misaligned buffer could use this flaw to
crash the application or, potentially, execute arbitrary code with the
permissions of the user running the application.
Signed-off-by: Haris Okanovic <haris.okanovic@ni.com> Reviewed-by: Ben Shelton <ben.shelton@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Remove intermediate partitions that may have been created by a previous
wic invocation. Those partitions are causing issues on some systems. In
particular vfat partition creation is hanging on mcopy execution on
Fedora.
Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul Eggleton [Fri, 8 May 2015 14:26:04 +0000 (15:26 +0100)]
devtool: if workspace layer exists, still ensure it's in bblayers.conf
When we run devtool, if the workspace layer already exists but isn't in
bblayers.conf (perhaps because it was previously created but
subsequently removed from bblayers.conf by the user) then we should add
it and notify the user, otherwise devtool operations won't work.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Paul Eggleton [Thu, 14 May 2015 10:44:59 +0000 (11:44 +0100)]
lib/oe/recipeutils: add a parse_recipe_simple() function
Add a function that simply parses a recipe by name and optionally the
bbappends that apply to it. (Note that if you're using tinfoil you need
to have initialised it with config_only=False so that it can map the
recipe name to a recipe file.)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
If we execute an external command, we ought to prepare for the
possibility that it can fail and handle the failure appropriately. We
can especially expect this to happen when running bitbake in this
scenario. Ensure we return the appropriate exit code to the calling
process.
Fixes [YOCTO #7757].
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Markus Lehtonen [Thu, 30 Apr 2015 09:16:07 +0000 (12:16 +0300)]
devtool: extract: remove patches when S=WORKDIR
Before this change, all files from the recipe (SRC_URI), including
patches, were added to to srctree repository when S==WORKDIR. The patch
files are useless as they are automatically applied on top of the
srctree by devtool.
This change causes devtool extract to not commit these unnecessary (and
possibly confusing) patch file(s) into srctree repository.
[YOCTO #7602]
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Otavio Salvador [Mon, 11 May 2015 11:26:47 +0000 (08:26 -0300)]
gstreamer1.0-plugins-bad: Move EGL requirement for Wayland
The EGL is used by the Wayland backend. When building using Software
Rendering and without Wayland support the EGL backend is not available
so we should not require EGL for GLES2 support.
This fixes following build error:
,----
| ...
| checking for bcm_host_init in -lbcm_host... no
| checking for WAYLAND_EGL... no
| configure: error: Could not find the required EGL libraries
| Configure failed. The contents of all config.log files follows to aid debugging
| ERROR: oe_runconf failed
`----
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com>
native.bbclass: avoid unintended substring replacement when setting PROVIDES
The way native_virtclass_handler was implemented leaded to
unintended substring replacements when setting PROVIDES for
native providers, in case the original PROVIDES value contains
providees with common substrings.
Here's a practical case where the old behavior was problematic:
the oracle-jse-jdk-x86-64 recipe provides both virtual/java and
virtual/javac:
Saul Wold [Tue, 12 May 2015 19:02:46 +0000 (12:02 -0700)]
lttng-modules: Update to stable version 2.6.1
This fixes a build issue with the 3.19.5 kernel where the regmap prototypes
have changed. The patch is rebased do to changes in the new version of the
Makefile.
[YOCTO #7737]
Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Ross Burton [Fri, 15 May 2015 16:42:09 +0000 (17:42 +0100)]
automake: simplify perl location forcing logic
Instead of letting configure find the host's perl and then use a complicated sed
to replace it at install time, simply pre-seed the configure logic with the path
we want to use.
Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ross Burton [Fri, 15 May 2015 16:42:08 +0000 (17:42 +0100)]
autoconf: simplify perl location forcing logic
Instead of letting configure find the host's perl and then use a complicated sed
to replace it at install time, simply pre-seed the configure logic with the path
we want to use.
Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Martin Jansa [Thu, 14 May 2015 11:41:26 +0000 (13:41 +0200)]
boost: properly fix do_boostconfig re-execution
* it was partially fixed in:
commit 291e20a51544c640d07767d1dc32d762f4370f41
Author: Venkata ramana gollamudi <ramana.gollamudi@huawei.com>
Date: Fri Apr 13 11:42:46 2012 +0000
Subject: boost: fix re-execution of task
but with disadvantage that when CXX or *FLAGS variables were changed
it was continuing to use old values
* just remove the line before appending it with current values to fix
that
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Modifies:
python3-native_3.4.2.bb -> python3-native_3.4.3.bb: Updates checksums, LICENSE did not change,
dates were updated.
python3_3.4.2.bb -> python3_3.4.3.bb: Updates checksums, LICENSE did not change,
dates were updated.
generate-manifest-3.4.py: fixes asyncio and net-tools.
python-3.4-manifest.inc: fixes asyncio and net-tools.
This upgrade contains a fix for CVE-2014-9365.
Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Thu, 14 May 2015 09:32:24 +0000 (10:32 +0100)]
sstate: Improve HASHCHECK function to make siginfo configurable
In some cases we want to test the availability of siginfo files, in some
cases we do not and really want the .tgz files (which may or may
not be present too). This makes adds a parameter to the function to allow
this.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Thu, 14 May 2015 09:31:51 +0000 (10:31 +0100)]
kernel/rm_work: Improve interaction
The do_shared_workdir task does leave behind the necessary information in
shared-work after it completes. We don't make this a "full" sstate task
however since that means tarring up and copying what is usually a large
amount of data which would be better extracted straight from the original
SCM.
The issue with rm_work occurs since it removes the do_shared_workdir stamp
meaning subsequent builds will add it back if they need to touch any kernel
modules for example. This ends up triggering a near enough complete kernerl
rebuild since if configure reruns, populate_sysroot has to rerun.
This change promotes the task to have a "setscene" variant but it doesn't use
any of the sstate class lifting to generate the sstate file. The sstate function
will therefore never get called since the sstate object will never exist.
We can add the task to the list of tasks rm_work promotes to a setscene variant
and unwanted rebuilds of the kernel should be avoided.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For recipes with PACKAGES_remove = "${PN}", the find which removes
.la files can race against deletion of other directories in WORKDIR
e.g.:
find: '/home/autobuilder/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/build/tmp/work/qemux86_64-poky-linux/init-ifupdown/1.0-r7/sstate-build-populate_lic': No such file or directory
| WARNING: /home/autobuilder/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/build/tmp/work/qemux86_64-poky-linux/init-ifupdown/1.0-r7/temp/run.do_configure.6558:1 exit 1 from
| find /home/autobuilder/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/build/tmp/work/qemux86_64-poky-linux/init-ifupdown/1.0-r7 -name \*.la -delete
Fix the race in the same way.
[YOCTO #7522]
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Wed, 13 May 2015 08:08:09 +0000 (09:08 +0100)]
glibc: Fix x32 make race
On x32 builds, sysd-syscalls appears malformed since the make-target-directory
appears on the wrong line. This causes races during the build process where you can
see failures like:
Assembler messages:
Fatal error: can't create [...]glibc/2.21-r0/build-x86_64-poky-linux-gnux32/time/gettimeofday.os: No such file or directory
Assembler messages:
Fatal error: can't create [...]glibc/2.21-r0/build-x86_64-poky-linux-gnux32/time/time.os: No such file or directory
The issue is that the carriage return is being escaped when it should
not be. The change to sysd-syscalls with this change:
which ensures the target directory is correctly created. Only x32 uses the vdso
code which contains the bug which is why the error only really appears on x32.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Robert Yang [Mon, 4 May 2015 15:32:35 +0000 (08:32 -0700)]
ghostscript: 9.15 -> 9.16
* Update LICENSE's md5sum, the new version added a "of" in the file, the
license is the same.
* Remove ghostscript-9.02-parallel-make.patch, it has 932 lines and
modified 24 files, which is hard to maintain, and it can't be applied
since the code has changed, and if we meet parallel issues again, we
need fix it in other ways.
* Fix a build error of -Werror=return-type.
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
