The new dpkg will report linux-wrs version parse error,
since there is a '_' inside. This patch fixes this issue.
Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
Rebase several patches to fit the latest version
Fix a compile issue related with snprintf.
dpkg: bump PR
Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
Signed-off-by: Saul Wold <Saul.Wold@intel.com>
Rebase several patches to fit the latest version
Fix a compile issue related with snprintf.
Reset PR in dpkg.inc
Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
Signed-off-by: Saul Wold <Saul.Wold@intel.com>
Using poky-qemu with our new tap networking and/or unfs support
required too many additional build steps. This updates the
meta-ide-support dependencies so all features are built and
available to use.
Specifically, this adds psuedo-native, qemu-helper-native, and
unfs-server-native to the dependency chain for meta-ide-support.
This fixes [BUGID #392]
Also add poky-gen-tapdevs and remove runqemu-nfs from the
qemu-helper-native recipe, and update some qemu control script
error messages to suggest building meta-ide-support.
Signed-off-by: Scott Garman <scott.a.garman@intel.com>
Fix the paths in configure.ac to use the target libraries and generators for
building pygtk. Fix taken from OE.
Thanks to Gary Thomas for providing a first stab at this.
Signed-off-by: Joshua Lock <josh@linux.intel.com>
[BUGID #374]
Previously the poison directories patch was present, but not enabled due
to the lack of the configure option being set, and also the fact configure
itself was not being patched.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
[BUGID #374]
The poison directory patch that was included with gcc-4.5.0 was not previously
enabled due to the lack of the configure file changes.
The patch has been updated to include the configure fragment. It was also noted
that this patch preformed nearly the same functions as the
zecke-no-host-includes patch, but with slightly different directories.
The directories scanned were added from the zecke-no-host-includes patch to
the new gcc-poison-dir-extend.patch.
The other difference with the zecke patch is that poisoned headers is no longer
an immediate fatal error. There may be instances where someone wants to do
this.
Adding -Werror=poison-system-directories to the CFLAGS would restore the
behavior.
Also fix a small problem where --help=warnings on gcc wouldn't return the
poison-system-directories as a valid option, even though it was.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
In some circumstance guest driver got interrupted before inserting all args
for one command, so that qemu get an invalid args and hang. GL patch
doesn't consume these missing args, which further cause FIFO disorder.
This commit reverts wrong behavior of GL patch, and introduces a qemu
upstream patch to rewind FIFO unpon detecting incomplete command.
[BUGID #111] fixed by this.
Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
This patch fixes the build failure I met with.
Thanks a lot to Qing He and Kevin Tian for pointing this out!
Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
gcc uses hardcoded path "${with-build-sysroot}/usr/include" to check target
libc ssp support. Based on GLIBC version strings in features.h in that search
path, gcc knows whether target (e)glibc implements stack protector itself.
However this breaks meta-toolchain, which actually has target libc headers
installed under {with-build-sysroot}/opt/... This way features.h is not found
and thus gcc-crosssdk-intermediate thinks that target (e)glibc doesn't support ssp.
Later when building eglibc-nativesdk, undefined reference to "__stack_chk_guard"
occurs which was caused by:
o eglibc do_configure found that gcc-crosssdk-intermediate supports ssp,
and thus enable -fstack-protector for nscd
o eglibc itself supports stack smash proctection for some architectures such
as i386, x86-64, etc. It's expected to use its own method to provide stack
protection, instead of relying on gcc. So eglibc rtld.os doesn't export
__stack_chk_guard to other modules
o then when installing nscd objects, gcc-crosssdk-intermediate sees the
flag "-fstack-protector", while it thought this eglibc doesn't implement
ssp itself, so gcc turns to the alternative to find a valid
__stack_chk_guard exported. eglibc doesn'g export it, while
gcc-crosssdk-intermediate itself disables libssp.
Then the undefined reference happens. If enabling libssp for gcc-crosssdk-
intermediate, it may also work-around this issue. But the ideal fix is still
to replace hard coded path with the actual one where target libc gets installed.
glibc-nativesdk doesn't encounter this issue because it thinks gcc doesn't
support ssp, and thus doesn't enable "-fstack-protector" for nscd. Don't know
the reason yet
This fix [BUGID #366]
Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
rpm_5.1.10.bb: bump PR
[BUGID #357]
The upstream distribution location for the Poky 5.1.10 version of RPM
has changed. Correct it to the new location.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Saul Wold <Saul.Wold@intel.com>
[BUGID #332]
Disable the dependency loop message that looked like an error had
occured. This is really a debug message.
Also remove the "remove: " debug message about which side of the
dep loop it is removing to resolve the circular dependency.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Patches can be symlinks and changing their ownership may not be possible.
Therefore stop doing this.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
the root cause is that the qemu cursor array is hardcoded to 256 bytes, while the sato use cursor of the size 64*64=4096, thus lead buffer overflow and abnormal mouse.
A qemu patch is introduced to dynamically allocate qemu cursor array to fix this issue. BTW, qemu upstream already redesign the cursor interface and implementation, and this issue does not occur in upstream, so no need to push this patch to upstream. and when upgrade the qemu, this patch can be safely removed.
Fix [BUGID #170]
Signed-off-by: Yu Ke <ke.yu@intel.com>
If not configured with --enable-target-optspace, gcc will report
errors if there is '-Os' optimization in parameters.
This fixes [BUGID #342]
Also add "--enable-target-optspace" option to arm gcc configuration.
Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
Fix the out of memory when building webkit-gtk with gcc-4.5.0
The new feature added after 4.3.3
"http://www.pubbs.net/200909/gcc/94048-patch-add-support-for-rmipsjalr.html"
will cause cc1plus eat up all the system memory when build webkit-gtk.
The function mips_get_pic_call_symbol keeps on recursively calling itself.
Disable this feature to walk aside the bug.
Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
Fix one parameter order issue for base_contains function,
which impacts glibc build under new gcc.
Add new judge code to determine whether <altivec.h> is needed.
This fixes the mpeg2dec build failure under new gcc.
Use O2 as the optimization flag to tinylogin as it will meet
segfault if compiled by gcc-4.5.0 when enable both frename-registers
and Os options. Use O2 instead.
Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
Add qemu-mipsel to the list of generated simulators. Obviously
this is needed to build a MIPS little endian system.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
In order to resolve a host-contamination problem, we re-work the way that
autoconf and friends are invoked during the compilation of RPM.
This has a side effect of fixing another bug where RPM was being renamed
HOST_ARCH-HOST_OS-rpm. So we remove the "fixes" for that behavior as well.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Within Poky we have a large number of self-referencing packages. So we
need to raise the number of rescans before triggering a dependency loop
error. 100 seems like a reasonable number.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Enable debian style tags including suggests, enhances, recommends
Note, these are not yet used by the dependency resolver.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
svn version of valgrind uses #! @PERL@ for several perl
scripts. However, PERL in autoconf doesn't distinguish
host perl and target perl, causing STAGING_DIR_NATIVE be
written in the output scripts.
This causes unrunnable scripts, and fails FILERDEPENDS
mechanism (thus also do_rootfs_rpm).
Uses /usr/bin/perl instead to fix it.
Signed-off-by: Qing He <qing.he@intel.com>
changes:
- add headerAddOrAppendEntry in lib/rpm4compat.h for compatibility
- fix rpmbag.h introduced in rpm 5.1.10
Signed-off-by: Qing He <qing.he@intel.com>
Adding i386-linux-user in target-list is enough in theory, but our gl stuff is
not friendly to linux-user code. So disable it when compiling linux-user.
[BUGID #218] fixed by this.
Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
Having one monolithic packages directory makes it hard to find things
and is generally overwhelming. This commit splits it into several
logical sections roughly based on function, recipes.txt gives more
information about the classifications used.
The opportunity is also used to switch from "packages" to "recipes"
as used in OpenEmbedded as the term "packages" can be confusing to
people and has many different meanings.
Not all recipes have been classified yet, this is just a first pass
at separating things out. Some packages are moved to meta-extras as
they're no longer actively used or maintained.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
Nitin A Kamble
Richard Purdie
Dongxiao Xu
Saul Wold
Scott Garman
Joshua Lock
Gary Thomas
Mark Hatle
Zhai Edwin
Dexuan Cui
Kevin Tian
Yu Ke
Bruce Ashfield
Qing He