Scott Rifenbark [Fri, 25 Oct 2013 16:43:43 +0000 (09:43 -0700)]
adt-manual: Edits to "Extracting the Root Filesystem" section
This section was a bit confusing. I added some lists to make
it clearer when this step is necessary. I also added some more
detail on where to find the setup script.
Scott Rifenbark [Thu, 24 Oct 2013 20:15:24 +0000 (13:15 -0700)]
adt-manual: Edits to the "Using a Cross-Toolchain Tarball" section.
This section was not quite right for the installation method
after obtaining the tarball. There was some old stuff in there
and it didn't mention the fact that the script asks you what
directory you want to install into.
Scott Rifenbark [Thu, 24 Oct 2013 17:44:52 +0000 (10:44 -0700)]
adt-manual: Fixed toolchain path in example
The path used for the toolchain was wrong. The string
"toolchain" appears in the path. I was not informed of this
before locking down 1.5 release doc changes. I have updated
the path in the "Using a Cross-Toolchain Tarball" section.
Occured twice.
Scott Rifenbark [Thu, 24 Oct 2013 16:51:38 +0000 (09:51 -0700)]
adt-manual: Removed tarball method from "Getting the ADT Installer Tarball"
Fixes [YOCTO #5368]
Partial fix to this issue.
This section demonstrated how to build the ADT Installer tarball
using BitBake by downloading the poky release tarball. I updated
the section to use the method where you use Git to clone the
poky repo and then check out the current release as a branch.
Scott Rifenbark [Thu, 24 Oct 2013 16:09:42 +0000 (09:09 -0700)]
adt-manual: Fixed wording for getting the ADT tarball
Poorly worded opening sentence for the "Getting the ADT Installer
Tarball" section. I re-wrote this to remove the confusing link
to the Index of Releases.
Scott Rifenbark [Thu, 24 Oct 2013 15:42:21 +0000 (08:42 -0700)]
yocto-project-qs: Updated the "Super User" section for no tarballs
Fixes [YOCTO #5368]
Partial fix for this issue. This section had two options for
setting up the Source Directory (tarball and cloned repo). I
removed the tarball option.
Also, I did some routine formatting as well as verified that
the example runs on a more recent Linux distro. Previously, the
example was confirmed and stated that it ran on 10.04 Ubuntu.
Well, this distro is not even in the supported list any longer
so I ran it on a 12.04 Ubuntu machine and stated that.
Discovered that the string "toolchain" is in the pathname of the
toolchain installers from the downloads area. This invalidated
the explanation of how the installer files are named and the
actual examples themselves. I fixed it all.
Scott Rifenbark [Wed, 23 Oct 2013 22:44:48 +0000 (15:44 -0700)]
yocto-project-qs: Updated "Building an Image" example to use Git repo
Fixes [YOCTO #5368]
Partially addresses this issue, which is removal of examples that
use a poky tarball. I changed the example so that it clones the
upstream poky repo and then checks out a local branch named for
the most recent release.
Scott Rifenbark [Wed, 23 Oct 2013 17:41:09 +0000 (10:41 -0700)]
documentation: Changed Note for most recent manual
Fixes [YOCTO #5368]
Changes partially address this issue, which is the removal of
tarball installations for poky. The notes at the beginning of
the YP manuals suggested that the tarball version of a manual
might lag the version found on the website. Because we are
discouraging installing poky/documentation from a tarball now,
I have re-written the note to be generic and suggest simply that
for the most recent version of the manual associated with the
release, see the manual on the website.
Scott Rifenbark [Tue, 22 Oct 2013 15:58:21 +0000 (08:58 -0700)]
dev-manual: Added -ptest to list of complementarty packages
Added the '-ptest' complementary package to the list of packages,
which included '-dev' and '-dbg' when using inherit packagegroup.
Robert P. J. Day pointed out the code in the OE packagegroup.bbclass
class that showed these three packages all together.
Scott Rifenbark [Tue, 22 Oct 2013 15:49:31 +0000 (08:49 -0700)]
dev-manual: Uncommented the Toaster GUI section.
Removed the comments for the section that describes how the
Toaster works with a GUI. I also commented out the smaller
section that was used in place of the GUI section before it
was fully functional.
Scott Rifenbark [Mon, 14 Oct 2013 18:18:04 +0000 (11:18 -0700)]
profile-manual: Added note about SystemTap ssh connectivity
Fixes [YOCTO #4409]
Added a note into the Setup section for SystemTap that tells
how ssh connection is assumed. Also provided a link to the
wiki page that basically replicates all the same information that
is in the section.
Scott Rifenbark [Mon, 14 Oct 2013 16:55:44 +0000 (09:55 -0700)]
dev-manual: Added note for BB Commander project location.
Fixes [YOCTO #5203]
Adding a BB Commander project location that is the same as your
Eclipse workspace causes an error. I have added a note warning
the user to not do this.
The actual file listings for the formfactor_0.0.bb and
formfactor_0.0.bbappend files had changed. I updated the listings
to match the actual files with the release.
Jason Wessel [Wed, 30 Oct 2013 17:35:17 +0000 (12:35 -0500)]
grub-efi.bbclass: Fix startup.nsh to work on more EFI revs
Some revs of the EFI firmware + shell do not automatically setup the
path in a such a way as to execute a binary without an absolute
reference like "FS0:\EFI\BOOT\bootx64.efi". All the versions that I
have tested work properly by simply calling the binary which is in the
EFI\BOOT directory by name like "bootx64.efi".
The error you see on the console looks like the following:
startup.nsh> EFI\BOOT\bootx64.efi
'EFI\BOOT\bootx64.efi' is not recognized as an internal or external command, operable program, or batch file
Shell>
This patch simply drops the EFI\BOOT for greater compatibility.
Jacob Kroon [Wed, 30 Oct 2013 00:57:11 +0000 (01:57 +0100)]
update-rc.d.bbclass: Cleanup package scripts
* Add proper preinst script
* Use -n "$D"/-z "$D" checks throughout the scripts
* Only set OPT in cases where its used
* Don't pass unnecessary -f to update-rc.d in postrm script
* Remove outdated comment
grub-efi.bbclass: Fixes GRUB_IMAGE when using boot-directdisk class
When boot-directdisk class is used and EFI boot is set the
grub-efi-${TRANSLATED_TARGET_ARCH}-native need to be dependent.
Allowing GRUB_IMAGE to be created and bootia32.efi got from the
image directory.
As above shows, irattach not started after executing restart command.
This commit changed the restart command logic: firstly stop, then
start.
Prompt telling user irattach start successfully or failure also
added.
Jason Wessel [Wed, 30 Oct 2013 03:04:32 +0000 (22:04 -0500)]
syslinux.bbclass: Fix default serial port string
The default value of SYSLINUX_SERIAL_TTY is not correct.
It should be console=ttyS0,115200 else the boot string generated in
the syslinux menus for the serial choice is not correct. The kernel
boot parameters will get set to:
Seth Bollinger [Sat, 26 Oct 2013 14:23:24 +0000 (09:23 -0500)]
ncurses-terminfo: Remove bashism from basic terminfo installation
The vtX terminfo files aren't being copied on systems where bash isn't
the default shell (debian, etc.). I removed the bash specific syntax
so the files are properly copied on these systems.
Hongxu Jia [Tue, 29 Oct 2013 07:12:17 +0000 (15:12 +0800)]
coreutils: support command arch
The "arch" is removed in util-linux 2.23, but some old
software and devs look for arch:
http://lists.gnu.org/archive/html/bug-coreutils/2007-06/msg00010.html
systemd-compat-units: Use correct run-postinsts script link
OE-Core commit 75a14923da1ba91eddde47f0907345c19c82d6f0 has moved
run-postinsts script execution from S98 to S99 in rcS.d. run-postinsts.service
should check for this script and run it on first boot rather than
S98run-postinsts, which is for opkg/dpkg.
the link was corrected but the mentioned commit is not available. Instead of
reverting, we use the same variable as opkg for init script ordering and drop
a note in case somebody wants to change default.
Gary Thomas [Wed, 30 Oct 2013 16:09:25 +0000 (10:09 -0600)]
core-image-basic.bb: Allow user extensions
Allow the user to provide additional packages to this image.
This lets core-image-basic behave like all other core-image*
recipes (which do support CORE_IMAGE_EXTRA_INSTALL), as well
as match the documentation which suggests this as the mode to
extend any core-image* image.
v2 - drop redundant setting of CORE_IMAGE_EXTRA_INSTALL
Richard Purdie [Tue, 29 Oct 2013 11:14:13 +0000 (11:14 +0000)]
recipes: Remove PR = r0 from all recipes
Remove all PR = "r0" from all .bb files in oe-core. This was done
with the command sed -e '/^PR.*=.*r0\"/d' recipes*/*/*.bb -i
We've switching to the PR server, PR bumps are no longer needed and
this saves people either accidentally bumping them or forgetting to
remove the lines (r0 is the default anyway).
Qiang Chen [Mon, 28 Oct 2013 05:15:54 +0000 (13:15 +0800)]
openssl: create package for openssl configuration file
* Add the openssl-conf package to the list of packages to
be created. This package contains the openssl.cnf file
which is used by both the openssl executable in the
openssl package and the libcrypto library.
* This is to avoid messages like:
WARNING: can't open config file: /usr/lib/ssl/openssl.cnf
* When running "openssl req" to request and generate a certificate
the command will fail without the openssl.cnf file being
installed on the target system.
* Made this package an RRECOMMENDS for libcrypto since:
* libcrypto is a RDEPENDS for the openssl package
* Users can specify a configuration file at another
location so it is not stricly required and many
commands will work without it (with warnings)
Lu Chong [Tue, 22 Oct 2013 09:40:22 +0000 (17:40 +0800)]
dbus: no messages of status command print
/etc/init.d/dbus-1 use "set -e" to let the script exit when any command failes.
This will cause "/etc/init.d/dbus-1 status" command can't display messages when dbus is stopped.
Tom Rini [Tue, 22 Oct 2013 16:37:10 +0000 (12:37 -0400)]
udev: Update touchscreen rule for ID_INPUT_TOUCHSCREEN
Since udev 174 udev has been running input_id as a built-in command and
setting this value in the environment for touchscreens. Use this logic
to detect when to make a touchscreen0 symlink.
Cristian Iorga [Tue, 22 Oct 2013 14:10:03 +0000 (17:10 +0300)]
connman: upgrade to 1.19
Improvements:
- On startup keep interfaces already configured
with static IPv4 addresses if there is a
service configuration file containing
the very same static values. If not,
take the interface down and flush
the old configuration as before (Jukka Rissanen).
- Handle FallbackNameservers properly;
use them when no other nameservers have been
configured for a service (Patrik Flykt).
Signed-off-by: Roy Li <rongqing.li@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Roy Li <rongqing.li@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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>
Ming Liu [Mon, 21 Oct 2013 00:41:34 +0000 (08:41 +0800)]
strace: remove += assignment of a OVERRIDES variable
In some cases, it's unfit to use "+=" in a conditional appending, we would
end up with the variable being set rather than being appended, which is not
it mean to.
Signed-off-by: Ming Liu <ming.liu@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Konrad Scherer [Mon, 21 Oct 2013 20:13:11 +0000 (16:13 -0400)]
pigz: Add pigz to buildtools tarball
When using the tar executable in the buildtools, tar will execute
gzip. If this happens before zlib-native is built, then the gzip
on the host will be used and can fail if the libz in the buildtools
is not compatible. Adding pigz to the build tools avoids this host
contamination.
Hongxu Jia [Mon, 21 Oct 2013 11:37:22 +0000 (19:37 +0800)]
debugedit: fix segment fault while file's bss offset have a large number
While ELF_C_RDWR_MMAP was used, elf_begin invoked mmap() to map file
into memory. While the file's bss Offset has a large number, elf_update
caculated file size by __elf64_updatenull_wrlock and the size was
enlarged.
In this situation, elf_update invoked ftruncate to enlarge the file,
and memory size (elf->maximum_size) also was incorrectly updated.
There was segment fault in elf_end which invoked munmap with the
length is the enlarged file size, not the mmap's length.
Before the above operations, invoke elf_begin/elf_update/elf_end
with ELF_C_RDWR and ELF_F_LAYOUT set to enlarge the above file, it
could make sure the file is safe for the following elf operations.
Since rpm-build requires perl, this caused a number of build failures
when the rpm-build package was attempted to be used since it references
/usr/bin/perl. This commit restores the previous contents of the rpm
package.
Jacob Kroon [Sun, 27 Oct 2013 09:20:29 +0000 (10:20 +0100)]
update-rc.d.bbclass: Fix host/target test in postinst
When running the postinst script I get a shell warning:
sh: argument expected
and the service is never stopped. This patch fixes the warning
message and stops the service.
Patch v2: Hans Beckérus pointed out that the patch is not correct.
This version uses the syntax proposed by Hans. I've tested
that the postinst script works correctly when run on the target,
both when the init script exists and when it doesn't exist.
Roy Li [Tue, 29 Oct 2013 04:54:03 +0000 (12:54 +0800)]
pseudo: fix library path in FILES_${PN}
libpseudo.so is always installed into ${prefix}/lib/, not ${libdir},
so fix these paths; and skip libdir WARN_QA checking to ignore the
warning in 64bit and multilib enabled system
Laurentiu Palcu [Mon, 28 Oct 2013 20:46:20 +0000 (22:46 +0200)]
nativesdk-qt4-tools: create qt.conf file
When installing the SDK to another location than the default one, qmake
will look for libraries, headers, etc. in the default location. That's
because the paths are hard-coded in the binary itself. Luckily, QT
allows to override this using a qt.conf file installed in the same
directory with the application executable. However, we already have a
patch that allows for the installation of qt.conf in another place and
read the location from QT_CONF_PATH environment variable.
Hence, install qt.conf in ${sysconfdir}. This will allow other apps, that
use QLibraryInfo class, to find it.
Ross Burton [Mon, 28 Oct 2013 17:52:31 +0000 (17:52 +0000)]
xorg-proto-common: set UNKNOWN_CONFIGURE_WHITELIST
This include adds configure options globally but not all X libraries support
them, so to avoid unknown-configure-option warnings add them to the whitelist.
Also change the options from --enable-foo=no to --disable-foo as they're clearer
and the whitelist would have to contain --enable-foo.
projects / thirdparty / openembedded / openembedded-core-contrib.git / log
