Re: [oe] build errors in openssl-native
Pierluigi Passaro pierluigi.passaro at phoenixsoftware.it writes: Hi Wilder, try dropping libdeps-first.patch in openssl-native recipe. It does not allow openssl-native build on ubuntu 11.10. Regards Pierlugi This worked. I had the same issue (while doing a 'bitbake helloworld-image' for beagleboard angstrom under Ubuntu 11.10 'oneiric'), with bitbake 1.12.0 and openembedded 2011.03 (from git). I edited $OEBASE/oe/openembedded/recipes/openssl/openssl-native_1.0.0d.bb and removed the reference to libdeps-first.patch in the SRC_URI section. Many thanks for the help - getting started with OE/bitbake can be a bit intimidating for the uninitiated! Krgds, M ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Performance measurement: Building openembedded-core with and without overclocking on C-i7 2600K
В сообщении от 18 октября 2011 10:03:25 автор Ulf Samuelsson написал: Also what happens if it it built on a fast SSD, or even a RAMdisk? Our main build server has two Xeons X5670 with 96 GB of RAM. It's running 24×7 cyclicly doing clean isolated builds of all our OE projects (currently five). Isolated means that the the actual build is done inside a container (LXC) with no network available at all, that is a requirement for all our builds, to be able to take one tarball of sources, one tarball of OE tree and build the project somewhere in a nuclear bunker. The system is configured in such way that container is located on tmpfs (with size of 50 GB). The most complex build takes about hour and a half on this system occupying about 45 GB of space in a ramdisk. So today I tried to get some RAM vs. Linux cache statistics and switched this mount point over to newly created 60 GB LVM partition with ext4 on RAID0 array consisting of two SAS 15K drives. The system made builds for three projects is this configuration and I see no difference at all, usual 1-2 minutes deviation. Granted, the system has quite powerful disks (RAID array gives about 380 MB/sec on hdparm) and things might be a little different on plain SATA drives, but frankly I'd expected to see the difference anyway since there are lots of small files involved in a build. Maybe I should try to further degrade the disk system by creating some encrypted volume inside LVM, but still from what I see Linux caching and buffering works good enough, just give it as much RAM as you can. But then also what you'll get from RAM or disk or even CPU upgrade depends on what type of build you have. Upgrading developers build servers from pair of 4-core Opterons (don't remember exact model) with 8 GB of RAM to pair of Xeons E5620 with 24 GB of RAM with comparable disks gave about 20-30% of build time reduction for one project and 50% for another. But that builds are not isolated and use icecc cluster with all build servers available to the cluster, maybe that helps also in our situation. -- http://roman.khimov.ru mailto: ro...@khimov.ru gpg --keyserver hkp://subkeys.pgp.net --recv-keys 0xE5E055C3 signature.asc Description: This is a digitally signed message part. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] Performance measurement: Building openembedded-core with and without overclocking on C-i7 2600K
2011-10-23 19:50, Roman Khimov skrev: ? ? ?? 18 ??? 2011 10:03:25 ? Ulf Samuelsson ???: Also what happens if it it built on a fast SSD, or even a RAMdisk? Our main build server has two Xeons X5670 with 96 GB of RAM. It's running 24×7 cyclicly doing clean isolated builds of all our OE projects (currently five). Isolated means that the the actual build is done inside a container (LXC) with no network available at all, that is a requirement for all our builds, to be able to take one tarball of sources, one tarball of OE tree and build the project somewhere in a nuclear bunker. The system is configured in such way that container is located on tmpfs (with size of 50 GB). The most complex build takes about hour and a half on this system occupying about 45 GB of space in a ramdisk. So today I tried to get some RAM vs. Linux cache statistics and switched this mount point over to newly created 60 GB LVM partition with ext4 on RAID0 array consisting of two SAS 15K drives. The system made builds for three projects is this configuration and I see no difference at all, usual 1-2 minutes deviation. Granted, the system has quite powerful disks (RAID array gives about 380 MB/sec on hdparm) and things might be a little different on plain SATA drives, but frankly I'd expected to see the difference anyway since there are lots of small files involved in a build. Maybe I should try to further degrade the disk system by creating some encrypted volume inside LVM, but still from what I see Linux caching and buffering works good enough, just give it as much RAM as you can. But then also what you'll get from RAM or disk or even CPU upgrade depends on what type of build you have. Upgrading developers build servers from pair of 4-core Opterons (don't remember exact model) with 8 GB of RAM to pair of Xeons E5620 with 24 GB of RAM with comparable disks gave about 20-30% of build time reduction for one project and 50% for another. But that builds are not isolated and use icecc cluster with all build servers available to the cluster, maybe that helps also in our situation. Thanks, I tried installing 32 bit Ubuntu 11.10 on a HDD and got results, which are very close to the results of 64 bit ubuntu 11.10, but when I tried hdparm the 32 bit system had 50 MB/s and the 64 bit system had 100-110 MB/s so they are not comparable. Also tried putting tmp/sysroots on a 3 GB tmpfs, and that only made the build a couple of minutes faster on a 1 hour build. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel -- Best Regards Ulf Samuelsson ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[oe] [PATCH meta-oe] memtester: Import from OE classic
Added LIC_FILES_CHKSUM
Signed-off-by: Joel A Fernandes joelag...@ti.com
---
This package is required by the beaglebone-tester
.../memtester/files/Makefile.patch | 15 +++
.../recipes-benchmark/memtester/memtester_4.1.3.bb | 27
2 files changed, 42 insertions(+), 0 deletions(-)
create mode 100644 meta-oe/recipes-benchmark/memtester/files/Makefile.patch
create mode 100644 meta-oe/recipes-benchmark/memtester/memtester_4.1.3.bb
diff --git a/meta-oe/recipes-benchmark/memtester/files/Makefile.patch
b/meta-oe/recipes-benchmark/memtester/files/Makefile.patch
new file mode 100644
index 000..57a0464
--- /dev/null
+++ b/meta-oe/recipes-benchmark/memtester/files/Makefile.patch
@@ -0,0 +1,15 @@
+Index: memtester-4.0.5/Makefile
+===
+--- memtester-4.0.5.orig/Makefile 2005-03-14 06:02:30.0 -0800
memtester-4.0.5/Makefile 2006-07-08 23:53:42.0 -0700
+@@ -24,8 +24,8 @@
+ auto-ccld.sh: \
+ conf-cc conf-ld warn-auto.sh
+ ( cat warn-auto.sh; \
+- echo CC=\'`head -1 conf-cc`\'; \
+- echo LD=\'`head -1 conf-ld`\' \
++ echo CC=\'`head -n 1 conf-cc`\'; \
++ echo LD=\'`head -n 1 conf-ld`\' \
+ ) auto-ccld.sh
+
+ compile: \
diff --git a/meta-oe/recipes-benchmark/memtester/memtester_4.1.3.bb
b/meta-oe/recipes-benchmark/memtester/memtester_4.1.3.bb
new file mode 100644
index 000..9f4e53e
--- /dev/null
+++ b/meta-oe/recipes-benchmark/memtester/memtester_4.1.3.bb
@@ -0,0 +1,27 @@
+SECTION = console/utils
+DESCRIPTION = Utility to test for faulty memory subsystem
+LICENSE = GPLv2
+
+LIC_FILES_CHKSUM = file://COPYING;md5=0636e73ff0215e8d672dc4c32c317bb3
+
+SRC_URI =
http://pyropus.ca/software/memtester/old-versions/memtester-${PV}.tar.gz;
+SRC_URI += file://Makefile.patch
+
+SRC_URI[md5sum] = e562451620cf5343016950462bc0dc38
+SRC_URI[sha256sum] =
ac56f0b6d6d6e58bcf2a3fa7f2c9b29894f5177871f21115a1906c535106acf6
+
+S = ${WORKDIR}/memtester-${PV}
+
+do_compile () {
+ echo '${CC} ${CFLAGS} -DPOSIX -c' conf-cc
+ echo '${CC} ${LDFLAGS}' conf-ld
+ oe_runmake
+}
+
+do_install () {
+ install -d ${D}${bindir}
+ install -d ${D}${mandir}/man8
+ install -m 0755 memtester ${D}${bindir}/
+ install -m 0755 memtester.8 ${D}${mandir}/man8/
+}
+
--
1.7.0.4
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
