[yocto] [meta-security][PATCH 2/2] Bastille: Remove dependency on lib-perl
Bastille never uses more than the minimal functionality provided by the
'lib' module, just pre-pending a named directory to @INC (and, optionally,
the directory with a ${archname}/auto appended to it). Lighten this a bit
by updating the Bastille code base and remove lib-perl from meta-security
entirely since it no longer serves any purpose.
Signed-off-by: Joe MacDonald
---
recipes-security/bastille/bastille_3.2.1.bb|3 +-
...-lib-remove-dependency-on-lib-perl-module.patch | 495
recipes-security/perl/lib-perl_0.63.bb | 28 --
3 files changed, 497 insertions(+), 29 deletions(-)
create mode 100644
recipes-security/bastille/files/0001-lib-remove-dependency-on-lib-perl-module.patch
delete mode 100644 recipes-security/perl/lib-perl_0.63.bb
diff --git a/recipes-security/bastille/bastille_3.2.1.bb
b/recipes-security/bastille/bastille_3.2.1.bb
index d506399..20a331a 100644
--- a/recipes-security/bastille/bastille_3.2.1.bb
+++ b/recipes-security/bastille/bastille_3.2.1.bb
@@ -6,7 +6,7 @@ LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://${S}/COPYING;md5=c93c0550bd3173f4504b2cbd8991e50b"
# Bash is needed for set +o privileged (check busybox), might also need ncurses
DEPENDS = "virtual/kernel"
-RDEPENDS_${PN} = "perl bash tcl perl-module-getopt-long perl-module-text-wrap
lib-perl perl-module-file-path perl-module-mime-base64 perl-module-file-find
perl-module-errno perl-module-file-glob perl-module-tie-hash-namedcapture
perl-module-file-copy perl-module-english perl-module-exporter perl-module-cwd
libcurses-perl coreutils"
+RDEPENDS_${PN} = "perl bash tcl perl-module-getopt-long perl-module-text-wrap
perl-module-file-path perl-module-mime-base64 perl-module-file-find
perl-module-errno perl-module-file-glob perl-module-tie-hash-namedcapture
perl-module-file-copy perl-module-english perl-module-exporter perl-module-cwd
libcurses-perl coreutils"
FILES_${PN} += "/run/lock/subsys/bastille"
inherit allarch module-base
@@ -32,6 +32,7 @@ SRC_URI =
"http://sourceforge.net/projects/bastille-linux/files/bastille-linux/3
file://edit_usage_message.patch \
file://organize_distro_discovery.patch \
file://do_not_apply_config.patch \
+ file://0001-lib-remove-dependency-on-lib-perl-module.patch \
"
SRC_URI[md5sum] = "df803f7e38085aa5da79f85d0539f91b"
diff --git
a/recipes-security/bastille/files/0001-lib-remove-dependency-on-lib-perl-module.patch
b/recipes-security/bastille/files/0001-lib-remove-dependency-on-lib-perl-module.patch
new file mode 100644
index 000..a3ec88d
--- /dev/null
+++
b/recipes-security/bastille/files/0001-lib-remove-dependency-on-lib-perl-module.patch
@@ -0,0 +1,495 @@
+From 23126d70d69251b735bd8f0e43c3b7c299e7ab0f Mon Sep 17 00:00:00 2001
+From: Joe MacDonald
+Date: Thu, 19 Sep 2013 10:16:53 -0400
+Subject: [PATCH] lib: remove dependency on lib-perl module
+
+The perl 'lib' module isn't really necessary based on the usage pattern in
+Bastille, so remove the dependency on it.
+
+Upstream-Status: Submitted [SourceForge project:
https://sourceforge.net/p/bastille-linux/bugs/160/]
+
+Signed-off-by: Joe MacDonald
+---
+ Bastille/AccountSecurity.pm |8 +++-
+ Bastille/Apache.pm |8 +++-
+ Bastille/BootSecurity.pm |8 +++-
+ Bastille/ConfigureMiscPAM.pm |8 +++-
+ Bastille/DNS.pm |8 +++-
+ Bastille/DisableUserTools.pm |8 +++-
+ Bastille/FTP.pm |8 +++-
+ Bastille/FilePermissions.pm |8 +++-
+ Bastille/IOLoader.pm |8 +++-
+ Bastille/Logging.pm |8 +++-
+ Bastille/MiscellaneousDaemons.pm |8 +++-
+ Bastille/OSXFirewall.pm |8 +++-
+ Bastille/PSAD.pm |8 +++-
+ Bastille/Printing.pm |8 +++-
+ Bastille/RemoteAccess.pm |8 +++-
+ Bastille/SecureInetd.pm |8 +++-
+ Bastille/Sendmail.pm |8 +++-
+ Bastille/TMPDIR.pm |8 +++-
+ Bastille/TestDriver.pm | 12 +---
+ BastilleBackEnd | 10 +-
+ InteractiveBastille | 10 +-
+ RevertBastille | 10 +-
+ find_bastille_affected_files.pl |9 -
+ 23 files changed, 170 insertions(+), 25 deletions(-)
+
+diff --git a/Bastille/AccountSecurity.pm b/Bastille/AccountSecurity.pm
+index e0ebc8a..96e27fd 100644
+--- a/Bastille/AccountSecurity.pm
b/Bastille/AccountSecurity.pm
+@@ -3,7 +3,13 @@
+ # Licensed under the GNU General Public License, version 2
+
+ package Bastille::AccountSecurity;
+-use lib "/usr/lib";
++BEGIN {
++unshift (@INC,"/usr/lib");
++use Config;
++if (-e "/usr/lib/$Config{archname}/auto" ) {
++unshift (@INC,"/usr/lib/$Config{archname}/auto");
++}
++}
+
+
+ use Bastille::API;
+diff --git a/Bastille/Apache.pm
[yocto] how to use already provided kernel tar file of mini2440 with yocto project
sir/ma'm; Please tell me the way how to use already provided kernel tar file of mini2440 with yocto project. I want to use linux-2.6.32 provided with mini2440 board. With regards Rahul Ravi ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Is this a bug of binutils
Hi,
On Fri, Sep 20, 2013 at 02:45:24PM +0800, Li Zhijian wrote:
> Hi，all
>
> I got a big problem when using the cross-toolchain to compile a simple C
> program.
> This problem since 3ae71c74c71f13a390b21b4c3ead04e51aaa82b8
> which is to upgrade the binutils from 2.22 to 2.23.1
>
> what I do is as follows, any help or ideas ?
>
> I) Build my cross-toolchain
> # git clone http://git.yoctoproject.org/git/poky/.git
> # cd poky
> # git checkout 3ae71c74c71f13a390b21b4c3ead04e51aaa82b8 -b tcmode-default
> ...skip some steps...
> # bitbake meta-toolchain
> Loading cache: 100%
> ||
> ETA: 00:00:00
> Loaded 1122 entries from dependency cache.
>
> Build Configuration:
> BB_VERSION = "1.17.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "CentOS-6.3"
> TARGET_SYS = "x86_64-poky-linux"
> MACHINE = "qemux86-64"
> DISTRO = "poky"
> DISTRO_VERSION = "1.3+snapshot-20130912"
> TUNE_FEATURES = "m64"
> TARGET_FPU = ""
> meta
> meta-yocto
> meta-yocto-bsp = "tcmode-default:3ae71c74c71f13a390b21b4c3ead04e51aaa82b8"
>
> ..cost a long time..
> all of the build work successfully
>
> II) Install my cross-toolchain
> # ./poky-eglibc-x86_64-x86_64-toolchain-1.3+snapshot-20130912.sh
> Enter target directory for SDK (default: /opt/poky/1.3+snapshot):
> toolchain-1.3-tcmode-default
>
> III） compile a simple C program
> # cat test.c
> int main ()
> {
> printf("hello world\n");
> return 0;
> }
> # source toolchain-1.3-tcmode-default/environment-setup-x86_64-poky-linux
> # $CC -o test test.c -L tmp/sysroots/qemux86-64/usr/lib/ -lm
Technically, for this simple program, it's enough to do:
$CC -o test test.c
The $CC contains the sysroot option and the linker will automatically
prefix /lib and /usr/lib with the target sysroot. So, it should be able
to compile just fine.
The -L option just adds another search path for libraries which will be
searched before the default ones. So, it shouldn't be a problem.
Somehow, it looks like it tries to link against the host's libraries.
Before compiling, do a 'echo $CC' and make sure the --sysroot points to
the correct directory.
Laurentiu
> test.c: In function 'main':
> test.c:3:9: warning: incompatible implicit declaration of built-in function
> 'printf' [enabled by default]
> /yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
> skipping incompatible /lib/libc.so.6 when searching for /lib/libc.so.6
> /yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
> cannot find /lib/libc.so.6
> /yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
> skipping incompatible /usr/lib/libc_nonshared.a when searching for
> /usr/lib/libc_nonshared.a
> /yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
> cannot find /usr/lib/libc_nonshared.a
> collect2: error: ld returned 1 exit status
>
>
> #cat toolchain-1.3-tcmode-default/environment-setup-x86_64-poky-linux
> export
> PATH=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin:/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux:$PATH
> export
> PKG_CONFIG_SYSROOT_DIR=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-poky-linux
> export
> PKG_CONFIG_PATH=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-poky-linux/usr/lib/pkgconfig
> export
> CONFIG_SITE=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/site-config-x86_64-poky-linux
> export CC="x86_64-poky-linux-gcc -m64
> --sysroot=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-poky-linux"
> export CXX="x86_64-poky-linux-g++ -m64
> --sysroot=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-poky-linux"
> export CPP="x86_64-poky-linux-gcc -E -m64
> --sysroot=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-poky-linux"
> export AS="x86_64-poky-linux-as "
> export LD="x86_64-poky-linux-ld
> --sysroot=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-poky-linux"
> export GDB=x86_64-poky-linux-gdb
> export STRIP=x86_64-poky-linux-strip
> export RANLIB=x86_64-poky-linux-ranlib
> export OBJCOPY=x86_64-poky-linux-objcopy
> export OBJDUM
Re: [yocto] [poky] Is this a bug of binutils
On Fri, Sep 20, 2013 at 11:43:31AM +0300, Laurentiu Palcu wrote:
> Hi,
>
> On Fri, Sep 20, 2013 at 02:45:24PM +0800, Li Zhijian wrote:
> > Hi，all
> >
> > I got a big problem when using the cross-toolchain to compile a simple C
> > program.
> > This problem since 3ae71c74c71f13a390b21b4c3ead04e51aaa82b8
> > which is to upgrade the binutils from 2.22 to 2.23.1
Apparently I missed this... Make sure you checkout
0333796a6b167dd754806700d7f771dd4a74e4ab (binutils_2.23.1.bb: Correct
typo in enable-targets configure option). This might be your problem.
Laurentiu
> >
> > what I do is as follows, any help or ideas ?
> >
> > I) Build my cross-toolchain
> > # git clone http://git.yoctoproject.org/git/poky/.git
> > # cd poky
> > # git checkout 3ae71c74c71f13a390b21b4c3ead04e51aaa82b8 -b tcmode-default
> > ...skip some steps...
> > # bitbake meta-toolchain
> > Loading cache: 100%
> > ||
> > ETA: 00:00:00
> > Loaded 1122 entries from dependency cache.
> >
> > Build Configuration:
> > BB_VERSION = "1.17.0"
> > BUILD_SYS = "x86_64-linux"
> > NATIVELSBSTRING = "CentOS-6.3"
> > TARGET_SYS = "x86_64-poky-linux"
> > MACHINE = "qemux86-64"
> > DISTRO = "poky"
> > DISTRO_VERSION = "1.3+snapshot-20130912"
> > TUNE_FEATURES = "m64"
> > TARGET_FPU = ""
> > meta
> > meta-yocto
> > meta-yocto-bsp = "tcmode-default:3ae71c74c71f13a390b21b4c3ead04e51aaa82b8"
> >
> > ..cost a long time..
> > all of the build work successfully
> >
> > II) Install my cross-toolchain
> > # ./poky-eglibc-x86_64-x86_64-toolchain-1.3+snapshot-20130912.sh
> > Enter target directory for SDK (default: /opt/poky/1.3+snapshot):
> > toolchain-1.3-tcmode-default
> >
> > III） compile a simple C program
> > # cat test.c
> > int main ()
> > {
> > printf("hello world\n");
> > return 0;
> > }
> > # source toolchain-1.3-tcmode-default/environment-setup-x86_64-poky-linux
> > # $CC -o test test.c -L tmp/sysroots/qemux86-64/usr/lib/ -lm
> Technically, for this simple program, it's enough to do:
>
> $CC -o test test.c
>
> The $CC contains the sysroot option and the linker will automatically
> prefix /lib and /usr/lib with the target sysroot. So, it should be able
> to compile just fine.
>
> The -L option just adds another search path for libraries which will be
> searched before the default ones. So, it shouldn't be a problem.
>
> Somehow, it looks like it tries to link against the host's libraries.
>
> Before compiling, do a 'echo $CC' and make sure the --sysroot points to
> the correct directory.
>
> Laurentiu
>
> > test.c: In function 'main':
> > test.c:3:9: warning: incompatible implicit declaration of built-in function
> > 'printf' [enabled by default]
> > /yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
> > skipping incompatible /lib/libc.so.6 when searching for /lib/libc.so.6
> > /yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
> > cannot find /lib/libc.so.6
> > /yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
> > skipping incompatible /usr/lib/libc_nonshared.a when searching for
> > /usr/lib/libc_nonshared.a
> > /yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
> > cannot find /usr/lib/libc_nonshared.a
> > collect2: error: ld returned 1 exit status
> >
> >
> > #cat toolchain-1.3-tcmode-default/environment-setup-x86_64-poky-linux
> > export
> > PATH=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin:/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux:$PATH
> > export
> > PKG_CONFIG_SYSROOT_DIR=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-poky-linux
> > export
> > PKG_CONFIG_PATH=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-poky-linux/usr/lib/pkgconfig
> > export
> > CONFIG_SITE=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/site-config-x86_64-poky-linux
> > export CC="x86_64-poky-linux-gcc -m64
> > --sysroot=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-poky-linux"
> > export CXX="x86_64-poky-linux-g++ -m64
> > --sysroot=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-poky-linux"
> > export CPP="x86_64-poky-linux-gcc -E -m64
> >
Re: [yocto] Is this a bug of binutils
at 2013-9-20 16:43, Laurentiu Palcu wrote:
Hi,
On Fri, Sep 20, 2013 at 02:45:24PM +0800, Li Zhijian wrote:
Hi，all
I got a big problem when using the cross-toolchain to compile a simple C
program.
This problem since 3ae71c74c71f13a390b21b4c3ead04e51aaa82b8
which is to upgrade the binutils from 2.22 to 2.23.1
what I do is as follows, any help or ideas ?
I) Build my cross-toolchain
# git clone http://git.yoctoproject.org/git/poky/.git
# cd poky
# git checkout 3ae71c74c71f13a390b21b4c3ead04e51aaa82b8 -b tcmode-default
...skip some steps...
# bitbake meta-toolchain
Loading cache: 100%
||
ETA: 00:00:00
Loaded 1122 entries from dependency cache.
Build Configuration:
BB_VERSION = "1.17.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "CentOS-6.3"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "1.3+snapshot-20130912"
TUNE_FEATURES = "m64"
TARGET_FPU = ""
meta
meta-yocto
meta-yocto-bsp = "tcmode-default:3ae71c74c71f13a390b21b4c3ead04e51aaa82b8"
..cost a long time..
all of the build work successfully
II) Install my cross-toolchain
# ./poky-eglibc-x86_64-x86_64-toolchain-1.3+snapshot-20130912.sh
Enter target directory for SDK (default: /opt/poky/1.3+snapshot):
toolchain-1.3-tcmode-default
III） compile a simple C program
# cat test.c
int main ()
{
printf("hello world\n");
return 0;
}
# source toolchain-1.3-tcmode-default/environment-setup-x86_64-poky-linux
# $CC -o test test.c -L tmp/sysroots/qemux86-64/usr/lib/ -lm
Technically, for this simple program, it's enough to do:
$CC -o test test.c
i know that is enough and it is compiled OK
but in the case with -L option ,it is failed
The $CC contains the sysroot option and the linker will automatically
prefix /lib and /usr/lib with the target sysroot. So, it should be able
to compile just fine.
I haved source the toolchian environment which is installed by
./poky-eglibc-x86_64-x86_64-toolchain-1.3+snapshot-20130912.sh and i think
that would include all the correct environment value
# source toolchain-1.3-tcmode-default/environment-setup-x86_64-poky-linux
this file's detail is at the last of this thread
# echo $CC
x86_64-poky-linux-gcc -m64
--sysroot=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-poky-linux
the sysroot points to directory which is install by
./poky-eglibc-x86_64-x86_64-toolchain-1.3+snapshot-20130912.sh
this directory includes a basic target sysroot
The -L option just adds another search path for libraries which will be
searched before the default ones. So, it shouldn't be a problem.
Somehow, it looks like it tries to link against the host's libraries.
yes, it seems that ld try to link to host's libraries
but i am not sure that if i had do some wrong steps
Before compiling, do a 'echo $CC' and make sure the --sysroot points to
the correct directory.
you means that i must make --sysroot points to the sysroot build by myself
instead
of the sysroot provided by
poky-eglibc-x86_64-x86_64-toolchain-1.3+snapshot-20130912.sh ??
--
Best regards.
Li Zhijian
Laurentiu
test.c: In function 'main':
test.c:3:9: warning: incompatible implicit declaration of built-in function
'printf' [enabled by default]
/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
skipping incompatible /lib/libc.so.6 when searching for /lib/libc.so.6
/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
cannot find /lib/libc.so.6
/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
skipping incompatible /usr/lib/libc_nonshared.a when searching for
/usr/lib/libc_nonshared.a
/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
cannot find /usr/lib/libc_nonshared.a
collect2: error: ld returned 1 exit status
#cat toolchain-1.3-tcmode-default/environment-setup-x86_64-poky-linux
export
PATH=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin:/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux:$PATH
export
PKG_CONFIG_SYSROOT_DIR=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-poky-linux
export
PKG_CONFIG_PATH=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-poky-linux/usr/lib/pkgconfig
export
CONFIG
Re: [yocto] [poky] Is this a bug of binutils
at 2013-9-20 16:50, Laurentiu Palcu wrote:
On Fri, Sep 20, 2013 at 11:43:31AM +0300, Laurentiu Palcu wrote:
Hi,
On Fri, Sep 20, 2013 at 02:45:24PM +0800, Li Zhijian wrote:
Hi，all
I got a big problem when using the cross-toolchain to compile a simple C
program.
This problem since 3ae71c74c71f13a390b21b4c3ead04e51aaa82b8
which is to upgrade the binutils from 2.22 to 2.23.1
Apparently I missed this... Make sure you checkout
0333796a6b167dd754806700d7f771dd4a74e4ab (binutils_2.23.1.bb: Correct
typo in enable-targets configure option). This might be your problem.
Laurentiu
i am sorry，i don't understand what do you mean
in poky git tree，
3ae71c74c71f13a390b21b4c3ead04e51aaa82b8 is newer than
0333796a6b167dd754806700d7f771dd4a74e4ab
this checkout 0333796a6b167dd754806700d7f771dd4a74e4ab ， toolchain work fine
# git log
commit 3ae71c74c71f13a390b21b4c3ead04e51aaa82b8
Author: Khem Raj
Date: Wed Aug 8 10:33:41 2012 -0700
tcmode-default.inc: Use binutils 2.23.1
...skip...
commit 0333796a6b167dd754806700d7f771dd4a74e4ab
Author: Khem Raj
Date: Wed Aug 8 07:57:46 2012 -0700
oprofile: Include config.h before bfd.h
oprofile uses bfd.h from binutils which now in 2.23+ expects config.h
so lets include it
...skip...
--
Best regards.
Li Zhijian
what I do is as follows, any help or ideas ?
I) Build my cross-toolchain
# git clone http://git.yoctoproject.org/git/poky/.git
# cd poky
# git checkout 3ae71c74c71f13a390b21b4c3ead04e51aaa82b8 -b tcmode-default
...skip some steps...
# bitbake meta-toolchain
Loading cache: 100%
||
ETA: 00:00:00
Loaded 1122 entries from dependency cache.
Build Configuration:
BB_VERSION = "1.17.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "CentOS-6.3"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "1.3+snapshot-20130912"
TUNE_FEATURES = "m64"
TARGET_FPU = ""
meta
meta-yocto
meta-yocto-bsp = "tcmode-default:3ae71c74c71f13a390b21b4c3ead04e51aaa82b8"
..cost a long time..
all of the build work successfully
II) Install my cross-toolchain
# ./poky-eglibc-x86_64-x86_64-toolchain-1.3+snapshot-20130912.sh
Enter target directory for SDK (default: /opt/poky/1.3+snapshot):
toolchain-1.3-tcmode-default
III） compile a simple C program
# cat test.c
int main ()
{
printf("hello world\n");
return 0;
}
# source toolchain-1.3-tcmode-default/environment-setup-x86_64-poky-linux
# $CC -o test test.c -L tmp/sysroots/qemux86-64/usr/lib/ -lm
Technically, for this simple program, it's enough to do:
$CC -o test test.c
The $CC contains the sysroot option and the linker will automatically
prefix /lib and /usr/lib with the target sysroot. So, it should be able
to compile just fine.
The -L option just adds another search path for libraries which will be
searched before the default ones. So, it shouldn't be a problem.
Somehow, it looks like it tries to link against the host's libraries.
Before compiling, do a 'echo $CC' and make sure the --sysroot points to
the correct directory.
Laurentiu
test.c: In function 'main':
test.c:3:9: warning: incompatible implicit declaration of built-in function
'printf' [enabled by default]
/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
skipping incompatible /lib/libc.so.6 when searching for /lib/libc.so.6
/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
cannot find /lib/libc.so.6
/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
skipping incompatible /usr/lib/libc_nonshared.a when searching for
/usr/lib/libc_nonshared.a
/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
cannot find /usr/lib/libc_nonshared.a
collect2: error: ld returned 1 exit status
#cat toolchain-1.3-tcmode-default/environment-setup-x86_64-poky-linux
export
PATH=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin:/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux:$PATH
export
PKG_CONFIG_SYSROOT_DIR=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-poky-linux
export
PKG_CONFIG_PATH=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-poky-linux/usr/lib/pkgconfig
export
CONFIG_SITE=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmod
Re: [yocto] [poky] Is this a bug of binutils
On Fri, Sep 20, 2013 at 05:56:25PM +0800, Li Zhijian wrote:
> at 2013-9-20 16:50, Laurentiu Palcu wrote:
> >On Fri, Sep 20, 2013 at 11:43:31AM +0300, Laurentiu Palcu wrote:
> >>Hi,
> >>
> >>On Fri, Sep 20, 2013 at 02:45:24PM +0800, Li Zhijian wrote:
> >>>Hi，all
> >>>
> >>>I got a big problem when using the cross-toolchain to compile a simple C
> >>>program.
> >>>This problem since 3ae71c74c71f13a390b21b4c3ead04e51aaa82b8
> >>>which is to upgrade the binutils from 2.22 to 2.23.1
> >Apparently I missed this... Make sure you checkout
> >0333796a6b167dd754806700d7f771dd4a74e4ab (binutils_2.23.1.bb: Correct
> >typo in enable-targets configure option). This might be your problem.
> >
> >Laurentiu
> i am sorry，i don't understand what do you mean
My bad, I copy-pasted the wrong sha1 (the summary was good though).
Here's the correct sha1: a8fa49fbc21d460479ecadeb1996a800cc4e3e07
Laurentiu
>
> in poky git tree，
>
> 3ae71c74c71f13a390b21b4c3ead04e51aaa82b8 is newer than
> 0333796a6b167dd754806700d7f771dd4a74e4ab
>
> this checkout 0333796a6b167dd754806700d7f771dd4a74e4ab ， toolchain work fine
>
> # git log
> commit 3ae71c74c71f13a390b21b4c3ead04e51aaa82b8
> Author: Khem Raj
> Date: Wed Aug 8 10:33:41 2012 -0700
>
> tcmode-default.inc: Use binutils 2.23.1
> ...skip...
>
> commit 0333796a6b167dd754806700d7f771dd4a74e4ab
> Author: Khem Raj
> Date: Wed Aug 8 07:57:46 2012 -0700
>
> oprofile: Include config.h before bfd.h
>
> oprofile uses bfd.h from binutils which now in 2.23+ expects config.h
> so lets include it
> ...skip...
>
>
> --
> Best regards.
> Li Zhijian
>
>
> >>>what I do is as follows, any help or ideas ?
> >>>
> >>>I) Build my cross-toolchain
> >>># git clone http://git.yoctoproject.org/git/poky/.git
> >>># cd poky
> >>># git checkout 3ae71c74c71f13a390b21b4c3ead04e51aaa82b8 -b tcmode-default
> >>>...skip some steps...
> >>># bitbake meta-toolchain
> >>>Loading cache: 100%
> >>>||
> >>> ETA: 00:00:00
> >>>Loaded 1122 entries from dependency cache.
> >>>
> >>>Build Configuration:
> >>>BB_VERSION = "1.17.0"
> >>>BUILD_SYS = "x86_64-linux"
> >>>NATIVELSBSTRING = "CentOS-6.3"
> >>>TARGET_SYS = "x86_64-poky-linux"
> >>>MACHINE = "qemux86-64"
> >>>DISTRO = "poky"
> >>>DISTRO_VERSION = "1.3+snapshot-20130912"
> >>>TUNE_FEATURES = "m64"
> >>>TARGET_FPU = ""
> >>>meta
> >>>meta-yocto
> >>>meta-yocto-bsp = "tcmode-default:3ae71c74c71f13a390b21b4c3ead04e51aaa82b8"
> >>>
> >>>..cost a long time..
> >>>all of the build work successfully
> >>>
> >>>II) Install my cross-toolchain
> >>># ./poky-eglibc-x86_64-x86_64-toolchain-1.3+snapshot-20130912.sh
> >>>Enter target directory for SDK (default: /opt/poky/1.3+snapshot):
> >>>toolchain-1.3-tcmode-default
> >>>
> >>>III） compile a simple C program
> >>># cat test.c
> >>>int main ()
> >>>{
> >>>printf("hello world\n");
> >>>return 0;
> >>>}
> >>># source toolchain-1.3-tcmode-default/environment-setup-x86_64-poky-linux
> >>># $CC -o test test.c -L tmp/sysroots/qemux86-64/usr/lib/ -lm
> >>Technically, for this simple program, it's enough to do:
> >>
> >>$CC -o test test.c
> >>
> >>The $CC contains the sysroot option and the linker will automatically
> >>prefix /lib and /usr/lib with the target sysroot. So, it should be able
> >>to compile just fine.
> >>
> >>The -L option just adds another search path for libraries which will be
> >>searched before the default ones. So, it shouldn't be a problem.
> >>
> >>Somehow, it looks like it tries to link against the host's libraries.
> >>
> >>Before compiling, do a 'echo $CC' and make sure the --sysroot points to
> >>the correct directory.
> >>
> >>Laurentiu
> >>
> >>>test.c: In function 'main':
> >>>test.c:3:9: warning: incompatible implicit declaration of built-in
> >>>function 'printf' [enabled by default]
> >>>/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
> >>> skipping incompatible /lib/libc.so.6 when searching for /lib/libc.so.6
> >>>/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
> >>> cannot find /lib/libc.so.6
> >>>/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
> >>> skipping incompatible /usr/lib/libc_nonshared.a when searching for
> >>>/usr/lib/libc_nonshared.a
> >>>/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
> >>> cannot find /usr/lib/libc_nonshared.a
> >>>collect2: error: ld returned 1 exit status
> >>>
> >>>
> >
Re: [yocto] [poky] Is this a bug of binutils
at 2013-9-20 18:02, Laurentiu Palcu wrote:
On Fri, Sep 20, 2013 at 05:56:25PM +0800, Li Zhijian wrote:
at 2013-9-20 16:50, Laurentiu Palcu wrote:
On Fri, Sep 20, 2013 at 11:43:31AM +0300, Laurentiu Palcu wrote:
Hi,
On Fri, Sep 20, 2013 at 02:45:24PM +0800, Li Zhijian wrote:
Hi，all
I got a big problem when using the cross-toolchain to compile a simple C
program.
This problem since 3ae71c74c71f13a390b21b4c3ead04e51aaa82b8
which is to upgrade the binutils from 2.22 to 2.23.1
Apparently I missed this... Make sure you checkout
0333796a6b167dd754806700d7f771dd4a74e4ab (binutils_2.23.1.bb: Correct
typo in enable-targets configure option). This might be your problem.
Laurentiu
i am sorry，i don't understand what do you mean
My bad, I copy-pasted the wrong sha1 (the summary was good though).
Here's the correct sha1: a8fa49fbc21d460479ecadeb1996a800cc4e3e07
not really this fix，i build meta-toolchain on
yocto-1.4.1(73f103bf9b2cdf985464dc53bf4f1cfd71d4531f)
and got the same problem
even at the latest poky, got the same problem
--
Best regards.
Li Zhijian
Laurentiu
in poky git tree，
3ae71c74c71f13a390b21b4c3ead04e51aaa82b8 is newer than
0333796a6b167dd754806700d7f771dd4a74e4ab
this checkout 0333796a6b167dd754806700d7f771dd4a74e4ab ， toolchain work fine
# git log
commit 3ae71c74c71f13a390b21b4c3ead04e51aaa82b8
Author: Khem Raj
Date: Wed Aug 8 10:33:41 2012 -0700
tcmode-default.inc: Use binutils 2.23.1
...skip...
commit 0333796a6b167dd754806700d7f771dd4a74e4ab
Author: Khem Raj
Date: Wed Aug 8 07:57:46 2012 -0700
oprofile: Include config.h before bfd.h
oprofile uses bfd.h from binutils which now in 2.23+ expects config.h
so lets include it
...skip...
--
Best regards.
Li Zhijian
what I do is as follows, any help or ideas ?
I) Build my cross-toolchain
# git clone http://git.yoctoproject.org/git/poky/.git
# cd poky
# git checkout 3ae71c74c71f13a390b21b4c3ead04e51aaa82b8 -b tcmode-default
...skip some steps...
# bitbake meta-toolchain
Loading cache: 100%
||
ETA: 00:00:00
Loaded 1122 entries from dependency cache.
Build Configuration:
BB_VERSION = "1.17.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "CentOS-6.3"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "1.3+snapshot-20130912"
TUNE_FEATURES = "m64"
TARGET_FPU = ""
meta
meta-yocto
meta-yocto-bsp = "tcmode-default:3ae71c74c71f13a390b21b4c3ead04e51aaa82b8"
..cost a long time..
all of the build work successfully
II) Install my cross-toolchain
# ./poky-eglibc-x86_64-x86_64-toolchain-1.3+snapshot-20130912.sh
Enter target directory for SDK (default: /opt/poky/1.3+snapshot):
toolchain-1.3-tcmode-default
III） compile a simple C program
# cat test.c
int main ()
{
printf("hello world\n");
return 0;
}
# source toolchain-1.3-tcmode-default/environment-setup-x86_64-poky-linux
# $CC -o test test.c -L tmp/sysroots/qemux86-64/usr/lib/ -lm
Technically, for this simple program, it's enough to do:
$CC -o test test.c
The $CC contains the sysroot option and the linker will automatically
prefix /lib and /usr/lib with the target sysroot. So, it should be able
to compile just fine.
The -L option just adds another search path for libraries which will be
searched before the default ones. So, it shouldn't be a problem.
Somehow, it looks like it tries to link against the host's libraries.
Before compiling, do a 'echo $CC' and make sure the --sysroot points to
the correct directory.
Laurentiu
test.c: In function 'main':
test.c:3:9: warning: incompatible implicit declaration of built-in function
'printf' [enabled by default]
/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
skipping incompatible /lib/libc.so.6 when searching for /lib/libc.so.6
/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
cannot find /lib/libc.so.6
/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
skipping incompatible /usr/lib/libc_nonshared.a when searching for
/usr/lib/libc_nonshared.a
/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/../../libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.7.2/ld:
cannot find /usr/lib/libc_nonshared.a
collect2: error: ld returned 1 exit status
#cat toolchain-1.3-tcmode-default/environment-setup-x86_64-poky-linux
export
PATH=/yocto/fnst/lizj/build_yocto/x86-64-yocto-1.3/toolchain-1.3-tcmode-default/sysroots/x86_64-pokysdk-linux/usr/bin:/yocto/fnst/lizj/build_yocto/x86-64-yo
Re: [yocto] [poky] Is this a bug of binutils
Hi,
On Fri, Sep 20, 2013 at 06:25:19PM +0800, Li Zhijian wrote:
> >
> >III） compile a simple C program
> ># cat test.c
> >int main ()
> >{
> >printf("hello world\n");
> >return 0;
> >}
> ># source toolchain-1.3-tcmode-default/environment-setup-x86_64-poky-linux
> ># $CC -o test test.c -L tmp/sysroots/qemux86-64/usr/lib/ -lm
OK, it looks like something strange happens in your setup.
To debug it, let's add '-Wl,--verbose' at the end of your command and you
should be able to see where the linker is looking for libraries. Also,
the linker script will be printed.
You should see it try your directory first
tmp/sysroots/qemux86-64/usr/lib/, and then fall through the default ones
with the sysroot prefix added and, at the end, the system ones:
/lib:/usr/lib.
Thanks,
Laurentiu
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] TCP Window Issue while doing SSH
Hi, I'm seeing a TCP window issue while doing a SSH. Below is TCPDUMP capture of SSH from Yocto to an external Linux server. Yocto sends a SYN window of 14600 (10x of MSS) and external Linux server ACKs with Window of 5792 (4x of MSS). Now, Yocto Linux drops the ACK. When I do the SSH from external Linux server the same thing happens and Yocto Linux never sends out a SYN ACK. 19:00:17.309270 IP 9.1.2.1.40144 > 9.1.1.5.ssh: S 1858484743:1858484743(0) win 14600 19:00:17.309282 IP 9.1.1.5.ssh > 9.1.2.1.40144: S 606474867:606474867(0) ack 1858484744 win 5792 I'm using 9.0.1 but I have faced the same issue with 9.0.2 as well. I tried turning off TCP window scaling with sysctl -w "net.ipv4.tcp_window_scaling=0" but it does not help. Any suggestions on how I can fix this problem? The SSH works fine when the peer accepts the Window size proposed by Yocto Linux but fails when the peer proposes an alternate Win size. Thanks -Ashish ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] running core-image-sato on the development host
On Sep 19, 2013, at 10:51 PM, arun kumar wrote: > can i run the image built using the quickstart guide on my x86 host, the > machine was set to qemux86, is there a way to use the files generated in > /tmp/deploy to boot on my host / Execute runqemu qemux86 with in a shell where you have sourced env script oe-init-build-env > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder][PATCH] buildset-config: small improvement to nightly-qa-logrotate scenario
Pulled into master. In production today. Thanks.
-b
On Thu, Sep 19, 2013 at 6:04 AM, Alexandru Palalau
wrote:
> Replaced DISTRO_EXTRA_RDEPENDS (which applies only for images that
> include packagegroup-base) with IMAGE_INSTALL_append in order to add
> logrotate package to the image.
>
> Signed-off-by: Alexandru Palalau
> ---
> buildset-config/nightly-qa-logrotate.conf | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/buildset-config/nightly-qa-logrotate.conf
> b/buildset-config/nightly-qa-logrotate.conf
> index c82206e..1a60bd3 100644
> --- a/buildset-config/nightly-qa-logrotate.conf
> +++ b/buildset-config/nightly-qa-logrotate.conf
> @@ -8,7 +8,7 @@ steps: [{'SetDest':{}},
> {'CheckOutLayers': {}},
> {'RunPreamble': {}},
> {'GetDistroVersion' : {'distro': 'poky'}},
> -{'CreateAutoConf': {'machine': 'qemux86-64', 'SDKMACHINE' : 'i686',
> 'distro': 'poky', 'atextappend' : '\nDISTRO_EXTRA_RDEPENDS +=
> "logrotate"\n'}},
> +{'CreateAutoConf': {'machine': 'qemux86-64', 'SDKMACHINE' : 'i686',
> 'distro': 'poky', 'atextappend' : '\nIMAGE_INSTALL_append = " logrotate"\n'}},
> {'CreateBBLayersConf': {'buildprovider' : 'yocto'}},
> {'BuildImages': {'images': 'core-image-sato'}},
> {'RunSanityTests': {'images': 'core-image-sato', 'suitesappend' :
> 'logrotate'}}]
> --
> 1.7.11.7
>
--
Elizabeth Flanagan
Yocto Project
Build and Release
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Configuring linux-yocto-custom to build specific kernel modules
Hi, I would like to know how I can build a specific kernel module (one that is already in the linux kernel). Do I have to create a custom bitbake recipe for the module or can I simply configure linux-yocto-custom? My specific aim is to build the kernel module drivers/net/wireless/rtl818x/rtl8187 as part of the core-image-minimal build. Regards, J ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Configuring linux-yocto-custom to build specific kernel modules
On 13-09-20 03:53 PM, John Doe wrote: Hi, I would like to know how I can build a specific kernel module (one that is already in the linux kernel). Do I have to create a custom bitbake recipe for the module or can I simply configure linux-yocto-custom? Is your kernel already building from linux-yocto-custom ? Or are you using the default linux-yocto kernel and recipes already ? If you are using one of the standard qemu machines, or a BSP that is already working with linux-yocto*, you can simply enable the module by creating a configuration fragment, and putting it on the SRC_URI. config fragments and how to add them to the SRC_URI are covered in the kernel development manuals found off the yocto site. Cheers, Bruce My specific aim is to build the kernel module drivers/net/wireless/rtl818x/rtl8187 as part of the core-image-minimal build. Regards, J ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] RFC: Janitorial tasks
On 19 September 2013 19:26, Bryan Evenson wrote: > Paul, > > Is the plan to move toward the YP wiki task list, the YP bugzilla, or both > for Janitorial task entry? If one would be preferred over the other, it'd > probably be good to state that at the top of the wiki page. > Currently it's both as both can be seen from the YP wiki page. > For the wiki task list, maybe add an "Assignee:" line, so that someone knows > if the task is being worked on? Would be frustrating to work on a task only > to find someone else did the same thing. > Probably a good idea. -- Paul Barker Email: p...@paulbarker.me.uk http://www.paulbarker.me.uk ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Mono 2.10.8.1 (meta-mono) Corelib not in sync with runtime...
I am trying to get Mono 2.10 working on a core-image-basic running on
qemux86 machine. I am using pokay-dylan-9.0.2 on a Debian 6.0.7 system for
the builds and been able to build and run images without issue. Yet, when
I went to add the meta-mono layer from git.yoctoporject.org, I started
running into problems.
I first had to add these lines to the mono_2.10.8.1.bb recipe, and move
the mono-2.10.8.1/ folder into the files/ folder to get the build to
succeed. I also added the EXTRA_OECONF line to disable X support (don't
want winforms, just Mono for console and services).
EXTRA_OECONF += "--without-x --without-moonlight --without-libgdiplus"
FILES_${PN} += "${datadir}/mono-2.0"
FILES_${PN} += "${datadir}/libgc-mono"
INSANE_SKIP_${PN} = "arch dev-so debug-files ldflags"
After that, I built and booted an image with the 'mono' package installed
and was able to run Mono simply:
$ mono --version
Mono JIT compiler version 2.10.8.1 (tarball Fri Sep 20 14:23:43 MDT 2013)
Copyright (C) 2002-2011 Novell, Inc, Xamarin, Inc and Contributors.
www.mono-project.com
TLS: normal
SIGSEGV: normal
Notifications: epoll
Architecture: x86
Disabled: none
Misc: debugger softdebug
LLVM: supported, not enabled.
GC:Included Boehm (with typed GC and Parallel Mark)
Yet when I actually tried to run a Mono application (simple console only
application already compiled on another system), I got this error:
Corlib not in sync with this runtime: expected corlib version 96, found 100.
Loaded from: /usr/lib/mono/2.0/mscorlib.dll
Download a newer corlib or a newer runtime at http://www.go-mono.com/daily.
It looks like this error indicates some sort mismatch in Mono, as if one
was mixing between a release and a development version. But there is no
Mono on my build machine to cause confusion, everything came from the Mono
recipe. Further, given the issues I encountered above in getting Mono
built, it appears this recipe has not been tested with more recent version
of Yocto.
Is there a more current Mono recipe available? Does anyone have any ideas
on what in this Mono recipe could cause that error? Or do I get to dig in
and untangle the Mono build? Thanks!
---
| Ryan Kirkpatrick | Boulder, CO | rkirkpat.net | twitter.com/rkirkpatnet |
---
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Adding kernel module to minimal image
Hello, How can I add kernel module to fsl-image-minimal? I want to add hello-mod module in /yocto/meta-skeleton/recipes-kerne/hello-mod path to my fsl-image-minimal. Then I read the Kernel Development Manual document and add MACHINE_EXTRA_RRECOMMENDS += "kernel-module-hello-mod" to local.conf file. After building the image, hello-mod dosen't exist in fsl-image-minimal in /yocto/build_p1022ds_release/tmp/work /p1022ds-fsl-linux-gnuspe/fsl-image-minimal-1.0-r0 path. What can I do to add hello-mod module to my fsl-image-minimal? ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
