Re: [yocto] [poky] Poky 10.0.0 release name.
On 4 September 2013 14:26, Flanagan, Elizabeth wrote: > Poky 10.0.0 will be codenamed "dora" The Yolkfolk? ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] CFLAGS and configurations
Hi Khem, Sorry if this has been asked too many times before, but is there is an advantage to specifying a whole bunch of CFLAGS for every invocation of the compiler versus specifying them during the ./configure? For example, if one ./configures their cross-compiler with things like -march, -mtune, --sysroot, etc then those will be the defaults. If nothing is otherwise specified, these ./configure options are what will be used. But if these things aren't specified at ./configure time, then every time the cross-compiler is invoked these options need to be specified. Looking, roughly, through some of the log.do_compile logs when cross-compiling applications for the target, and looking at the output of invoking the cross-compile with the "-v" flag, it appears most of these flags need to be specified for each invocation of the compiler. The ./configure specifies the sysroot, for example, but doesn't try to specify any of the -mtune or -march (etc) flags. Wouldn't it be easier the other way? That way we don't have to worry that some component's build isn't clobbering our required CFLAGS? Do the SDK cross-compilers work the same way? Are they ./configure'd similarly? Best regards, Trevor ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH 0/4] Refactor kernel recipes
On 10 September 2013 23:36, wrote: > From: Philipp Wagner > > Hi, > > as follow-up to the discussion in > [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi: Add version 3.8.13 > I've refactored the kernel recipes a bit and included all discussed > kernel versions. The default is now 3.6. > > I've left linux.inc as-is, as this seems to be copied from meta-oe. Should > we include this directly instead of copying it here? > > Philipp > > Philipp Wagner (4): > Refactor kernel recipes to reduce code duplication > Remove tabs from recipe > Make Linux 3.6 the default for Raspberry Pi > Add kernel 3.8 and 3.11 for Raspberry Pi > > conf/machine/include/rpi-default-providers.inc | 3 + > recipes-kernel/linux/linux-raspberrypi.inc | 34 + > recipes-kernel/linux/linux-raspberrypi_3.11.0.bb | 6 + > recipes-kernel/linux/linux-raspberrypi_3.2.27.bb | 33 + > recipes-kernel/linux/linux-raspberrypi_3.6.11.bb | 33 + > recipes-kernel/linux/linux-raspberrypi_3.8.13.bb | 6 + > recipes-kernel/linux/linux.inc | 174 > +++ > 7 files changed, 140 insertions(+), 149 deletions(-) > create mode 100644 recipes-kernel/linux/linux-raspberrypi.inc > create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.11.0.bb > create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.8.13.bb > > -- > 1.8.1.4 Testing this now with PREFERRED_VERSION_linux-raspberrypi = "3.8%". -- Paul Barker Email: p...@paulbarker.me.uk http://www.paulbarker.me.uk ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] CFLAGS and configurations
On Wed, Sep 11, 2013 at 12:10 AM, Trevor Woerner wrote: > Hi Khem, > > Sorry if this has been asked too many times before, but is there is an > advantage to specifying a whole bunch of CFLAGS for every invocation > of the compiler versus specifying them during the ./configure? > Keep in mind that all packages we build are not autotooled. There are other component build systems besides autotools that come into play like scons, cmake and so on and we have to be consistent across all of them. > For example, if one ./configures their cross-compiler with things like > -march, -mtune, --sysroot, etc then those will be the defaults. If > nothing is otherwise specified, these ./configure options are what > will be used. But if these things aren't specified at ./configure > time, then every time the cross-compiler is invoked these options need > to be specified. > > Looking, roughly, through some of the log.do_compile logs when > cross-compiling applications for the target, and looking at the output > of invoking the cross-compile with the "-v" flag, it appears most of > these flags need to be specified for each invocation of the compiler. > The ./configure specifies the sysroot, for example, but doesn't try to > specify any of the -mtune or -march (etc) flags. > > Wouldn't it be easier the other way? That way we don't have to worry > that some component's build isn't clobbering our required CFLAGS? yes for packages using autotools may be but I dont see a big downside of using CFLAGS either. It gives you same functionality but is a bit more homogenous across all kind of components. > > Do the SDK cross-compilers work the same way? Are they ./configure'd > similarly? We now have relocatable SDKs and one feature that we use it making sure the we have the ability to change sysroot on install. So this will have to be passed via CFLAGS. > > Best regards, > Trevor ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Add new module to recipe + meta-toolchain-qt: add gdb
Philipp Wagner writes: > > Hi Jose, > ... > > To do that, just start a new console, do *not* source the > /opt/poky/1.4.2/environment-* file. This should give you an empty > PYTHONHOME variable and an unmodified PATH, so you can just use the > regular tools on the desktop. > > Philipp > Hello Philipp That works. But then we have to use a qtcreator.sh with the poky PYTHOHOME to debug Target and another qtcreator2.sh without it to debug Desktop. There is another workaround also: we can add to the QTCreator-Project-Options-Desktop-Environment a new PYTHONHOME value and it seems to have preference over the environment.sh value. This is to be done for every project. However we are new to Yocto and have problems finding and understanding things. For example this gdb/pythons thing: Why python is recompiled and created on /opt/poky sdk environment? Why not use host python? What are the steps to create gdb (or any other utlity) on the sdk directory (/opt/poky/..)? Where is the python recipe to introduce it in host sdk to follow as an example? Thanks and best regards. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] dev-manual: use ##OEROOT## instead of ##COREBASE##
The variable ##COREBASE## has been deprecated, so use ##OEROOT## instead. Signed-off-by: Ross Burton --- documentation/dev-manual/dev-manual-common-tasks.xml | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 7fa9149..9fadd7b 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -4980,15 +4980,15 @@ BBFILES ?= "" BBLAYERS ?= " \ - ##COREBASE##/meta \ - ##COREBASE##/meta-yocto \ - ##COREBASE##/meta-yocto-bsp \ - ##COREBASE##/meta-mylayer \ + ##OEROOT##/meta \ + ##OEROOT##/meta-yocto \ + ##OEROOT##/meta-yocto-bsp \ + ##OEROOT##/meta-mylayer \ " BBLAYERS_NON_REMOVABLE ?= " \ - ##COREBASE##/meta \ - ##COREBASE##/meta-yocto \ + ##OEROOT##/meta \ + ##OEROOT##/meta-yocto \ " Creating and providing an archive of the -- 1.7.10.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Meta-security][PATCH 1/3] snort: add recipe
On 09/10/2013 09:01 PM, b40...@freescale.com wrote: From: Chunrong Guo *snort - a free lightweight network intrusion detection system for UNIX and Windows Signed-off-by: Chunrong Guo --- recipes-security/snort/files/default | 42 ++ .../snort/files/disable-dap-address-space-id.patch | 52 +++ .../snort/files/disable-inaddr-none.patch | 75 recipes-security/snort/files/logrotate | 12 + recipes-security/snort/files/snort.init| 425 recipes-security/snort/files/volatiles |2 + recipes-security/snort/snort_2.9.4.6.bb| 87 7 files changed, 695 insertions(+), 0 deletions(-) create mode 100644 recipes-security/snort/files/default create mode 100644 recipes-security/snort/files/disable-dap-address-space-id.patch create mode 100644 recipes-security/snort/files/disable-inaddr-none.patch create mode 100644 recipes-security/snort/files/logrotate create mode 100755 recipes-security/snort/files/snort.init create mode 100644 recipes-security/snort/files/volatiles create mode 100644 recipes-security/snort/snort_2.9.4.6.bb diff --git a/recipes-security/snort/files/default b/recipes-security/snort/files/default new file mode 100644 index 000..afd3840 --- /dev/null +++ b/recipes-security/snort/files/default @@ -0,0 +1,42 @@ +# Parameters for the daemon +# Add any additional parameteres here. +PARAMS="-m 027 -D -d " +# +# Snort user +# This user will be used to launch snort. Notice that the +# preinst script of the package might do changes to the user +# (home directory, User Name) when the package is upgraded or +# reinstalled. So, do *not* change this to 'root' or to any other user +# unless you are sure there is no problem with those changes being introduced. +# +SNORTUSER="snort" +# +# Logging directory +# Snort logs will be dropped here and this will be the home +# directory for the SNORTUSER. If you change this value you should +# change the /etc/logrotate.d/snort definition too, otherwise logs +# will not be rotated properly. +# +LOGDIR="/var/log/snort" +# +# Snort group +# This is the group that the snort user will be added to. +# +SNORTGROUP="snort" +# +# Allow Snort's init.d script to work if the configured interfaces +# are not available. Set this to yes if you configure Snort with +# multiple interfaces but some might not be available on boot +# (e.g. wireless interfaces) +# +# Note: In order for this to work the 'iproute' package needs to +# be installed. +ALLOW_UNAVAILABLE="no" + +# Local configs +# +LOCAL_SNORT_STARTUP=boot +LOCAL_SNORT_HOME_NET="192.168.0.0/16" +LOCAL_SNORT_INTERFACE="" +LOCAL_SNORT_STATS_RCPT="root" +LOCAL_SNORT_STATS_THRESHOLD="1" diff --git a/recipes-security/snort/files/disable-dap-address-space-id.patch b/recipes-security/snort/files/disable-dap-address-space-id.patch new file mode 100644 index 000..39e5c9c --- /dev/null +++ b/recipes-security/snort/files/disable-dap-address-space-id.patch @@ -0,0 +1,52 @@ +Upstream-Status:Inappropriate [embedded specific] + +fix the below error: +checking for dap address space id... configure: +configure: error: cannot run test program while cross compiling + + +Signed-off-by: Chunrong Guo + +--- a/configure.in 2013-08-23 00:06:37.239361932 -0500 b/configure.in 2013-08-23 00:07:32.860266534 -0500 +@@ -679,23 +679,23 @@ + + AC_CHECK_FUNCS([daq_hup_apply] [daq_acquire_with_meta]) + +-AC_MSG_CHECKING([for daq address space ID]) +-AC_RUN_IFELSE( +-[AC_LANG_PROGRAM( +-[[ +-#include +-]], +-[[ +- DAQ_PktHdr_t hdr; +- hdr.address_space_id = 0; +-]])], +-[have_daq_address_space_id="yes"], +-[have_daq_address_space_id="no"]) +-AC_MSG_RESULT($have_daq_address_space_id) +-if test "x$have_daq_address_space_id" = "xyes"; then +-AC_DEFINE([HAVE_DAQ_ADDRESS_SPACE_ID],[1], +-[DAQ version supports address space ID in header.]) +-fi ++#AC_MSG_CHECKING([for daq address space ID]) ++#AC_RUN_IFELSE( ++#[AC_LANG_PROGRAM( ++#[[ ++##include ++#]], ++#[[ ++# DAQ_PktHdr_t hdr; ++# hdr.address_space_id = 0; ++#]])], ++have_daq_address_space_id="yes" ++#[have_daq_address_space_id="no"]) ++#AC_MSG_RESULT($have_daq_address_space_id) ++#if test "x$have_daq_address_space_id" = "xyes"; then ++#AC_DEFINE([HAVE_DAQ_ADDRESS_SPACE_ID],[1], ++#[DAQ version supports address space ID in header.]) ++#fi + + # any sparc platform has to have this one defined. + AC_MSG_CHECKING(for sparc) diff --git a/recipes-security/snort/files/disable-inaddr-none.patch b/recipes-security/snort/files/disable-inaddr-none.patch new file mode 100644 index 000..9dafe63 --- /dev/null +++ b/recipes-security/snort/files/disable-inaddr-none.patch @@ -0,0 +1,75 @@ +Upstream-Status: Inappropriate [embedded specific] + +fix the below error: +checking for INADDR_NONE... configure: +configure: error: cannot run test program while cross compiling + +Signed-off-by: Chunrong Guo + + +--- a/configure.in
Re: [yocto] [Meta-security][PATCH 3/3] barnyard: add recipe
On 09/10/2013 09:06 PM, b40...@freescale.com wrote:
From: Chunrong Guo
*Barnyard is a output system for Snort
Signed-off-by: Chunrong Guo
---
recipes-security/barnyard/barnyard_0.2.0.bb | 22 ++
1 files changed, 22 insertions(+), 0 deletions(-)
create mode 100644 recipes-security/barnyard/barnyard_0.2.0.bb
diff --git a/recipes-security/barnyard/barnyard_0.2.0.bb
b/recipes-security/barnyard/barnyard_0.2.0.bb
new file mode 100644
index 000..a13ebdc
--- /dev/null
+++ b/recipes-security/barnyard/barnyard_0.2.0.bb
@@ -0,0 +1,22 @@
+DESCRIPTION = "Barnyard is a output system for Snort."
+HOMEPAGE = "http://www.snort.org/";
+LICENSE = "QPL"
+LIC_FILES_CHKSUM = "file://LICENSE.QPL;md5=1b8ff8c0012b5a2d647357699bf44b41"
+
+DEPENDS = "libpcap"
+RDEPENDS_${PN} = "libpcap"
DEPENDS are also RDEPENDS so this is extra and not needed.
+
+SRC_URI = " ${GENTOO_MIRROR}/${P}.tar.gz;name=tarball \
You don't want to use ${P} as it will be prefixed with any multilib type
of extension, it's better to use ${BP} which won't be expanded.
+ "
+SRC_URI[tarball.md5sum] = "be3283028cf414b52b220308ceb411e9"
+SRC_URI[tarball.sha256sum] =
"09e0f8e095e79cfe70ea069d13e7d02521a504a1f400a45556a634dccfd31a3a"
+
+
+S = "${WORKDIR}/${P}"
Same as above, this is also the default, so you should not need to
specify this item.
+inherit autotools pkgconfig
+
+do_configure_prepend () {
+ #fix hardcoded include path
+ sed -i -e 's:extra_incl=-I/usr/include/pcap::g' ${S}/configure.in
+}
+
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to customize a file coming from another recipe?
I'm building w/the Arago distribution which contains lighttpd for a web server. I include this in my image as follows: IMAGE_INSTALL = "packagegroup-core-boot \ ... lighttpd lighttpd-module-cgi lighttpd-module-compress lighttpd-module-expire \ ... " This installs a default configuration file for the service which I now want to customize. What is the recommended way to overwrite or customize files in another package? Is the best course to create a recipe bbappend for the lighttpd_1.4.31.bb file that is being used? And can I just include a new file with the same name in my append and will it overwrite the old one, or do I need to create an actual patch file? Or is it better to create a new separate recipe that just ships my version of the configuration file? How are conflicts handled when two recipes attempt to install the same file? Thanks, Brad ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to customize a file coming from another recipe?
I'm building w/the Arago distribution which contains lighttpd for a web server. I include this in my image as follows: IMAGE_INSTALL = "packagegroup-core-boot \ ... lighttpd lighttpd-module-cgi lighttpd-module-compress lighttpd-module-expire \ ... " This installs a default configuration file for the service which I now want to customize. What is the recommended way to overwrite or customize files in another package? Is the best course to create a recipe bbappend for the lighttpd_1.4.31.bb file that is being used? And can I just include a new file with the same name in my append and will it overwrite the old one, or do I need to create an actual patch file? Or is it better to create a new separate recipe that just ships my version of the configuration file? How are conflicts handled when two recipes attempt to install the same file? Thanks, Brad ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] yocto-1.5 rc1
The first release candidate for yocto-1.5 will be available in a few hours at: http://autobuilder.yoctoproject.org/pub/releases/1.5_M5.rc1 poky 566ca1e4769b4ec7e3f6c6a98bb817db2221cf82 meta-fsl-arm 6b7309e2bc8a9c9c9f02b2bd1ff97f9968fa4720 meta-fsl-ppc 1ddf5e66c635e086864ce15931628ce1a2d6ff0a meta-intel 4f5c753fb2db0cb1f6989ea3be270eebf3ea3572 meta-minnow 7719e114bd0c2118c3d4c2a1a7c06e966103ab09 meta-qt3 b73552fb998fd30a01dbee5a172e432a16078222 -- Elizabeth Flanagan Yocto Project Build and Release ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Meta-security][PATCH v2] snort: add recipe
From: Chunrong Guo *snort - a free lightweight network intrusion detection system for UNIX and Windows Signed-off-by: Chunrong Guo --- recipes-security/snort/files/default | 42 ++ .../snort/files/disable-dap-address-space-id.patch | 52 +++ .../snort/files/disable-inaddr-none.patch | 75 recipes-security/snort/files/logrotate | 12 + recipes-security/snort/files/snort.init| 425 recipes-security/snort/files/volatiles |2 + recipes-security/snort/snort_2.9.4.6.bb| 86 7 files changed, 694 insertions(+), 0 deletions(-) create mode 100644 recipes-security/snort/files/default create mode 100644 recipes-security/snort/files/disable-dap-address-space-id.patch create mode 100644 recipes-security/snort/files/disable-inaddr-none.patch create mode 100644 recipes-security/snort/files/logrotate create mode 100755 recipes-security/snort/files/snort.init create mode 100644 recipes-security/snort/files/volatiles create mode 100644 recipes-security/snort/snort_2.9.4.6.bb diff --git a/recipes-security/snort/files/default b/recipes-security/snort/files/default new file mode 100644 index 000..afd3840 --- /dev/null +++ b/recipes-security/snort/files/default @@ -0,0 +1,42 @@ +# Parameters for the daemon +# Add any additional parameteres here. +PARAMS="-m 027 -D -d " +# +# Snort user +# This user will be used to launch snort. Notice that the +# preinst script of the package might do changes to the user +# (home directory, User Name) when the package is upgraded or +# reinstalled. So, do *not* change this to 'root' or to any other user +# unless you are sure there is no problem with those changes being introduced. +# +SNORTUSER="snort" +# +# Logging directory +# Snort logs will be dropped here and this will be the home +# directory for the SNORTUSER. If you change this value you should +# change the /etc/logrotate.d/snort definition too, otherwise logs +# will not be rotated properly. +# +LOGDIR="/var/log/snort" +# +# Snort group +# This is the group that the snort user will be added to. +# +SNORTGROUP="snort" +# +# Allow Snort's init.d script to work if the configured interfaces +# are not available. Set this to yes if you configure Snort with +# multiple interfaces but some might not be available on boot +# (e.g. wireless interfaces) +# +# Note: In order for this to work the 'iproute' package needs to +# be installed. +ALLOW_UNAVAILABLE="no" + +# Local configs +# +LOCAL_SNORT_STARTUP=boot +LOCAL_SNORT_HOME_NET="192.168.0.0/16" +LOCAL_SNORT_INTERFACE="" +LOCAL_SNORT_STATS_RCPT="root" +LOCAL_SNORT_STATS_THRESHOLD="1" diff --git a/recipes-security/snort/files/disable-dap-address-space-id.patch b/recipes-security/snort/files/disable-dap-address-space-id.patch new file mode 100644 index 000..39e5c9c --- /dev/null +++ b/recipes-security/snort/files/disable-dap-address-space-id.patch @@ -0,0 +1,52 @@ +Upstream-Status:Inappropriate [embedded specific] + +fix the below error: +checking for dap address space id... configure: +configure: error: cannot run test program while cross compiling + + +Signed-off-by: Chunrong Guo + +--- a/configure.in 2013-08-23 00:06:37.239361932 -0500 b/configure.in 2013-08-23 00:07:32.860266534 -0500 +@@ -679,23 +679,23 @@ + + AC_CHECK_FUNCS([daq_hup_apply] [daq_acquire_with_meta]) + +-AC_MSG_CHECKING([for daq address space ID]) +-AC_RUN_IFELSE( +-[AC_LANG_PROGRAM( +-[[ +-#include +-]], +-[[ +- DAQ_PktHdr_t hdr; +- hdr.address_space_id = 0; +-]])], +-[have_daq_address_space_id="yes"], +-[have_daq_address_space_id="no"]) +-AC_MSG_RESULT($have_daq_address_space_id) +-if test "x$have_daq_address_space_id" = "xyes"; then +-AC_DEFINE([HAVE_DAQ_ADDRESS_SPACE_ID],[1], +-[DAQ version supports address space ID in header.]) +-fi ++#AC_MSG_CHECKING([for daq address space ID]) ++#AC_RUN_IFELSE( ++#[AC_LANG_PROGRAM( ++#[[ ++##include ++#]], ++#[[ ++# DAQ_PktHdr_t hdr; ++# hdr.address_space_id = 0; ++#]])], ++have_daq_address_space_id="yes" ++#[have_daq_address_space_id="no"]) ++#AC_MSG_RESULT($have_daq_address_space_id) ++#if test "x$have_daq_address_space_id" = "xyes"; then ++#AC_DEFINE([HAVE_DAQ_ADDRESS_SPACE_ID],[1], ++#[DAQ version supports address space ID in header.]) ++#fi + + # any sparc platform has to have this one defined. + AC_MSG_CHECKING(for sparc) diff --git a/recipes-security/snort/files/disable-inaddr-none.patch b/recipes-security/snort/files/disable-inaddr-none.patch new file mode 100644 index 000..9dafe63 --- /dev/null +++ b/recipes-security/snort/files/disable-inaddr-none.patch @@ -0,0 +1,75 @@ +Upstream-Status: Inappropriate [embedded specific] + +fix the below error: +checking for INADDR_NONE... configure: +configure: error: cannot run test program while cross compiling + +Signed-off-by: Chunrong Guo + + +--- a/configure.in 2013-08-21 03:56:17.197414789 -0500 b/configure.i
[yocto] [Meta-security][PATCH v2] barnyard: add recipe
From: Chunrong Guo
*Barnyard is a output system for Snort
Signed-off-by: Chunrong Guo
---
recipes-security/barnyard/barnyard_0.2.0.bb | 19 +++
1 files changed, 19 insertions(+), 0 deletions(-)
create mode 100644 recipes-security/barnyard/barnyard_0.2.0.bb
diff --git a/recipes-security/barnyard/barnyard_0.2.0.bb
b/recipes-security/barnyard/barnyard_0.2.0.bb
new file mode 100644
index 000..c5e0e78
--- /dev/null
+++ b/recipes-security/barnyard/barnyard_0.2.0.bb
@@ -0,0 +1,19 @@
+DESCRIPTION = "Barnyard is a output system for Snort."
+HOMEPAGE = "http://www.snort.org/";
+LICENSE = "QPL"
+LIC_FILES_CHKSUM = "file://LICENSE.QPL;md5=1b8ff8c0012b5a2d647357699bf44b41"
+
+DEPENDS = "libpcap"
+
+SRC_URI = " ${GENTOO_MIRROR}/${BP}.tar.gz;name=tarball \
+ "
+SRC_URI[tarball.md5sum] = "be3283028cf414b52b220308ceb411e9"
+SRC_URI[tarball.sha256sum] =
"09e0f8e095e79cfe70ea069d13e7d02521a504a1f400a45556a634dccfd31a3a"
+
+inherit autotools pkgconfig
+
+do_configure_prepend () {
+ #fix hardcoded include path
+ sed -i -e 's:extra_incl=-I/usr/include/pcap::g' ${S}/configure.in
+}
+
--
1.7.5.4
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Support for monit utility
Hi, I am trying to find /monit/ utility in Yocto BSP. I tried with /bitbake monit /command but it failed. Does yocto supports /monit/ or similar utility to monitor threads and processes on system? Regards, Rohit - Notice: This message has been scanned by Trend Micro Mail Security scanner and is believed to be clean - ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
