Richard Purdie [Mon, 16 Jul 2012 14:52:19 +0000 (14:52 +0000)]
useradd.bbclass: Fix for multilib builds
The class adds a setscene dependency on base-passwd as well as adds this to DEPENDS.
The DEPENDS version will be auso-converted to include MLPREFIX whilst the setscene
dependency will not. This result in errors about non-existent tasks.
This patch ensures MLPREFIX is added when it is needed and fixes various
build failures. Whether we should have two base-passwd recipes in a multilib
system is a question which would need to be addressed by future changes.
Scott Rifenbark [Mon, 16 Jul 2012 18:12:26 +0000 (11:12 -0700)]
documentation: Converted FAQ appendix to a chapter
As part of moving the reference manual to a real reference manual I
am removing the "appendix" classification and having everthing be
a chapter. I changed the "faq" appendix to a chapter and
made sure any references in the doc set use the proper term now
(chapter).
Scott Rifenbark [Mon, 16 Jul 2012 18:08:02 +0000 (11:08 -0700)]
documentation/poky-ref-manual: Converted ref-varlocality to chapter.
As part of moving the reference manual to a real reference manual I
am removing the "appendix" classification and having everthing be
a chapter. I changed the "ref-varlocality" appendix to a chapter and
made sure any references in the doc set use the proper term now
(chapter).
Scott Rifenbark [Mon, 16 Jul 2012 18:02:19 +0000 (11:02 -0700)]
documentation: converted ref-variables-gloss to chapter.
As part of moving the reference manual to a real reference manual I
am removing the "appendix" classification and having everthing be
a chapter. I changed the "ref-varibales-gloss" appendix to a chapter and
made sure any references in the doc set use the proper term now
(chapter).
Scott Rifenbark [Mon, 16 Jul 2012 17:53:16 +0000 (10:53 -0700)]
documentation: converted ref-images and ref-features to chapters
As part of moving the reference manual to a real reference manual I
am removing the "appendix" classification and having everthing be
a chapter. I changed the "ref-imagese" and "ref-features" appendices
to chapters and made any references in the doc set use the proper
term now (chapter).
Scott Rifenbark [Mon, 16 Jul 2012 17:31:19 +0000 (10:31 -0700)]
documentation/poky-ref-manual: Converted ref-classes to chapter
As part of moving the reference manual to a real reference manual I
am removing the "appendix" classification and having everthing be
a chapter. I changed the "ref-classes" appendix to a chapter and
made sure any references in the doc set use the proper term now
(chapter).
Scott Rifenbark [Mon, 16 Jul 2012 17:19:15 +0000 (10:19 -0700)]
documentation/poky-ref-manual: Converted ref-bitbake to chapter
As part of moving the reference manual to a real reference manual I
am removing the "appendix" classification and having everthing be
a chapter. I changed the "ref-bitbake" appendix to a chapter and
made sure the single in the doc set use the proper term now
(chapter).
Scott Rifenbark [Mon, 16 Jul 2012 17:10:27 +0000 (10:10 -0700)]
documentation/poky-ref-manual: Re-cast structure appendix as chapter
As part of moving the reference manual to a real reference manual I
am removing the "appendix" classification and having everthing be
a chapter. I changed the "ref-structure" appendix to a chapter and
made sure the two references in the doc set use the proper term now
(chapter).
Scott Rifenbark [Fri, 13 Jul 2012 21:17:33 +0000 (14:17 -0700)]
documentation/poky-ref-manual: Removed artifacts for dev chapter
Removing the Development chapter resulted in some links being
re-defined to go to the YP Development manual. Also, the
poky-ref-manual.xml file had to be altered to not include the
chapter. Any sort of residual cleanup needed as a result of
getting rid of this chapter is handled in this commit.
Scott Rifenbark [Fri, 13 Jul 2012 21:12:10 +0000 (14:12 -0700)]
documentation/poky-ref-manual/development.xml: Deleted development chapter
The Development chapter has been emptied out so it is now deleted from
the reference manual. All relevant topics now reside in the YP
Development Manual.
Added the section "Using an External SCM" to the "Common Tasks"
chapter. This information was formerly in the YP Reference Manual
in the old development chapter.
Removed the "Development Using a Development Shell" section. This
section was moved to the YP Development manual into the "Common
Development Models" chapter.
I inserted the section "Using a Development Shell" into the "Common
Development Models" chapter. This information was formerly in the
YP Reference Manual and is being moved out to help the ref manual
become a truer reference manual.
Kang Kai [Tue, 17 Jul 2012 06:58:52 +0000 (14:58 +0800)]
bitbake: hob2: add elf to hcc supported image types
[Yocto #2709]
OE Core Commit c9b01af84b64edba056f959c349895e0698324e6 add elf image
type. This will cause hob build image failed.
Add elf to hcc supoorted image types to fix this issue.
bitbake: siggen.py: Insure .siginfo files writes into shared sstate cache are atomic
Use tempfile.mkstemp to create a temporary file in the sstate dir and move it
into place after closing. The previous code would fail in the chmod() if two
users were running jobs that touched the same signature file.
Nitin A Kamble [Thu, 3 May 2012 17:26:35 +0000 (10:26 -0700)]
tar: fix build with automake 1.12.x
automake 1.12.x automatically deletes empty directories, so
the additional rmdir from the do_install_append fails.
cleanup the do_install_append for automake 1.12.x
Avoid this error:
| rmdir: failed to remove `/srv/home/nitin/builds/build-gcc47/tmp/work/i586-poky-linux/tar-1.26-r1/image/usr/sbin/': No such file or directory
NOTE: package tar-1.26-r1: task do_install: Failed
automake 1.12.x automatically deletes empty directories, so
the additional rmdir from the do_install_append fails.
cleanup the do_install_append for automake 1.12.x
Avoids this build issue:
| rmdir: failed to remove `/srv/home/nitin/builds2/build0/tmp/work/i586-poky-linux/gpgme-1.3.2-r0/image/usr/libexec': No such file or directory
| ERROR: Function failed: do_install
Nitin A Kamble [Thu, 3 May 2012 20:30:20 +0000 (13:30 -0700)]
libfm: fix build with automake 1.12.x
automake 1.12.x automatically deletes empty directories, so
the additional rmdir from the do_install_append fails.
cleanup the do_install_append for automake 1.12.x
Avoids this build issue:
| rmdir: failed to remove `/srv/home/nitin/builds/build-gcc47/tmp/work/i586-poky-linux/libfm-0.1.17-r4/image/usr/lib/gio/modules/': No such file or directory
NOTE: package libfm-0.1.17-r4: task do_install: Failed
Nitin A Kamble [Thu, 3 May 2012 18:12:34 +0000 (11:12 -0700)]
xf86-video-vmware: fix build with automake 1.12.x
automake 1.12.x automatically deletes empty directories, so
the additional rmdir from the do_install_append fails.
cleanup the do_install_append for automake 1.12.x
Fixes this build issue:
| rmdir: failed to remove
`/srv/home/nitin/builds/build-gcc47/tmp/work/i586-poky-linux/xf86-video-vmware-2_12.0.1-r17.1/image/usr/bin':
No such file or directory
NOTE: package xf86-video-vmware-2_12.0.1-r17.1: task do_install: Failed
Nitin A Kamble [Thu, 3 May 2012 17:39:02 +0000 (10:39 -0700)]
telepathy-glib: fix build with automake 1.12.x
automake 1.12.x automatically deletes empty directories, so
the additional rmdir from the do_install_append fails.
cleanup the do_install_append for automake 1.12.x
avoid this issue:
| rmdir: failed to remove `/srv/home/nitin/builds/build-gcc47/tmp/work/i586-poky-linux/telepathy-glib-0.18.1-r0/image/usr/bin': No such file or directory
NOTE: package telepathy-glib-0.18.1-r0: task do_install: Failed
Nitin A Kamble [Thu, 3 May 2012 17:29:32 +0000 (10:29 -0700)]
libgcrypt: fix build with automake 1.12.x
automake 1.12.x automatically deletes empty directories, so
the additional rmdir from the do_install_append fails.
cleanup the do_install_append for automake 1.12.x
avoid this issue:
| rmdir: failed to remove `/srv/home/nitin/builds/build-gcc47/tmp/work/i586-poky-linux/libgcrypt-1.5.0-r0/image/usr/sbin': No such file or directory
NOTE: package libgcrypt-1.5.0-r0: task do_install: Failed
This patch fixes building this tool in cross environment
It uses tools such as CC, HOST_CC, I386_CC etc.
and as long as you are building native it does not
matter since they all are same namely 'gcc' but
in cross compiling that wont work. So we make the
makefiles and configure scripts aware of that fact
Upstream hosts this program in a svn repo. So change
the SRC_URI to official svn repo. With git we were
checking out a lot more that just mkelfimage which
is not required.
There were unpackaged empty directories too so
we make sure they are removed as well.
kxgettext.o is generated when building ppc kernels
so we end up with packaging errors like
> ERROR: QA Issue: Architecture did not match (20 to 62) on
> /work/virtex5-poky-linux/linux-xilinx-2.6.38-r00/packages-split/kernel-dev/usr/src/kernel/scripts/kconfig/kxgettext.o
This patch adds a fix where arm endianness is detected correctly
secondly it adds a missing dependency on libatomics-ops
which was found when build in clean tmpdir and populating
it from a valid sstate.
lib/oe/sstatesig.py: Exclude git-native from sstate checksum
gcc exposed this issue where cross gcc recipes were not having
same task checksums as libgcc or gcc-runtime the target recipes
which use same shared workdir and it was triggering the unpack
fetch and patch tasks to reexecute and hence the trouble
Now that we have more than 1 package to consider lets combine
the check
These patches are backport from gcc mainline
they fix issues where eglibc was not compilable
for e5500+ due to missing vector intrinsics
It obsoletes the existing e5500 patch
do_headerfix task is essentially editing configuration
headers in sources which can well be maintained as a
patch which is easier to spot errors (if any) than
dynamically edited source tree
pam_unix_acct.c: In function '_unix_run_verify_binary':
pam_unix_acct.c:97:19: error: storage size of 'rlim' isn't known
pam_unix_acct.c:106:19: error: 'RLIMIT_NOFILE' undeclared (first use in
this function)
pam_unix_acct.c:106:19: note: each undeclared identifier is reported
only once for each function it appears in
1.49.0 is not buildable with eglibc 2.16 since
it exposes a define TIME_UTC which is also used
in boost until 1.50.0 when it was renamed to
TIME_UTC_ so instead of porting needed patches
we upgrade boost to latest release
gettext,m4,augeas,gnutls: Account for removal of gets in eglibc 2.16
These recipes use gnulib which needs this change to use gets
when its defined and not otherwise. Until that change goes into
gnulib and then all these package upgrade gnulib in their sourcebase
we patch them
Martin Jansa [Mon, 16 Jul 2012 08:25:49 +0000 (10:25 +0200)]
libx11: fix makekeys build
* on hosts without libx11 installed it fails with
| makekeys.c:33:27: fatal error: X11/Xresource.h: No such file or directory
since oe-core rev 52d4ff7b35602faa52360a3e7a800891ef60c739
* upstream added -I$(top_srcdir)/include in 24283d40b1e4314c6647dda49d2a159833341a8b
to ensure that right Xresource.h version is used, but we're building
makekeys outside source tree (x11_disable_makekeys.patch), so we need
to pass -I${S}/include in our makekeys build too
* building makekeys outside source tree isn't probably needed anymore
and recipes should be updated to reflect that, upstream fixes:
https://bugs.freedesktop.org/show_bug.cgi?id=22584
http://cgit.freedesktop.org/xorg/lib/libX11/commit/src/util/Makefile.am?id=b2487d07f7b355f230a56e32c763acd08862735c
http://cgit.freedesktop.org/xorg/lib/libX11/commit/src/util/Makefile.am?id=24283d40b1e4314c6647dda49d2a159833341a8b
/home/kraj/work/angstrom/sources/openembedded-core/build/tmp-eglibc/work/armv5te-oe-linux-gnueabi/gdb-7.4.1-r0.0/gdb-7.4.1/gdb/linux-nat.h:79:18:
error: field 'siginfo' has incomplete type
mirrors: Add debian archive snapshot mirrors to search list
I ran across this problem when apt 0.7.14 was not fetchable
from regular debian mirrors and existing snapshot mirror
did not have it either since we did not use proper syntax
so it was not hitting that.
Ting Liu [Fri, 13 Jul 2012 05:14:25 +0000 (00:14 -0500)]
lsof: define linux C library type when using eglibc
lsof tries to compile a temp c source file and execute the binary to
determine linux C library type (file Configure, line 2689-2717).
It is inpracticable for cross-compilation and may have build issue on
some distros since it depends on host settings.
Fix below error when building for 64bit target on 64bit host:
[...]
| dsock.c:481:44: error: 'TCP_LISTEN' undeclared (first use in this function)
| dsock.c:482:45: error: 'TCP_CLOSING' undeclared (first use in this function)
[...]
| make: *** [dsock.o] Error 1
The actual issue exists in do_configure:
[...]
Testing C library type with cc ... done
Cannot determine C library type; assuming it is not glibc.
Which is in turn caused by missing 'gnu/stubs-32.h" when compiling
the temp c source file on host:
[...]
fatal error: gnu/stubs-32.h: No such file or directory compilation terminated.
Richard Purdie [Thu, 12 Jul 2012 15:25:47 +0000 (16:25 +0100)]
crosssdk/nativesdk: Ensure EXTRA_OECONF_FPU is unset
If EXTRA_OECONF_FPU is left set, certain ARM variables related to hard-float
can get pulled in and trigger rebuilds of the crosssdk code. The best solution
is to simply force the variable to a known correct value for the SDK targets
currently supported in the same way as TARGET_FPU.
There is some slight rearrangement of the gcc code to ensure the variable is
always used to call the fpu function.
Richard Purdie [Thu, 12 Jul 2012 15:18:23 +0000 (16:18 +0100)]
sstate.bbclass: Move crosssdk before cross to ensure correct variables are set
There was a bug showing up where the crosssdk recipes were being installed as machine
specific in the sstate-control directory. This turned out to be due to the architecture
fields used by sstate being set incorrectly. The problem is that the crosssdk inherits
the cross class. It therefore needs to be listed in this if statement block before
the cross check, not after.
This should resolve some package architecture issue of crosssdk sstate files.
sysvinit-inittab_2.88dsf.bb: Allow multiple serial port consoles to be defined
Set SERIAL_CONSOLES if you want to define multiple serial consoles, also if
you need to check for the presence of the serial consoles you can also define
SERIAL_CONSOLES_CHECK to determine if these are present when you boot. This
will prevent error message that pop up when the serial port is not present.
Andrei Gherzan [Thu, 12 Jul 2012 18:05:56 +0000 (21:05 +0300)]
image_types.bbclass: Default XZ_COMPRESSION_LEVEL to -e -6
Having XZ_COMPRESSION_LEVEL on -e -9 and -T 0 will make xz eat more
than 6Gb memory. Reduce this to -6 to make xz to use about 471Mb
on the tested machine.
Andrei Gherzan [Thu, 12 Jul 2012 14:31:54 +0000 (17:31 +0300)]
image_types.bbclass: Fix COMPRESS_CMD for xz to redirect compressed data to file
Having -c modifier makes xz to output the compressed data to stdout. In this
way the needed data will be in the do_rootfs log.
Redirect data to ${IMAGE_NAME}.rootfs.${type}.xz .
Xin Ouyang [Thu, 21 Jun 2012 07:13:54 +0000 (15:13 +0800)]
cpan.bbclass: Fix CCFLAGS.
We should not just replace CCFLAGS with CFLAGS while compiling, because
this may cause run-time errors with perl's DynaLoader.pm.
Tested on qemux86 with new libnet-libidn-perl bb recipe:
root@qemux86:~# perl -e "use Net::LibIDN"
Not a CODE reference at /usr/lib/perl/5.14.2//DynaLoader.pm line 213.
END failed--call queue aborted at /usr/lib/perl/vendor_perl/5.14.2//Net/LibIDN.pm line 213.
Compilation failed in require at -e line 1.
BEGIN failed--compilation aborted at -e line 1.
Recently the tarball has been changing due the fact it gets rebuilt
nightly and timestamps are getting updated and changed internal to
the tarball. Moving back to SVN to try and address this.
Paul Eggleton [Mon, 9 Jul 2012 12:38:39 +0000 (13:38 +0100)]
classes/rootfs_deb: use more reliable check for package existence
It turns out "apt-cache showpkg" does return some information when a
package does not exist but another package recommends it, which can
occur for empty *-dev packages; so use "apt-cache policy" with a
different line count instead.
Peter Seebach [Wed, 11 Jul 2012 20:31:55 +0000 (15:31 -0500)]
package.bbclass: Allow overriding of debugedit starting path
In the usual case, the computed path used for debugedit to fix
up path references for the target filesystem is correct. However,
prebuilt binary components, such as prebuilt toolchains, can
have debug paths that do not reflect paths within the local
build directory. Providing an override lets us continue to use
the standard debugedit logic in package.bbclass.