Currently default header is linux-libc-header, which leads the dismatch
with wrs kernel.
The different headers for same file cause trouble between kerenl module and
user level binary. E.g. segfault in v86d due to different
CONNECTOR_MAX_MSG_SIZE in connector.h from the one used by uvesafb.
This fix is work around to sync with wrs kernel headers, and should be removed
after switching to linux-libc-headers-wrs.
[BUGID #279] 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>
When install the live image into netbook/emenlow, the install tool prompt:
# Found drive at /dev/sda. Do you want to install moblin there ? [y/n]
The "moblin" here should be replaced by "poky".
Fix [BUGID #368]
Signed-off-by: Yu Ke <ke.yu@intel.com>
qmmp is not included any image before, because it depends on one moblin recipe taglib. Since now the taglib is included into meta/recipes-support, it is safely to add qmmp into the task-poky-qt.
This commit also add an build time dependency for qmmp, because qmmp use some head files from taglib. Without this, qmmp build failure is occationally observed.
Fix [BUGID #301]
Signed-off-by: Yu Ke <ke.yu@intel.com>
Part of [BUGID #373]
Update the default revisions for kern_tools to pull in the updates
required to support BSP bootstrapping.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Part of [BUGID #373]
In order to generate BSP definitions for new boards, we need
to know the architecture. So we'll arrange to pass it to
updateme.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Fixes [BUGID #372]
If for some unknown reason, the kernel git repository hasn't been properly
updated and is *older* than the revisions listed in default-revisions the
branch sanity checking kicks in and tries to force branches to the right
revs. The problem is, the revisions it is looking for don't exist in the
tree. As a result, error messages are thrown about invalid commit IDs.
These aren't helpful, and are simply confusing for the user.
Instead we can test for the commit ID, and if it isn't valid, indicate
that the commit ID isn't valid and that the tree is potentially out
of sync.
This situation is not common, but it is an easy test and the extra
sanity checking is useful.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.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>
[BUGID #327]
RPM attempts to validate all of the directories on the system are
owned by a package. While the root "/" directory was not owned, so
in some cases an error could be thrown. Resolve this by informing
RPM that yes, "/" is in fact a directory on the system that was
properly constructed and is "owned".
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
This reverts commit 138df217ef.
We still need the vm_mmap_min_addr set to 0 to run locale generation for
qemu-arm
Signed-off-by: Joshua Lock <josh@linux.intel.com>
The directory list in the manifest file needs to be sorted such that child
directories are deleted first. Fortunately as the list is generated by walking
the directory tree achieving this is as simple as reversing the directory list.
Fixes [BUGID #269]
Signed-off-by: Joshua Lock <josh@linux.intel.com>
With new batch ability, we can use below simple 2 lines for multiple alternatives
updates:
ALTERNATIVE_LINKS = "${bindir}/cmd1 {sbindir}/cmd2 ..."
ALTERNATIVE_PRIORITY = "100"
Then for each command "/path/cmd" listed in ALTERNATIVE_LINKS, below is done
automatically:
${D}/path/cmd is renamed to ${D}/path/cmd.{PN}
a new alternative named 'cmd' is created which:
links /path/cmd to /path/cmd.{PN} with priority specified in ALTERNATIVE_PRIORITY
This way the recipe with multiple alternatives could be simplified a lot. There
are still some cases where above assumptions may break, but I expect more recipes
should benefit from this simple enhancement
Fix [BUGID #257]
Signed-off-by: Kevin Tian <kevin.tian@intel.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>
