Fixes [BUGID #99]
The mouse option as passed to Xfbdev was correct for most
targets, except mips (and a PS/2 mouse). Modifying the
syntax of the option fixes the mips case, and has no impact
on other users.
Signed-off-by: Richard Griffiths <rgriffit@windriver.com>
Fixes [BUGID #99]
The mouse, usb and cursor devices don't work for the
qemumips machine. There's no easy way to 'undo' the
defaults, or dynamically remove them, so we simply
don't use the default UI options for this machine type.
Mouse and pointer are provided via ps/2 and not via
the usb and wacom tablet driver.
Signed-off-by: Richard Griffiths <rgriffit@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
This fixes the following error on do_install:
> line 175: export: `=': not a valid identifier
> line 175: export: `[...]/usr/lib': not a valid identifier
Signed-off-by: Daniel Díaz <yosoy@danieldiaz.org>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
If this is done as a global export it can affect the whole task and the
wrong python libraries can be found for example.
[BUGID #335]
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
[BUGID #376]
Update to the insane class to detect the new gcc and binutils poison
messages located within the config.log. (Continue to scan for the old
style message.)
Add a new compile and install log check to the package_qa that scans the
logs for the same types of messages "unsafe for cross-compilation".
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
[BUGID #375]
When configuring for the log file output, we generate a symlink to the
target filename. This link uses the same file naming, but without the
active pid, making it easier to see which log file is the last one
generated.
Signed-off-by: Mark Hatle <mark.hatle@windriver.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>
libc locale generation is very time consuming so document the
GLIBC_GENERATE_LOCALES variable in the sample local.conf
Signed-off-by: Joshua Lock <josh@linux.intel.com>
[BUGID #379]
In a strange configuration, siteconfig could have already generated it's
directory, but decided it needs to regenerate the site config. The lack
of -p in the mkdir causes a failure.
Signed-off-by: Mark Hatle <mark.hatle@windriver.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>
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>
