systemd doesn't look in /etc/rcS.d for init scripts so we never
start networking unless we are using ifplugd. We need to check
how this behves on the sysmobts and sysmobsc in case the network
is being started twice.
Build a version of barebox that has support for NAND flash and
ubifs. Load the kernel from the device. One needs to flash the
*mlo*.img into the xloader partitions and the other image into
the barebox partition.
erase /dev/nand0.xload.bb
erase /dev/nand0.xload_backup1.bb
erase /dev/nand0.xload_backup2.bb
erase /dev/nand0.xload_backup3.bb
cp /mnt/mmc0.0/MLO /dev/nand0.xload.bb
cp /mnt/mmc0.0/MLO /dev/nand0.xload_backup1.bb
cp /mnt/mmc0.0/MLO /dev/nand0.xload_backup2.bb
cp /mnt/mmc0.0/MLO /dev/nand0.xload_backup3.bb
`debugfs' treats spaces and "" specially. So when we are dealing with
file names, great care should be taken to make sure that `debugfs'
recognizes file names correctly.
The basic solution here is:
1. Use quotation marks to handle spaces correctly.
2. Replace "xxx" with ""xxx"" so that debugfs knows that the quotation
marks are parts of the file name.
[YOCTO #6503]
(From OE-Core rev: 24f17607e996c499c8f86eda0588d02af1e960b9)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Scenario:
a) libtool script is built on system with bash as /bin/sh
b) machine B installs sstate from build a)
c) machine B has dash as /bin/sh
In this scenario, the script fails to work properly since its expecting
/bin/sh to have bash like syntax and it no longer does have it.
This patch forces the configure process to use /bin/bash, not /bin/sh
and hence allows the scripts to work correctly when used from sstate.
(From OE-Core rev: 24d5b449e5f4d91119f0d8e13c457618811aadfc)
(From OE-Core rev: 330c3085317a0b0981163ff5c41c54596e0d127d)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* some fundamental perf commands can work
without the dependency on perl, python or bash
make them separate packages and RSUGGEST them
* bump PR
The patch was sponsored by sysmocom
(From OE-Core rev: a6f79561f7a2f6bc354d5ea8d84b836ac5c9b08f)
Signed-off-by: Henning Heinold <henning@itconsulting-heinold.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* TUI/GUI support was added in 2.6.35 based on libnewt
* since 3.10 slang replaced libnewt completly
* changing TUI_DEFINES is not necessary, because NO_NEWT is
still respected with newer kernels
* add comment about the gui history to the recipe
The patch was sponsored by sysmocom
(From OE-Core rev: 104e317f1fe68244d31c72897df2e5c997ff502a)
Signed-off-by: Henning Heinold <henning@itconsulting-heinold.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The patch was sponsored by sysmocom
(From OE-Core rev: 7e38d8ad6f7f4c289975acdac5c4d254ff3df7e6)
Signed-off-by: Henning Heinold <henning@itconsulting-heinold.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fix the use of command dirname on ubuntu 12.04.
dirname does not accept space in file name.
(From OE-Core rev: ab6bd289d51c3c44862b43241a99d3e4f3ff13c0)
Signed-off-by: Stéphane Cerveau <scerveau@connected-labs.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The SHA we use it actually on cross_prelink branch
if you do not use yocto source mirrors then the fetch
for prelink on dora fails due to missing branch in SRC_URI
(From OE-Core rev: 13b57cab7cdd2bf967622ec5015478dc56938b8b)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
[YOCTO #6309]
It appears a logic issue has caused rpm -V to no longer
verify the files on the filesystem match what was installed.
(From OE-Core master rev: 117862cd0eebf6887c2ea6cc353432caee2653aa)
(From OE-Core rev: 9f9bcad51381887819d58ffdde2e41307d342473)
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
console-kit-log-system-start.service fails to to start if the
/var/log/ConsoleKit directory does not exist. Normally it is created
automatically but as we mount a tmpfs at /var/log, we need to add
a tmpfiles.d entry to create it.
(From OE-Core master rev: 2a9a14bf400fe0c263c58aa85b02aba7311b1328)
(From OE-Core rev: 305da37a4dc0fba2b8f3219cfae47a1d4228f244)
Signed-off-by: Jonathan Liu <net147@gmail.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Previously, even if we encounter some error when populating the
ext filesystem, we don't error out and the rootfs process still
succeeds.
However, what's really expected is that the populate-extfs.sh script
should error out if something wrong happens when using `debugfs' to
generate the ext filesystem. For example, if there's not enough block
in the filesystem, and allocating a block for some file fails, the
failure should not be ignored. Otherwise, we will have a successful
build but a corrupted filesystem.
The debugfs returns 0 as long as the command is valid. That is, even
if the command fails, the debugfs still returns 0. That's really a
pain here. That's why this patch checks the error output to see whether
there's any error logged.
(From OE-Core rev: 468d3e60ee10348578f78f846e87c02359fdb8bf)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There was a patch trying to fix this problem by using 'dirname', but it
caused some build failures, thus got reverted.
The problem is that $DIR might be empty and we should first do the check
before trying to use $(dirname $DIR).
[YOCTO #5712]
(From OE-Core rev: 8277c71747758e2ba0815a6f5cd11c9e0c9c90ce)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This doesn't work like this. We need to know the _exact_ PV/PR
of the package and we don't. Specially with the PR server in dora
and later we can not know the version.
This reverts commit 767d7b6939.
I had the actual title of the manual as displayed in the section
heading for Chapter One wrong.
(From yocto-docs rev: e61b251da0d8225f7497b2b7a0a8c8d1510a429b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Found a link in the dev-manual that had a hard return splitting
the link across two lines. The mega-manual.sed file cannot process
those links so it ignores them.
(From yocto-docs rev: fabd8d47b4a5ce1e108ad282d9903e3b1daa5f3d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Found a very subtle problem with the search string that processes
links to the Yocto Project Profiling and Tracing Manual where the
links go to the top-level (i.e. no ID tag in the link).
I had the name of the manual as "Yocto Project Profile and
Tracing Manual", which means there would never be a match.
Consequently, when the Makefile called the mega-manual.sed file
to process the links in mega-manual.html, any top-level link
to that manual was not processed and was being left as a hard
link to the versioned manual. Processing a top-link should
convert it to a non-link (for now).
(From yocto-docs rev: 38c7971abe19293657f0170ecd8dc28c1047859b)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Conflicts:
documentation/tools/mega-manual.sed
Had to clean up some conflicts to get the cherry-pick
to work. It seems the line for the profile manual was
not even in this sed file. Also, had to reset the
1.4.4 strings to 1.5.3.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added a new entry to support the 1.5.3 release. Using July 2014
as the release month and year.
(From yocto-docs rev: fcd6046b8b2a5606e77d14cffa0bd2eebbe1748a)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
So far we have used chrpath to fix the rpath we don't want but
this creates issues with supporting both dora and edison (we need
to depend on different recipes). Instead just force the RPATH to
be off. This can be done by setting the internal _RPATH variable.
I found this in Tool/gnulink.py.
It seems that 585324fee380109acd9986388f857f413a60b896 is no
longer there in git and it has been rewritten to
ffc3ad4945da69f3caa2b40e4eed715a9a8d9526
Change-Id: I9ffe8bd9bcef0d2dc5e6f6d3a6e4317bada8f4be
(master rev: b193c7f251542aa76cb5a4d6dcb71d15b27005eb)
(From OE-Core rev: b7371b49b4b83c2e864126480b65363fe9f2cfd2)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Patrick Doyle <wpdster@gmail.com>
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This upgrades the firmware from 3.6 to 3.10. This is a significant
firmware upgrade and it changed ABIs too. Try hard to fix the
dependencies as much as possible. This requires the DSP headers
files to be of version 3.10 as well but we can not have versioned
DEPENDS.
The code has not been finished and doesn't meet the quality
standards we have for a product. Comment the sysmobts-mgr
related files that will be back soon.