Re: [oe] Cross-Compilation of ROOT for ARM machine
On Tue, Jul 16, 2013 at 7:37 PM, Brian Kelly wrote: > > I am trying to compile the Root library (ver. 5.34.09) for an arm machine > (i.e. a gumstix verdex XL6P running the Angstrom linux distribution (a > computer-on-module)). I attempted native compilation but I kept getting an > internal error in the compiler program, which led to suspect that there was > not enough memory for the library to compile (this is most likely the case > since the library compiled fine on a debian arm emulation using qemu). > > Now I am attempting to the bitbake software. I followed the instructions on > the website http://wiki.gumstix.org/index.php?title=Verdex_Git_Repositoryto > create a working bitbake environment and verdex image was created > successfully. > > > Now I am trying to create a recipe that will allow me to run Root. > Supposedly the libraries have been built successfully but the installation > on the gumstix fails (see attachment). > > I have attached my work so far (my recipe, the terminal output from the > computer I am running bitbake on and the terminal output from my gumstix) > and, since I am quite inexperienced with bitbake, I would greatly > appreciate > any constructive feedback that will help me get the Root library working on > the gumstix. > > Thank you very much in for any help that you may provide. > hi. i am not sure exactly what you are trying to do here. but you seem to be using quite old instructions that relate to 'OE classic'. The wiki you mentioned hasn't got any update from more than 2 years. many changes have happened in OE, i suggest you start with http://openembedded.org/wiki/OpenEmbedded-Core you recipe as it is written wouldn't work with the OE-core, and guidelines to migrate recipes can be found here: http://openembedded.org/wiki/Migrating_metadata_to_OE-Core i am not familiar with gumtix, but you might check with that community if they release an OE SDK you could use for cross compilation. or you can at least get more up to date information about how to add your recipe in their builds. ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH] proxy-libintl: Put .a in -dev package and allow empty main package
This helps in staging the library when it is asked for
via dependencies otherwise its missing in staging sysroot
even though its built its stashed into -staticdev package
Signed-off-by: Khem Raj
---
.../proxy-libintl/proxy-libintl_20100902.bb|4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta-oe/recipes-core/proxy-libintl/proxy-libintl_20100902.bb
b/meta-oe/recipes-core/proxy-libintl/proxy-libintl_20100902.bb
index 451a3c6..e1531dd 100644
--- a/meta-oe/recipes-core/proxy-libintl/proxy-libintl_20100902.bb
+++ b/meta-oe/recipes-core/proxy-libintl/proxy-libintl_20100902.bb
@@ -14,8 +14,10 @@ SRC_URI[md5sum] = "aef407c2b97ee829383aadd867c61d1e"
SRC_URI[sha256sum] =
"291ac350cc5eb4a01b0d651ca99fae64cee8a1c06b2005277fab5a4356f9ae91"
S = "${WORKDIR}"
+PACKAGES = "${PN} ${PN}-dev"
FILES_${PN}-dev = "${includedir}/libintl.h ${libdir}/libintl.a"
-
+INSANE_SKIP_${PN}-dev = "staticdev"
+ALLOW_EMPTY_${PN} = "1"
CFLAGS_append = " -fPIC -Wall -I ../../include ${@['-DSTUB_ONLY',
''][d.getVar('USE_NLS', 1) != 'no']}"
TARGET_CC_ARCH += "${LDFLAGS}"
--
1.7.9.5
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-networking][PATCH v2] Upgrade vsftpd to 3.0.0
Hi Roy,
I merged this into my tree yesterday and on review it turns out I did
have a question for you (and for anyone else on the list with an
opinion) and a bit of feedback.
This adds (unconditional) support for tcp-wrappers and makes it a
requirement for the upgraded vsftp. Is this something we could make
conditional based on tcp-wrappers being present? Or does anyone think
this is something worth doing? tcp-wrappers is coming from oe-core and
I don't have any systems where the new requirement would be a problem,
but does anyone else have a system they'd want vsftp without
tcp-wrappers?
A couple of other things below ...
[[meta-networking][PATCH v2] Upgrade vsftpd to 3.0.0] On 13.07.16 (Tue 20:51)
rongqing...@windriver.com wrote:
> From: "Roy.Li"
>
> Upgrade vsftpd to 3.0.0 with below modification:
> 1. more strict access limitation, like: do not allow anonymous access
> 2. use vsftpd.ftpusers and vsftpd.user_list to confine user access
> 3. enable pam if DISTRO_FEATURE includes pam
> 4. enable tcp-wrapper
> 5. install vsftpd.conf with 0600 permission, not 0755
>
> Signed-off-by: Roy.Li
> ---
> .../recipes-daemons/vsftpd/files/vsftpd.conf | 43
> +---
> .../recipes-daemons/vsftpd/files/vsftpd.ftpusers | 15 +++
> .../recipes-daemons/vsftpd/files/vsftpd.user_list | 20 +
> .../makefile-destdir.patch |4 +-
> .../makefile-libs.patch|2 +-
> .../makefile-strip.patch |6 +--
> .../{vsftpd-2.3.5 => vsftpd-3.0.0}/nopam.patch |0
> .../vsftpd-3.0.0/vsftpd-tcp_wrappers-support.patch | 25
> .../vsftpd/{vsftpd_2.3.5.bb => vsftpd_3.0.0.bb}| 36 +---
> 9 files changed, 133 insertions(+), 18 deletions(-)
> mode change 100755 => 100644
> meta-networking/recipes-daemons/vsftpd/files/vsftpd.conf
> create mode 100644
> meta-networking/recipes-daemons/vsftpd/files/vsftpd.ftpusers
> create mode 100644
> meta-networking/recipes-daemons/vsftpd/files/vsftpd.user_list
> rename meta-networking/recipes-daemons/vsftpd/{vsftpd-2.3.5 =>
> vsftpd-3.0.0}/makefile-destdir.patch (95%)
> rename meta-networking/recipes-daemons/vsftpd/{vsftpd-2.3.5 =>
> vsftpd-3.0.0}/makefile-libs.patch (92%)
> rename meta-networking/recipes-daemons/vsftpd/{vsftpd-2.3.5 =>
> vsftpd-3.0.0}/makefile-strip.patch (68%)
> rename meta-networking/recipes-daemons/vsftpd/{vsftpd-2.3.5 =>
> vsftpd-3.0.0}/nopam.patch (100%)
> create mode 100644
> meta-networking/recipes-daemons/vsftpd/vsftpd-3.0.0/vsftpd-tcp_wrappers-support.patch
> rename meta-networking/recipes-daemons/vsftpd/{vsftpd_2.3.5.bb =>
> vsftpd_3.0.0.bb} (48%)
>
> diff --git a/meta-networking/recipes-daemons/vsftpd/files/vsftpd.conf
> b/meta-networking/recipes-daemons/vsftpd/files/vsftpd.conf
> old mode 100755
> new mode 100644
> index 08f91e0..bb19294
> --- a/meta-networking/recipes-daemons/vsftpd/files/vsftpd.conf
> +++ b/meta-networking/recipes-daemons/vsftpd/files/vsftpd.conf
> @@ -12,17 +12,17 @@
> listen=YES
>
> # Allow anonymous FTP? (Beware - allowed by default if you comment this out).
> -anonymous_enable=YES
> +anonymous_enable=NO
> #
> # Uncomment this to allow local users to log in.
> -#local_enable=YES
> +local_enable=YES
> #
> # Uncomment this to enable any form of FTP write command.
> write_enable=YES
> #
> # Default umask for local users is 077. You may wish to change this to 022,
> # if your users expect that (022 is used by most other ftpd's)
> -#local_umask=022
> +local_umask=022
> #
> # Uncomment this to allow the anonymous FTP user to upload files. This only
> # has an effect if the above global write enable is activated. Also, you will
> @@ -54,7 +54,7 @@ connect_from_port_20=YES
> #xferlog_file=/var/log/vsftpd.log
> #
> # If you want, you can have your log file in standard ftpd xferlog format
> -#xferlog_std_format=YES
> +xferlog_std_format=YES
> #
> # You may change the default value for timing out an idle session.
> #idle_session_timeout=600
> @@ -64,7 +64,7 @@ connect_from_port_20=YES
> #
> # It is recommended that you define on your system a unique user which the
> # ftp server can use as a totally isolated and unprivileged user.
> -#nopriv_user=ftpsecure
> +#nopriv_user=ftp
> #
> # Enable this and the server will recognise asynchronous ABOR requests. Not
> # recommended for security (the code is non-trivial). Not enabling it,
> @@ -105,4 +105,35 @@ connect_from_port_20=YES
> # sites. However, some broken FTP clients such as "ncftp" and "mirror" assume
> # the presence of the "-R" option, so there is a strong case for enabling it.
> #ls_recurse_enable=YES
> -
> +#
> +# This string is the name of the PAM service vsftpd will use.
> +pam_service_name=vsftpd
I haven't tried this, does it do the right thing when PAM is not present
on the system? In particular, what's it do when nopam.patch is applied?
In that same vein:
ERROR: Command Error:
Re: [oe] [PATCH] cyrus-sasl: several fixes
[[PATCH] cyrus-sasl: several fixes] On 13.07.17 (Wed 14:24)
rongqing...@windriver.com wrote:
> From: "Roy.Li"
>
> 1. Fix hardcoded libdir
> 2. configure cyrus-sasl based on PACKAGECONFIG
> 3. create user by inherit useradd
> 4. add -fPIC to CFLAG to fix a building failure, the cause as below:
> ld: ../sasldb/.libs/libsasldb.a(db_berkeley.o): relocation
> R_X86_64_32S against
> `.rodata' can not be used when making a shared object; recompile with
> -fPIC
> ../sasldb/.libs/libsasldb.a(db_berkeley.o): could not read symbols:
> Bad value
>
> Further investigation shows Upstream chose a strange way to keep
> compatible
> with certain versions of automake.
>
> --- a/sasldb/Makefile.am
> +++ b/sasldb/Makefile.am
> @@ -1,6 +1,6 @@
> # Makefile.am for the SASLdb library
> # Rob Siemborski
> -# $Id: Makefile.am,v 1.28 2005/04/11 05:09:31 shadow Exp $
> +# $Id: Makefile.am,v 1.29 2005/05/07 04:14:56 shadow Exp $
> # Copyright (c) 2000 Carnegie Mellon University. All rights
> reserved.
> #
> # Redistribution and use in source and binary forms, with or without
> @@ -62,7 +62,7 @@ libsasldb_la_LIBADD = $(SASL_DB_BACKEND)
> libsasldb_a_SOURCES =
> EXTRA_libsasldb_a_SOURCES =
>
> -libsasldb.a: libsasldb.la $(LOCAL_SASL_DB_BACKEND_STATIC)
> - $(AR) cru .libs/$@ $(LOCAL_SASL_DB_BACKEND_STATIC)
> +libsasldb.a: libsasldb.la $(SASL_DB_BACKEND_STATIC)
> + $(AR) cru .libs/$@ $(SASL_DB_BACKEND_STATIC)
This is ... odd. I'm not sure how this relates to the comment below,
but your solution seems sound.
>
> that snippet of Makefile rule made libsasldb.a built twice, one with
> -fPIC, other without -fPIC. if no -fPIC library follow behind, this error
> will appear. so we enable -fPIC no matter whatever objects are built.
>
> Signed-off-by: Roy.Li
> ---
> .../cyrus-sasl/cyrus-sasl_2.1.26.bb| 32
> +---
> .../cyrus-sasl/files/Fix-hardcoded-libdir.patch| 25 +++
> 2 files changed, 52 insertions(+), 5 deletions(-)
> create mode 100644
> meta-networking/recipes-daemons/cyrus-sasl/files/Fix-hardcoded-libdir.patch
>
> diff --git a/meta-networking/recipes-daemons/cyrus-sasl/cyrus-sasl_2.1.26.bb
> b/meta-networking/recipes-daemons/cyrus-sasl/cyrus-sasl_2.1.26.bb
> index 4311540..4dac450 100644
> --- a/meta-networking/recipes-daemons/cyrus-sasl/cyrus-sasl_2.1.26.bb
> +++ b/meta-networking/recipes-daemons/cyrus-sasl/cyrus-sasl_2.1.26.bb
> @@ -5,21 +5,40 @@ LICENSE = "BSD"
> LIC_FILES_CHKSUM = "file://COPYING;md5=3f55e0974e3d6db00ca6f57f2d206396"
>
> SRC_URI = "ftp://ftp.cyrusimap.org/cyrus-sasl/cyrus-sasl-${PV}.tar.gz \
> -file://avoid-to-call-AC_TRY_RUN.patch"
> +file://avoid-to-call-AC_TRY_RUN.patch \
> +file://Fix-hardcoded-libdir.patch"
>
> -inherit autotools pkgconfig
> +inherit autotools pkgconfig useradd
>
> EXTRA_OECONF += "--with-dblib=berkeley \
> --with-bdb-libdir=${STAGING_LIBDIR} \
> --with-bdb-incdir=${STAGING_INCDIR} \
> - --without-pam --without-opie --without-des \
> + --with-bdb=db-5.3 \
> + --enable-login \
> + --with-plugindir="${libdir}/sasl2/" \
I'm not sure I expected any of these changes based on your commit log,
though. Well, moving --with/out-pam/opie/des into PACKAGECONFIG
variables, yes, but not --with-bdb/--enable-login/--with-plugindir. Can
you comment on those as well?
> andrew_cv_runpath_switch=none"
>
> -PACKAGECONFIG ??= ""
> +PACKAGECONFIG = "ntlm \
> +${@base_contains('DISTRO_FEATURES', 'ldap', 'ldap', '', d)} \
> +${@base_contains('DISTRO_FEATURES', 'pam', 'pam', '', d)} \
> +"
Shouldn't you be checking the other values in DISTRO_FEATURES as well?
And is ntlm a given? I'm thinking you didn't necessarily mean to drop
the ?? here.
-J.
> PACKAGECONFIG[gssapi] = "--enable-gssapi=yes,--enable-gssapi=no,krb5,"
> +PACKAGECONFIG[pam] = "--with-pam,--without-pam,libpam,"
> +PACKAGECONFIG[opie] = "--with-opie,--without-opie,opie,"
> +PACKAGECONFIG[des] = "--with-des,--without-des,,"
> +PACKAGECONFIG[ldap] = "--with-ldap=${STAGING_LIBDIR}
> --enable-ldapdb,--without-ldap --disable-ldapdb,openldap,"
> +PACKAGECONFIG[ntlm] = "--with-ntlm,--without-ntlm,,"
> +
> +CFLAGS += "-fPIC"
>
> do_configure_prepend () {
> rm -f acinclude.m4 config/libtool.m4
> +
> +# make it be able to work with db 5.0 version
> +local sed_files="sasldb/db_berkeley.c utils/dbconverter-2.c"
> +for sed_file in $sed_files; do
> +sed -i 's#DB_VERSION_MAJOR == 4.*#(&) || DB_VERSION_MAJOR == 5#'
> $sed_file
> +done
> }
>
> do_compile_prepend () {
> @@ -29,8 +48,11 @@ do_compile_prepend () {
> cd ..
> }
>
> +USERADD_PACKAGES = "${PN}-bin"
> +GROUPADD_PARAM_
Re: [oe] [meta-networking][PATCH] licences: Add netperf license
Merged, thanks.
-J.
[[oe] [meta-networking][PATCH] licences: Add netperf license] On 13.07.10 (Wed
11:12) Chunrong Guo wrote:
> Signed-off-by: Chunrong Guo
> ---
> meta-networking/conf/layer.conf |2 +
> meta-networking/licenses/netperf | 43
> ++
> 2 files changed, 45 insertions(+), 0 deletions(-)
> create mode 100644 meta-networking/licenses/netperf
>
> diff --git a/meta-networking/conf/layer.conf b/meta-networking/conf/layer.conf
> index f75080a..14eb048 100644
> --- a/meta-networking/conf/layer.conf
> +++ b/meta-networking/conf/layer.conf
> @@ -14,3 +14,5 @@ BBFILE_PRIORITY_networking = "5"
> LAYERVERSION_networking = "1"
>
> LAYERDEPENDS_networking = "core"
> +
> +LICENSE_PATH += "${LAYERDIR}/licenses"
> diff --git a/meta-networking/licenses/netperf
> b/meta-networking/licenses/netperf
> new file mode 100644
> index 000..3f3ceb2
> --- /dev/null
> +++ b/meta-networking/licenses/netperf
> @@ -0,0 +1,43 @@
> +
> +
> + Copyright (C) 1993 Hewlett-Packard Company
> + ALL RIGHTS RESERVED.
> +
> + The enclosed software and documentation includes copyrighted works
> + of Hewlett-Packard Co. For as long as you comply with the following
> + limitations, you are hereby authorized to (i) use, reproduce, and
> + modify the software and documentation, and to (ii) distribute the
> + software and documentation, including modifications, for
> + non-commercial purposes only.
> +
> + 1. The enclosed software and documentation is made available at no
> + charge in order to advance the general development of
> + high-performance networking products.
> +
> + 2. You may not delete any copyright notices contained in the
> + software or documentation. All hard copies, and copies in
> + source code or object code form, of the software or
> + documentation (including modifications) must contain at least
> + one of the copyright notices.
> +
> + 3. The enclosed software and documentation has not been subjected
> + to testing and quality control and is not a Hewlett-Packard Co.
> + product. At a future time, Hewlett-Packard Co. may or may not
> + offer a version of the software and documentation as a product.
> +
> + 4. THE SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS".
> + HEWLETT-PACKARD COMPANY DOES NOT WARRANT THAT THE USE,
> + REPRODUCTION, MODIFICATION OR DISTRIBUTION OF THE SOFTWARE OR
> + DOCUMENTATION WILL NOT INFRINGE A THIRD PARTY'S INTELLECTUAL
> + PROPERTY RIGHTS. HP DOES NOT WARRANT THAT THE SOFTWARE OR
> + DOCUMENTATION IS ERROR FREE. HP DISCLAIMS ALL WARRANTIES,
> + EXPRESS AND IMPLIED, WITH REGARD TO THE SOFTWARE AND THE
> + DOCUMENTATION. HP SPECIFICALLY DISCLAIMS ALL WARRANTIES OF
> + MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
> +
> + 5. HEWLETT-PACKARD COMPANY WILL NOT IN ANY EVENT BE LIABLE FOR ANY
> + DIRECT, INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
> + (INCLUDING LOST PROFITS) RELATED TO ANY USE, REPRODUCTION,
> + MODIFICATION, OR DISTRIBUTION OF THE SOFTWARE OR DOCUMENTATION.
> +
> +
--
-Joe MacDonald.
:wq
signature.asc
Description: Digital signature
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH] netcat: intergrat two fixes
And merged. Thanks, Roy.
-J.
[[PATCH] netcat: intergrat two fixes] On 13.07.16 (Tue 13:07)
rongqing...@windriver.com wrote:
> From: "Roy.Li"
>
> 1. fix a running issue on PPC, since 'char' type has different range of values
> on x86 and on PPC.
> 2. fix a building issue.
>
> Signed-off-by: Roy.Li
> ---
> .../netcat/make-netcat_flag_count_work.patch | 34
>
> .../netcat/netcat/netcat-locale_h.patch| 25 ++
> .../recipes-support/netcat/netcat_0.7.1.bb |2 ++
> 3 files changed, 61 insertions(+)
> create mode 100644
> meta-networking/recipes-support/netcat/netcat/make-netcat_flag_count_work.patch
> create mode 100644
> meta-networking/recipes-support/netcat/netcat/netcat-locale_h.patch
>
> diff --git
> a/meta-networking/recipes-support/netcat/netcat/make-netcat_flag_count_work.patch
>
> b/meta-networking/recipes-support/netcat/netcat/make-netcat_flag_count_work.patch
> new file mode 100644
> index 000..dd1938a
> --- /dev/null
> +++
> b/meta-networking/recipes-support/netcat/netcat/make-netcat_flag_count_work.patch
> @@ -0,0 +1,34 @@
> +Make netcat_flag_count() return positive value
> +
> +C language has 3 distinct char types:
> + char
> + unsigned char
> + signed char
> +A char has the same range of values as signed char on X86,
> +but same as unsigned char on PPC which made netcat_flag_count
> +return a negative value, now we force variable c as signed char
> +to make netcat_flag_count return positive value.
> +
> +Upstream-Status: Pending
> +
> +Signed-off-by: Roy.Li
> +---
> + src/flagset.c |2 +-
> + 1 files changed, 1 insertions(+), 1 deletions(-)
> +
> +diff --git a/src/flagset.c b/src/flagset.c
> +index 442b634..54ac898 100644
> +--- a/src/flagset.c
> b/src/flagset.c
> +@@ -134,7 +134,7 @@ unsigned short netcat_flag_next(unsigned short port)
> +
> + int netcat_flag_count(void)
> + {
> +- register char c;
> ++ register signed char c;
> + register int i;
> + int ret = 0;
> +
> +--
> +1.7.5.4
> +
> diff --git
> a/meta-networking/recipes-support/netcat/netcat/netcat-locale_h.patch
> b/meta-networking/recipes-support/netcat/netcat/netcat-locale_h.patch
> new file mode 100644
> index 000..5cbcb08
> --- /dev/null
> +++ b/meta-networking/recipes-support/netcat/netcat/netcat-locale_h.patch
> @@ -0,0 +1,25 @@
> +Apparently somewhere along the line HAVE_LOCALE_H was changed to
> +HAVE_LC_MESSAGES. Adjust netcat to match.
> +
> +Upstream-Status: Pending
> +
> +Signed-off-by: Mark Hatle
> +
> +Index: netcat-0.7.1/src/intl.h
> +===
> +--- netcat-0.7.1.orig/src/intl.h
> netcat-0.7.1/src/intl.h
> +@@ -25,11 +25,11 @@
> + #ifdef ENABLE_NLS
> + #include
> +
> +-#ifdef HAVE_LOCALE_H
> ++#if defined(HAVE_LC_MESSAGES) || defined(HAVE_LOCALE_H)
> + #include
> + #else
> + #error You must have locale.h in your system
> +-#endif /* HAVE_LOCALE_H */
> ++#endif /* HAVE_LC_MESSAGES || HAVE_LOCALE_H */
> +
> + /* Our dear (and very common) gettext macros */
> + #define _(String) gettext(String)
> diff --git a/meta-networking/recipes-support/netcat/netcat_0.7.1.bb
> b/meta-networking/recipes-support/netcat/netcat_0.7.1.bb
> index a4805a4..0bb5c87 100644
> --- a/meta-networking/recipes-support/netcat/netcat_0.7.1.bb
> +++ b/meta-networking/recipes-support/netcat/netcat_0.7.1.bb
> @@ -8,6 +8,8 @@ PR = "r3"
>
> SRC_URI = "${SOURCEFORGE_MIRROR}/netcat/netcat-${PV}.tar.bz2 \
> file://obsolete_autoconf_macros.patch \
> + file://netcat-locale_h.patch \
> + file://make-netcat_flag_count_work.patch \
> "
>
> SRC_URI[md5sum] = "0a29eff1736ddb5effd0b1ec1f6fe0ef"
--
-Joe MacDonald.
:wq
signature.asc
Description: Digital signature
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-networking][PATCH] The ip is being installed into /sbin as of the latest busybox.
Merged. Thanks. -J. [[meta-networking][PATCH] The ip is being installed into /sbin as of the latest busybox.] On 13.07.16 (Tue 17:53) rongqing...@windriver.com wrote: > From: "Roy.Li" > > The ip is being installed into /sbin as of the latest busybox, or oe-core. > > Signed-off-by: Roy.Li > --- > .../recipes-protocols/zeroconf/zeroconf/debian-zeroconf|4 > ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git > a/meta-networking/recipes-protocols/zeroconf/zeroconf/debian-zeroconf > b/meta-networking/recipes-protocols/zeroconf/zeroconf/debian-zeroconf > index c3705d2..0c9d15b 100644 > --- a/meta-networking/recipes-protocols/zeroconf/zeroconf/debian-zeroconf > +++ b/meta-networking/recipes-protocols/zeroconf/zeroconf/debian-zeroconf > @@ -35,10 +35,10 @@ done > > # should we only allocate an address if we do not already have one? > if [ -n "$FALLBACK" ]; then > -/bin/ip addr show $IFACE scope global | grep -q "inet" > +/sbin/ip addr show $IFACE scope global | grep -q "inet" > IP=$? > if [ $IP -eq 0 ]; then > -/bin/ip route add 169.254.0.0/16 dev $IFACE > +/sbin/ip route add 169.254.0.0/16 dev $IFACE > exit 0 > fi > fi -- -Joe MacDonald. :wq signature.asc Description: Digital signature ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-networking][PATCH] inetutils: several improvement
Merged, thanks.
-J.
[[oe] [meta-networking][PATCH] inetutils: several improvement] On 13.07.17 (Wed
11:20) rongqing...@windriver.com wrote:
> From: "Roy.Li"
>
> 1. integrate rexec, rlogin, rsh, telnet, tftpd xinetd startup scripts
> 2. inherit update-alternatives bbclass, not call update-alternatives directly.
> 3. package all commands into subpackages
>
> Signed-off-by: Roy.Li
> ---
> .../inetutils-1.9.1/rexec.xinetd.inetutils | 20 +++
> .../inetutils-1.9.1/rlogin.xinetd.inetutils| 23 +++
> .../inetutils/inetutils-1.9.1/rsh.xinetd.inetutils | 21 +++
> .../inetutils-1.9.1/telnet.xinetd.inetutils| 13 ++
> .../inetutils-1.9.1/tftpd.xinetd.inetutils | 19 +++
> .../inetutils/inetutils_1.9.1.bb | 148
>
> 6 files changed, 215 insertions(+), 29 deletions(-)
> create mode 100644
> meta-networking/recipes-connectivity/inetutils/inetutils-1.9.1/rexec.xinetd.inetutils
> create mode 100644
> meta-networking/recipes-connectivity/inetutils/inetutils-1.9.1/rlogin.xinetd.inetutils
> create mode 100644
> meta-networking/recipes-connectivity/inetutils/inetutils-1.9.1/rsh.xinetd.inetutils
> create mode 100644
> meta-networking/recipes-connectivity/inetutils/inetutils-1.9.1/telnet.xinetd.inetutils
> create mode 100644
> meta-networking/recipes-connectivity/inetutils/inetutils-1.9.1/tftpd.xinetd.inetutils
>
> diff --git
> a/meta-networking/recipes-connectivity/inetutils/inetutils-1.9.1/rexec.xinetd.inetutils
>
> b/meta-networking/recipes-connectivity/inetutils/inetutils-1.9.1/rexec.xinetd.inetutils
> new file mode 100644
> index 000..80aed36
> --- /dev/null
> +++
> b/meta-networking/recipes-connectivity/inetutils/inetutils-1.9.1/rexec.xinetd.inetutils
> @@ -0,0 +1,20 @@
> +# default: off
> +# description:
> +# Rexecd is the server for the rexec program. The server provides remote
> +# execution facilities with authentication based on user names and
> +# passwords.
> +#
> +service exec
> +{
> + socket_type = stream
> + protocol= tcp
> + flags = NAMEINARGS
> + wait= no
> + user= root
> + group = root
> + log_on_success += USERID
> + log_on_failure += USERID
> + server = /usr/bin/tcpd
> + server_args = /usr/sbin/in.rexecd
> + disable = yes
> +}
> diff --git
> a/meta-networking/recipes-connectivity/inetutils/inetutils-1.9.1/rlogin.xinetd.inetutils
>
> b/meta-networking/recipes-connectivity/inetutils/inetutils-1.9.1/rlogin.xinetd.inetutils
> new file mode 100644
> index 000..00dbf93
> --- /dev/null
> +++
> b/meta-networking/recipes-connectivity/inetutils/inetutils-1.9.1/rlogin.xinetd.inetutils
> @@ -0,0 +1,23 @@
> +# default: off
> +# description:
> +# Rlogind is a server for the rlogin program. The server provides remote
> +# execution with authentication based on privileged port numbers from trusted
> +# host
> +#
> +service login
> +{
> + socket_type = stream
> + protocol= tcp
> + flags = NAMEINARGS
> + wait= no
> + user= root
> + group = root
> + log_on_success += USERID
> + log_on_failure += USERID
> + server = /usr/bin/tcpd
> + server_args = /usr/sbin/in.rlogind -a
> + disable = yes
> +}
> +
> +
> +
> diff --git
> a/meta-networking/recipes-connectivity/inetutils/inetutils-1.9.1/rsh.xinetd.inetutils
>
> b/meta-networking/recipes-connectivity/inetutils/inetutils-1.9.1/rsh.xinetd.inetutils
> new file mode 100644
> index 000..ad59b62
> --- /dev/null
> +++
> b/meta-networking/recipes-connectivity/inetutils/inetutils-1.9.1/rsh.xinetd.inetutils
> @@ -0,0 +1,21 @@
> +# default: off
> +# description:
> +# The rshd server is a server for the rcmd(3) routine and,
> +# consequently, for the rsh(1) program. The server provides
> +# remote execution facilities with authentication based on
> +# privileged port numbers from trusted hosts.
> +#
> +service shell
> +{
> + socket_type = stream
> + protocol= tcp
> + flags = NAMEINARGS
> + wait= no
> + user= root
> + group = root
> + log_on_success += USERID
> + log_on_failure += USERID
> + server = /usr/bin/tcpd
> + server_args = /usr/sbin/in.rshd -aL
> + disable = yes
> +}
> diff --git
> a/meta-networking/recipes-connectivity/inetutils/inetutils-1.9.1/telnet.xinetd.inetutils
>
> b/meta-networking/recipes-connectivity/inetutils/inetutils-1.9.1/telnet.xinetd.inetutils
> new file mode 100644
> index 000..2a2a12e
> --- /dev/null
> +++
> b/meta-networking/recipes-connectivity/inetutils/inetutils-1.9.1/telnet.xinetd.inetutils
> @@ -0,0 +1,1
Re: [oe] [meta-networking][PATCH] ipsec-tools: fix dependencies and enable two configuration
Merged, thanks.
-J.
[[meta-networking][PATCH] ipsec-tools: fix dependencies and enable two
configuration] On 13.07.16 (Tue 14:38) rongqing...@windriver.com wrote:
> From: "Roy.Li"
>
> ipsec-tools depends on bison-native
> enable ipv6 support by DISTRO_FEATURE, and enable shared library support.
>
> Signed-off-by: Roy.Li
> ---
> meta-networking/recipes-support/ipsec-tools/ipsec-tools_0.8.1.bb |6
> --
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/meta-networking/recipes-support/ipsec-tools/ipsec-tools_0.8.1.bb
> b/meta-networking/recipes-support/ipsec-tools/ipsec-tools_0.8.1.bb
> index ef753c0..c44d374 100644
> --- a/meta-networking/recipes-support/ipsec-tools/ipsec-tools_0.8.1.bb
> +++ b/meta-networking/recipes-support/ipsec-tools/ipsec-tools_0.8.1.bb
> @@ -5,7 +5,7 @@ SECTION = "console/network"
> LICENSE = "BSD"
> LIC_FILES_CHKSUM =
> "file://src/libipsec/pfkey.c;beginline=6;endline=31;md5=bc9b7ff40beff19fe6bc6aef26bd2b24"
>
> -DEPENDS = "virtual/kernel openssl readline flex"
> +DEPENDS = "virtual/kernel openssl readline flex bison-native"
>
> SRC_URI =
> "ftp://ftp.netbsd.org/pub/NetBSD/misc/ipsec-tools/0.8/ipsec-tools-${PV}.tar.bz2
> \
> file://0001-Fix-warning-with-gcc-4.8.patch \
> @@ -46,7 +46,9 @@ EXTRA_OECONF = "--with-kernel-headers=${STAGING_INCDIR} \
> --without-libradius \
> --without-gssapi \
> --without-libpam \
> ---disable-security-context"
> +--disable-security-context \
> +--enable-shared \
> +${@base_contains('DISTRO_FEATURES', 'ipv6',
> '--enable-ipv6=yes', '', d)}"
>
> # See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530527
> CFLAGS += "-fno-strict-aliasing"
--
-Joe MacDonald.
:wq
signature.asc
Description: Digital signature
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-networking][PATCH v2] Upgrade vsftpd to 3.0.0
On Wednesday 17 July 2013 14:43:16 Joe MacDonald wrote: > This adds (unconditional) support for tcp-wrappers and makes it a > requirement for the upgraded vsftp. Is this something we could make > conditional based on tcp-wrappers being present? Or does anyone think > this is something worth doing? tcp-wrappers is coming from oe-core and > I don't have any systems where the new requirement would be a problem, > but does anyone else have a system they'd want vsftp without > tcp-wrappers? We've recently added tcp-wrappers to a number of recipes in OE-Core; at the time there was a discussion about a possible follow-up to add a DISTRO_FEATURES item to disable it system-wide. I guess whether or not it's worth it depends on what the overhead of having it enabled is. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-initramfs] Pull request 20130717
The following changes since commit 8f2bec330b1463dc39d35769214cb324a1d4fdc9: linux-yocto-tiny-kexecboot_3.8: use 'require' instead of 'include' for compliance (2013-07-08 13:36:04 +0100) are available in the git repository at: https://github.com/andrea-adami/meta-handheld master for you to fetch changes up to e71e1528062c6b24ee1f93e69b1f529b15edd919: linux-yocto-tiny-kexecboot_3.8: tosa-tiny.scc: reflect last patchset changes (2013-07-17 23:19:43 +0200) Andrea Adami (22): linux-yocto_3.8: pxamci-regulator.patch: refactor headers linux-yocto_3.8: sharpsl_param.patch: refactor for upstream submission linux-yocto_3.8: collie-eraseinfo.patch: refactor for upstream submission linux-yocto_3.8: collie-jedec-probe.patch: refactor for upstream submission linux-yocto_3.8: locomo_kbd_tweak-r2.patch: refactor header and footer linux-yocto_3.8: ucb1x00-device.patch: refactor for upstream submission linux-yocto_3.8: add ucb1x00-device.patch linux-yocto_3.8: add collie_battery-dev-pm.patch linux-yocto_3.8: collie.scc: reflect last patchset changes linux-yocto_3.8: tosa.scc: add tosa_battery_irq_to_gpio.patch linux-yocto_3.8: tosa.cfg: add ts WM97XX and tosa_battery modules linux-yocto-tiny-kexecboot_3.8: resync locomo_kbd_tweak-r2.patch with linux-yocto_3.8 linux-yocto-tiny-kexecboot_3.8: resync collie-eraseinfo.patch with linux-yocto_3.8 linux-yocto-tiny-kexecboot_3.8: resync collie-jedec-probe.patch with linux-yocto_3.8 linux-yocto-tiny-kexecboot_3.8: resync pxamci-regulator.patch with linux-yocto_3.8 linux-yocto-tiny-kexecboot_3.8: resync sharpsl_param.patch with linux-yocto_3.8 linux-yocto-tiny-kexecboot_3.8: resync mcp-device.patch with linux-yocto_3.8 linux-yocto-tiny-kexecboot_3.8: add ucb1x00.patch from linux-yocto_3.8 linux-yocto-tiny-kexecboot_3.8: add collie_battery-dev-pm.patch from linux-yocto_3.8 linux-yocto-tiny-kexecboot_3.8: collie-tiny.scc: reflect last patchset changes linux-yocto-tiny-kexecboot_3.8: add tosa_battery_irq_to_gpio.patch from linux-yocto_3.8 linux-yocto-tiny-kexecboot_3.8: tosa-tiny.scc: reflect last patchset changes .../linux/linux-yocto-3.8/collie/collie.scc| 2 + .../patches-locomokbd/locomo_kbd_tweak-r2.patch| 12 -- .../patches/patches-mfd/mcp-device.patch | 48 +++--- .../patches/patches-mfd/ucb1x00-device.patch | 28 + .../patches/patches-mtd/collie-eraseinfo.patch | 25 --- .../patches/patches-mtd/collie-jedec-probe.patch | 25 --- .../patches-power/collie_battery-dev-pm.patch | 39 ++ .../patches-power/tosa_battery_irq_to_gpio.patch | 39 ++ .../patches/patches-pxa/pxamci-regulator.patch | 13 -- .../patches/patches-pxa/sharpsl_param.patch| 25 +++ recipes-kernel/linux/linux-yocto-3.8/tosa/tosa.cfg | 8 recipes-kernel/linux/linux-yocto-3.8/tosa/tosa.scc | 1 + .../collie/collie-tiny.scc | 2 + .../patches-locomokbd/locomo_kbd_tweak-r2.patch| 12 -- .../patches/patches-mfd/mcp-device.patch | 48 +++--- .../patches/patches-mfd/ucb1x00-device.patch | 28 + .../patches/patches-mtd/collie-eraseinfo.patch | 25 --- .../patches/patches-mtd/collie-jedec-probe.patch | 25 --- .../patches-power/collie_battery-dev-pm.patch | 39 ++ .../patches-power/tosa_battery_irq_to_gpio.patch | 39 ++ .../patches/patches-pxa/pxamci-regulator.patch | 13 -- .../patches/patches-pxa/sharpsl_param.patch| 25 +++ .../tosa/tosa-tiny.scc | 1 + 23 files changed, 402 insertions(+), 120 deletions(-) create mode 100644 recipes-kernel/linux/linux-yocto-3.8/patches/patches-mfd/ucb1x00-device.patch create mode 100644 recipes-kernel/linux/linux-yocto-3.8/patches/patches-power/collie_battery-dev-pm.patch create mode 100644 recipes-kernel/linux/linux-yocto-3.8/patches/patches-power/tosa_battery_irq_to_gpio.patch create mode 100644 recipes-kernel/linux/linux-yocto-tiny-kexecboot-3.8/patches/patches-mfd/ucb1x00-device.patch create mode 100644 recipes-kernel/linux/linux-yocto-tiny-kexecboot-3.8/patches/patches-power/collie_battery-dev-pm.patch create mode 100644 recipes-kernel/linux/linux-yocto-tiny-kexecboot-3.8/patches/patches-power/tosa_battery_irq_to_gpio.patch ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-handheld] Pull request 20130717
The following changes since commit 8f2bec330b1463dc39d35769214cb324a1d4fdc9: linux-yocto-tiny-kexecboot_3.8: use 'require' instead of 'include' for compliance (2013-07-08 13:36:04 +0100) are available in the git repository at: https://github.com/andrea-adami/meta-handheld master for you to fetch changes up to e71e1528062c6b24ee1f93e69b1f529b15edd919: linux-yocto-tiny-kexecboot_3.8: tosa-tiny.scc: reflect last patchset changes (2013-07-17 23:19:43 +0200) Andrea Adami (22): linux-yocto_3.8: pxamci-regulator.patch: refactor headers linux-yocto_3.8: sharpsl_param.patch: refactor for upstream submission linux-yocto_3.8: collie-eraseinfo.patch: refactor for upstream submission linux-yocto_3.8: collie-jedec-probe.patch: refactor for upstream submission linux-yocto_3.8: locomo_kbd_tweak-r2.patch: refactor header and footer linux-yocto_3.8: ucb1x00-device.patch: refactor for upstream submission linux-yocto_3.8: add ucb1x00-device.patch linux-yocto_3.8: add collie_battery-dev-pm.patch linux-yocto_3.8: collie.scc: reflect last patchset changes linux-yocto_3.8: tosa.scc: add tosa_battery_irq_to_gpio.patch linux-yocto_3.8: tosa.cfg: add ts WM97XX and tosa_battery modules linux-yocto-tiny-kexecboot_3.8: resync locomo_kbd_tweak-r2.patch with linux-yocto_3.8 linux-yocto-tiny-kexecboot_3.8: resync collie-eraseinfo.patch with linux-yocto_3.8 linux-yocto-tiny-kexecboot_3.8: resync collie-jedec-probe.patch with linux-yocto_3.8 linux-yocto-tiny-kexecboot_3.8: resync pxamci-regulator.patch with linux-yocto_3.8 linux-yocto-tiny-kexecboot_3.8: resync sharpsl_param.patch with linux-yocto_3.8 linux-yocto-tiny-kexecboot_3.8: resync mcp-device.patch with linux-yocto_3.8 linux-yocto-tiny-kexecboot_3.8: add ucb1x00.patch from linux-yocto_3.8 linux-yocto-tiny-kexecboot_3.8: add collie_battery-dev-pm.patch from linux-yocto_3.8 linux-yocto-tiny-kexecboot_3.8: collie-tiny.scc: reflect last patchset changes linux-yocto-tiny-kexecboot_3.8: add tosa_battery_irq_to_gpio.patch from linux-yocto_3.8 linux-yocto-tiny-kexecboot_3.8: tosa-tiny.scc: reflect last patchset changes .../linux/linux-yocto-3.8/collie/collie.scc| 2 + .../patches-locomokbd/locomo_kbd_tweak-r2.patch| 12 -- .../patches/patches-mfd/mcp-device.patch | 48 +++--- .../patches/patches-mfd/ucb1x00-device.patch | 28 + .../patches/patches-mtd/collie-eraseinfo.patch | 25 --- .../patches/patches-mtd/collie-jedec-probe.patch | 25 --- .../patches-power/collie_battery-dev-pm.patch | 39 ++ .../patches-power/tosa_battery_irq_to_gpio.patch | 39 ++ .../patches/patches-pxa/pxamci-regulator.patch | 13 -- .../patches/patches-pxa/sharpsl_param.patch| 25 +++ recipes-kernel/linux/linux-yocto-3.8/tosa/tosa.cfg | 8 recipes-kernel/linux/linux-yocto-3.8/tosa/tosa.scc | 1 + .../collie/collie-tiny.scc | 2 + .../patches-locomokbd/locomo_kbd_tweak-r2.patch| 12 -- .../patches/patches-mfd/mcp-device.patch | 48 +++--- .../patches/patches-mfd/ucb1x00-device.patch | 28 + .../patches/patches-mtd/collie-eraseinfo.patch | 25 --- .../patches/patches-mtd/collie-jedec-probe.patch | 25 --- .../patches-power/collie_battery-dev-pm.patch | 39 ++ .../patches-power/tosa_battery_irq_to_gpio.patch | 39 ++ .../patches/patches-pxa/pxamci-regulator.patch | 13 -- .../patches/patches-pxa/sharpsl_param.patch| 25 +++ .../tosa/tosa-tiny.scc | 1 + 23 files changed, 402 insertions(+), 120 deletions(-) create mode 100644 recipes-kernel/linux/linux-yocto-3.8/patches/patches-mfd/ucb1x00-device.patch create mode 100644 recipes-kernel/linux/linux-yocto-3.8/patches/patches-power/collie_battery-dev-pm.patch create mode 100644 recipes-kernel/linux/linux-yocto-3.8/patches/patches-power/tosa_battery_irq_to_gpio.patch create mode 100644 recipes-kernel/linux/linux-yocto-tiny-kexecboot-3.8/patches/patches-mfd/ucb1x00-device.patch create mode 100644 recipes-kernel/linux/linux-yocto-tiny-kexecboot-3.8/patches/patches-power/collie_battery-dev-pm.patch create mode 100644 recipes-kernel/linux/linux-yocto-tiny-kexecboot-3.8/patches/patches-power/tosa_battery_irq_to_gpio.patch ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-initramfs] Pull request 20130717
Please discard this request, wrong subject line...intended for [meta-handheld] On Thu, Jul 18, 2013 at 12:09 AM, Andrea Adami wrote: > The following changes since commit 8f2bec330b1463dc39d35769214cb324a1d4fdc9: > > linux-yocto-tiny-kexecboot_3.8: use 'require' instead of 'include' for > compliance (2013-07-08 13:36:04 +0100) > > are available in the git repository at: > > https://github.com/andrea-adami/meta-handheld master > > for you to fetch changes up to e71e1528062c6b24ee1f93e69b1f529b15edd919: > > linux-yocto-tiny-kexecboot_3.8: tosa-tiny.scc: reflect last patchset > changes (2013-07-17 23:19:43 +0200) > > > Andrea Adami (22): > linux-yocto_3.8: pxamci-regulator.patch: refactor headers > linux-yocto_3.8: sharpsl_param.patch: refactor for upstream submission > linux-yocto_3.8: collie-eraseinfo.patch: refactor for upstream > submission > linux-yocto_3.8: collie-jedec-probe.patch: refactor for upstream > submission > linux-yocto_3.8: locomo_kbd_tweak-r2.patch: refactor header and footer > linux-yocto_3.8: ucb1x00-device.patch: refactor for upstream submission > linux-yocto_3.8: add ucb1x00-device.patch > linux-yocto_3.8: add collie_battery-dev-pm.patch > linux-yocto_3.8: collie.scc: reflect last patchset changes > linux-yocto_3.8: tosa.scc: add tosa_battery_irq_to_gpio.patch > linux-yocto_3.8: tosa.cfg: add ts WM97XX and tosa_battery modules > linux-yocto-tiny-kexecboot_3.8: resync locomo_kbd_tweak-r2.patch with > linux-yocto_3.8 > linux-yocto-tiny-kexecboot_3.8: resync collie-eraseinfo.patch with > linux-yocto_3.8 > linux-yocto-tiny-kexecboot_3.8: resync collie-jedec-probe.patch with > linux-yocto_3.8 > linux-yocto-tiny-kexecboot_3.8: resync pxamci-regulator.patch with > linux-yocto_3.8 > linux-yocto-tiny-kexecboot_3.8: resync sharpsl_param.patch with > linux-yocto_3.8 > linux-yocto-tiny-kexecboot_3.8: resync mcp-device.patch with > linux-yocto_3.8 > linux-yocto-tiny-kexecboot_3.8: add ucb1x00.patch from linux-yocto_3.8 > linux-yocto-tiny-kexecboot_3.8: add collie_battery-dev-pm.patch from > linux-yocto_3.8 > linux-yocto-tiny-kexecboot_3.8: collie-tiny.scc: reflect last patchset > changes > linux-yocto-tiny-kexecboot_3.8: add tosa_battery_irq_to_gpio.patch from > linux-yocto_3.8 > linux-yocto-tiny-kexecboot_3.8: tosa-tiny.scc: reflect last patchset > changes > > .../linux/linux-yocto-3.8/collie/collie.scc| 2 + > .../patches-locomokbd/locomo_kbd_tweak-r2.patch| 12 -- > .../patches/patches-mfd/mcp-device.patch | 48 > +++--- > .../patches/patches-mfd/ucb1x00-device.patch | 28 + > .../patches/patches-mtd/collie-eraseinfo.patch | 25 --- > .../patches/patches-mtd/collie-jedec-probe.patch | 25 --- > .../patches-power/collie_battery-dev-pm.patch | 39 ++ > .../patches-power/tosa_battery_irq_to_gpio.patch | 39 ++ > .../patches/patches-pxa/pxamci-regulator.patch | 13 -- > .../patches/patches-pxa/sharpsl_param.patch| 25 +++ > recipes-kernel/linux/linux-yocto-3.8/tosa/tosa.cfg | 8 > recipes-kernel/linux/linux-yocto-3.8/tosa/tosa.scc | 1 + > .../collie/collie-tiny.scc | 2 + > .../patches-locomokbd/locomo_kbd_tweak-r2.patch| 12 -- > .../patches/patches-mfd/mcp-device.patch | 48 > +++--- > .../patches/patches-mfd/ucb1x00-device.patch | 28 + > .../patches/patches-mtd/collie-eraseinfo.patch | 25 --- > .../patches/patches-mtd/collie-jedec-probe.patch | 25 --- > .../patches-power/collie_battery-dev-pm.patch | 39 ++ > .../patches-power/tosa_battery_irq_to_gpio.patch | 39 ++ > .../patches/patches-pxa/pxamci-regulator.patch | 13 -- > .../patches/patches-pxa/sharpsl_param.patch| 25 +++ > .../tosa/tosa-tiny.scc | 1 + > 23 files changed, 402 insertions(+), 120 deletions(-) > create mode 100644 > recipes-kernel/linux/linux-yocto-3.8/patches/patches-mfd/ucb1x00-device.patch > create mode 100644 > recipes-kernel/linux/linux-yocto-3.8/patches/patches-power/collie_battery-dev-pm.patch > create mode 100644 > recipes-kernel/linux/linux-yocto-3.8/patches/patches-power/tosa_battery_irq_to_gpio.patch > create mode 100644 > recipes-kernel/linux/linux-yocto-tiny-kexecboot-3.8/patches/patches-mfd/ucb1x00-device.patch > create mode 100644 > recipes-kernel/linux/linux-yocto-tiny-kexecboot-3.8/patches/patches-power/collie_battery-dev-pm.patch > create mode 100644 > recipes-kernel/linux/linux-yocto-tiny-kexecboot-3.8/patches/patches-power/tosa_battery_irq_to_gpio.patch ___ Openembedded-devel mailing list Opene
Re: [oe] [meta-oe][PATCH] qt-creator: add new recipe for version 2.7.2
On 7 July 2013 06:10, Otavio Salvador wrote: > On Fri, Jul 5, 2013 at 11:46 PM, Jonathan Liu wrote: >> Signed-off-by: Jonathan Liu > > This recipe seems to be usable in target but it'd be great if Qt > Creator could also be build as a toolchain part; did you try it? I haven't tried that. Regards, Jonathan ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH] qt-creator: add new recipe for version 2.7.2
On Wed, Jul 17, 2013 at 10:04 PM, Jonathan Liu wrote: > On 7 July 2013 06:10, Otavio Salvador wrote: >> On Fri, Jul 5, 2013 at 11:46 PM, Jonathan Liu wrote: >>> Signed-off-by: Jonathan Liu >> >> This recipe seems to be usable in target but it'd be great if Qt >> Creator could also be build as a toolchain part; did you try it? > > I haven't tried that. Is it at your roadmap? -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://projetos.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH] qt-creator: add new recipe for version 2.7.2
On 18 July 2013 11:09, Otavio Salvador wrote: > On Wed, Jul 17, 2013 at 10:04 PM, Jonathan Liu wrote: >> On 7 July 2013 06:10, Otavio Salvador wrote: >>> On Fri, Jul 5, 2013 at 11:46 PM, Jonathan Liu wrote: Signed-off-by: Jonathan Liu >>> >>> This recipe seems to be usable in target but it'd be great if Qt >>> Creator could also be build as a toolchain part; did you try it? >> >> I haven't tried that. > > Is it at your roadmap? Not at the moment. Feel free to have a go at it if you like. Regards, Jonathan ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH] licences: Add iozone3, SMAIL_GPL
Hello,
Please apply this patch .
Thanks,
chunrong
-Original Message-
From: Guo Chunrong-B40290
Sent: Thursday, July 11, 2013 10:32 AM
To: openembedded-devel@lists.openembedded.org
Cc: Liu Ting-B28495; Luo Zhenhua-B19537; Guo Chunrong-B40290; Yu
Zongchun-B40527; Guo Chunrong-B40290
Subject: [meta-oe][PATCH] licences: Add iozone3, SMAIL_GPL
*fix the fllowing warning
|WARNING:debianutils: No generic license file exists for: SMAIL_GPL in any
provider
|WARNING:iozone3: No generic license file exists for: iozone3 in any
provider
Signed-off-by: Chunrong Guo
---
meta-oe/conf/layer.conf|2 +
meta-oe/licenses/SMAIL_GPL | 164
meta-oe/licenses/iozone3 | 62 +
3 files changed, 228 insertions(+), 0 deletions(-) create mode 100644
meta-oe/licenses/SMAIL_GPL create mode 100644 meta-oe/licenses/iozone3
diff --git a/meta-oe/conf/layer.conf b/meta-oe/conf/layer.conf index
68f7823..bc025bb 100644
--- a/meta-oe/conf/layer.conf
+++ b/meta-oe/conf/layer.conf
@@ -23,6 +23,8 @@ BBFILE_PATTERN_openembedded-layer := "^${LAYERDIR}/"
BBFILE_PRIORITY_openembedded-layer = "6"
+LICENSE_PATH += "${LAYERDIR}/licenses"
+
SIGGEN_EXCLUDERECIPES_ABISAFE += " \
pointercal-xinput \
mplayer-common \
diff --git a/meta-oe/licenses/SMAIL_GPL b/meta-oe/licenses/SMAIL_GPL new file
mode 100644 index 000..dfc3fd1
--- /dev/null
+++ b/meta-oe/licenses/SMAIL_GPL
@@ -0,0 +1,164 @@
+This is the Debian GNU/Linux package debianutils.
+
+It is an original Debian package. Programs in it were maintained by
+Guy Maor , and are now maintained by Clint Adams
+.
+
+All its programs except readlink, savelog, and which may be
+redistributed under the terms of the GNU GPL, Version 2 or later, found
+on Debian systems in the file /usr/share/common-licenses/GPL.
+
+which is in the public domain.
+
+readlink is Copyright (c) 1997 Kenneth Stailey, and may also be
+distributed under the terms of the BSD copyright.
+
+savelog may be redistributed under the following terms: (The rest of
+this file consists of savelog's distribution terms.)
+
+#ident "@(#)smail:RELEASE-3_2:COPYING,v 1.2 1996/06/14 18:59:10 woods Exp"
+
+SMAIL GENERAL PUBLIC LICENSE
+ (Clarified 11 Feb 1988)
+
+ Copyright (C) 1988 Landon Curt Noll & Ronald S. Karr Copyright (C)
+ 1992 Ronald S. Karr Copyleft (GNU) 1988 Landon Curt Noll & Ronald S.
+ Karr
+
+ Everyone is permitted to copy and distribute verbatim copies of this
+ license, but changing it is not allowed. You can also use this
+ wording to make the terms for other programs.
+
+ The license agreements of most software companies keep you at the
+mercy of those companies. By contrast, our general public license is
+intended to give everyone the right to share SMAIL. To make sure that
+you get the rights we want you to have, we need to make restrictions
+that forbid anyone to deny you these rights or to ask you to surrender
+the rights. Hence this license agreement.
+
+ Specifically, we want to make sure that you have the right to give
+away copies of SMAIL, that you receive source code or else can get it
+if you want it, that you can change SMAIL or use pieces of it in new
+free programs, and that you know you can do these things.
+
+ To make sure that everyone has such rights, we have to forbid you to
+deprive anyone else of these rights. For example, if you distribute
+copies of SMAIL, you must give the recipients all the rights that you
+have. You must make sure that they, too, receive or can get the source
+code. And you must tell them their rights.
+
+ Also, for our own protection, we must make certain that everyone
+finds out that there is no warranty for SMAIL. If SMAIL is modified by
+someone else and passed on, we want its recipients to know that what
+they have is not what we distributed, so that any problems introduced
+by others will not reflect on our reputation.
+
+ Therefore we (Landon Curt Noll and Ronald S. Karr) make the following
+terms which say what you must do to be allowed to distribute or change
+SMAIL.
+
+
+ COPYING POLICIES
+
+ 1. You may copy and distribute verbatim copies of SMAIL source code
+as you receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy a valid copyright notice "Copyright
+(C) 1988 Landon Curt Noll & Ronald S. Karr" (or with whatever year is
+appropriate); keep intact the notices on all files that refer to this
+License Agreement and to the absence of any warranty; and give any
+other recipients of the SMAIL program a copy of this License Agreement
+along with the program. You may charge a distribution fee for the
+physical act of transferring a copy.
+
+ 2. You may modify your copy or copies of SMAIL or any portion of it,
+and copy and distribute such modifications under the terms of Paragraph
+1 above, provided that y
