[yocto] [PATCH] distro/poky: Add Debian 7.5 and 7.6 version as validated

[Otavio Salvador]

Signed-off-by: Otavio Salvador 
---
 meta-yocto/conf/distro/poky.conf | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta-yocto/conf/distro/poky.conf b/meta-yocto/conf/distro/poky.conf
index ec251f9..34ce8ec 100644
--- a/meta-yocto/conf/distro/poky.conf
+++ b/meta-yocto/conf/distro/poky.conf
@@ -88,6 +88,8 @@ SANITY_TESTED_DISTROS ?= " \
 Debian-7.2 \n \
 Debian-7.3 \n \
 Debian-7.4 \n \
+Debian-7.5 \n \
+Debian-7.6 \n \
 SUSE-LINUX-12.2 \n \
 openSUSE-project-12.3 \n \
 openSUSE-project-13.1 \n \
-- 
2.1.0.rc1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] PR Server import/export questions

[Bryan Evenson]

All,

I'm making the transition from the dylan to daisy branch, and in my first 
attempt I got a bunch of QA warnings about PRINC being deprecated and that I 
should start using a PR service.  I took a look through the manual and the PR 
server wiki and I still have some concerns about the PR server.  I may be able 
to figure out some of these things with trial and error, but given what could 
go wrong if I mess this up I thought it'd be prudent to ask a few questions 
first.

My big concern for using a PR server for consistently generating a package feed 
for firmware upgrades.  Our big concern is if something were to happen to the 
PR server and we would lose the last PR state.  I believe this is where the 
bitbake-prserv-tool import and export come in as described on the PR Service 
wiki.  However, the details on the import and export are a little light.

Could someone describe a basic workflow using the PR server and backing up the 
PR data?  I'm assuming that the exported PR file can be stored in a local Git 
repository, but having never seen the exported data I didn't know if there were 
any issues in backing up the exported PRs in this manner.  If this would work, 
then I'm assuming a workflow could be:
1. Pull latest from local Git server and import PRs to the PR server.
2. Do work for next system version.
3. Push updates back to local Git server.
4. Pull latest Git server and test for candidate release.
5. Perform minor bug fixes and push back to local Git server.
6. Repeat steps 4 and 5 until there are no more bug fixes pushed back to the 
local Git server.
7. Export PRs from the PR server, push PRs to local Git server and tag the 
release.

Anyone see any issues with this workflow?  If so, how have you been handling 
working with the PR server at your organization?  Has anyone else had any other 
issues using a PR server?

Thanks,
Bryan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] base-files: /etc/profile profile.d execution order

[Jate Sujjavanich]

I moved the profile.d loop in my build the end of the etc profile script.

Should this change be made in base-files?


- Jate S.

On Thursday, August 7, 2014, Jate S  wrote:

> I am trying to use a file in profile.d to override the default umask
> in /etc/profile. However, the umask line in /etc/profile comes after
> the code which sources profile.d files.
>
> I suggest moving the umask line and the exports to before the profile.d
> code.
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [musl] Re: [OE-core] Announcing meta-musl OE/Yocto layer supporting musl C library

[Szabolcs Nagy]

* Khem Raj  [2014-08-18 12:04:54 -0700]:
> On Mon, Aug 18, 2014 at 11:50 AM, Paul Barker  wrote:
> >> >
> > I've put the failing "log.do_compile" files into one directory which is 
> > 1.3MB
> > uncompressed or just 41kB compressed. I've posted them to:
> >   http://www.paulbarker.me.uk/musl-error-logs_2014-08-18/
> >   
> > http://www.paulbarker.me.uk/musl-error-logs_2014-08-18/musl-error-logs_2014-08-18.tar.xz
> >

i looked at the logs

i think most of the issues already have fixes in alpinelinux or
sabotage, they should be pushed upstream if they are not there yet

common errors and recommended fixes:

findutils
gzip
old gnulib with broken freadahead, newer gnulib works with musl

libtirpc
pax
sys/cdefs.h, application should be fixed not to use it

logrotate
sys/queue.h, missing from musl, ship queue.h with app source

e2fsprogs
ethtool:
use of __uint64_t, __uint32_t (non-conforming, use standard types)
libnfsidmap
use of u_int32_t (without including sys/types.h)

procps
psmisc
undefined PATH_MAX (missing limits.h include)

mc:
undefined CTRL(x) (missing sys/ttydefaults.h include)
glibc includes sys/ttydefaults.h into termios.h, musl doesnt

cronie
undefined MAXNAMLEN, musl has it in sys/param.h

at
undefied __isleap
glibc time.h has # define __isleap(year) \
((year) % 4 == 0 && ((year) % 100 != 0 || (year) % 400 == 0))

elfutils
error.h, musl does not have this

sysklogd
iptables
include incompatible linux headers (+ various other issues)
probably harder to fix

sudo:
the build command helpfully redirected the compiler output to /dev/null
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] eglibc-dbg files ownership

[Luca Barbieri]

Hi, I need an help to understand a problem.
Using dora branch I've strange file ownership on some *-dbg package files,
for example in eglibc-dbg.

If I'm not wrong, it seems to me that source files are copied by
copydebugsources function in package.bbclass

This method uses "cpio -pd0mlL --no-preserve-owner" so I suppose copied
files must be owned by root.. but instead they have strange permissions

May somebody explain me if I miss something and why the -dbg package has
this incorrect ownership?

Thanks

-
Luca Barbieri
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-oracle-java][PATCH 1/2] oracle-java: update fetch method

[Maxin B. John]

Hi,

Gentle ping .. 
Could anyone review these, please ?

On Thu, Aug 14, 2014 at 05:47:31PM +0200, Maxin B. John wrote:
> Use custom FETCHCMD_wget to avoid manual downloading of Oracle Java packages.
> 
> Signed-off-by: Maxin B. John 
> ---
>  recipes-devtools/oracle-java/oracle-jse.inc | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/recipes-devtools/oracle-java/oracle-jse.inc 
> b/recipes-devtools/oracle-java/oracle-jse.inc
> index 98069f4..3a4e20d 100644
> --- a/recipes-devtools/oracle-java/oracle-jse.inc
> +++ b/recipes-devtools/oracle-java/oracle-jse.inc
> @@ -6,6 +6,8 @@ LIC_FILES_CHKSUM = "\
>   
> file://${WORKDIR}/${JDK_JRE}${PV}_${PV_UPDATE}/THIRDPARTYLICENSEREADME.txt;md5=c339b34e3da6673d2c5950d0f8808f8c
>  \
>   "
>  
> +FETCHCMD_wget_append = " --header=Cookie:oraclelicense=a "
> +
>  # get the java update version in the resulting package
>  PR =. "u${PV_UPDATE}"
>  S = "${WORKDIR}"
> -- 
> 1.9.1
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] how to use the new features of the toaster

[Alex Damian]

Hi,

Thanks for keeping an eye on Toaster !

The builder part is still a work in progress. The building-related features
are being outlined here:

https://wiki.yoctoproject.org/wiki/Toaster_1.7_design#Feature_list

While

A mockup of the functionality is here:

http://www.yoctoproject.org/toaster/project-no-targets.html


We currently work on implementing the project settings design part, and you
can follow progress on the bugzilla items here:

https://bugzilla.yoctoproject.org/buglist.cgi?list_id=22&resolution=---&classification=Build%20System%20%26%20Metadata&query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=IN%20PROGRESS%20DESIGN&bug_status=IN%20PROGRESS%20DESIGN%20COMPLETE&bug_status=IN%20PROGRESS%20IMPLEMENTATION&bug_status=IN%20PROGRESS%20REVIEW&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=1.7&target_milestone=1.7%20M1&target_milestone=1.7%20M2&target_milestone=1.7%20M3&target_milestone=1.7%20M4&product=Toaster


We also meet every week on a phone conference, let me know if you would
like to attend.

Cheers,
Alex



On Tue, Aug 19, 2014 at 3:25 AM, leimao...@cn.fujitsu.com <
leimao...@cn.fujitsu.com> wrote:

> Hi,
>
>  Because I noticed that in poky(master), the toaster has the ability to
> trigger a build command, and have
>  the build executed.
>  --
>  commit 6e71c276b582135228419d95174b7e7784d496b2
>  Author: Alexandru DAMIAN 
>  Date:   Mon Jun 30 18:33:04 2014 +0100
>
> bitbake: toaster: add project main edit page
>
> This is the first commit on the project main edit page.
>
> At this point we have:
> * the default settings for a newly created project
> * the ability to add targets
> * the ability to trigger a build command, and have
> the build executed
> ..
>  ---
>
>  So, I tried to use the new features of the toaster. But I don't know how .
>
>  Is there anybody tell me where can I find the documentation how to use
> the new features?
>
>  Best Regards,
>  Lei Maohui
> --
> ___
> 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] [meta-oracle-java][PATCH 1/2] oracle-java: update fetch method

[Vladimir Redzhepov]

Hi Maxin,

Looks good. 

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Maxin B. John
Sent: Tuesday, August 19, 2014 6:30 PM
To: yocto@yoctoproject.org
Subject: Re: [yocto] [meta-oracle-java][PATCH 1/2] oracle-java: update fetch 
method

Hi,

Gentle ping .. 
Could anyone review these, please ?

On Thu, Aug 14, 2014 at 05:47:31PM +0200, Maxin B. John wrote:
> Use custom FETCHCMD_wget to avoid manual downloading of Oracle Java packages.
> 
> Signed-off-by: Maxin B. John 
> ---
>  recipes-devtools/oracle-java/oracle-jse.inc | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/recipes-devtools/oracle-java/oracle-jse.inc 
> b/recipes-devtools/oracle-java/oracle-jse.inc
> index 98069f4..3a4e20d 100644
> --- a/recipes-devtools/oracle-java/oracle-jse.inc
> +++ b/recipes-devtools/oracle-java/oracle-jse.inc
> @@ -6,6 +6,8 @@ LIC_FILES_CHKSUM = "\
>   
> file://${WORKDIR}/${JDK_JRE}${PV}_${PV_UPDATE}/THIRDPARTYLICENSEREADME.txt;md5=c339b34e3da6673d2c5950d0f8808f8c
>  \
>   "
>  
> +FETCHCMD_wget_append = " --header=Cookie:oraclelicense=a "
> +
>  # get the java update version in the resulting package
>  PR =. "u${PV_UPDATE}"
>  S = "${WORKDIR}"
> -- 
> 1.9.1
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Coverity

[Seth Bollinger]

Hello All,

We have a few code bases that we need to run Coverity on.  Does someone
have an example of how that would hook into a recipe?

Thanks,

Seth
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Coverity

[Khem Raj]

On Tue, Aug 19, 2014 at 10:20 AM, Seth Bollinger  wrote:
> Hello All,
>
> We have a few code bases that we need to run Coverity on.  Does someone have
> an example of how that would hook into a recipe?
>

I dont think anyone have submitted patches for that yet. but you would
actually write a task in a bbclass and then offer to  inherit it
globally or per recipe

in that task you will implement the needed bits for running scans and
all dependencies etc needed for scan.

_
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH] samhain: arm build failure

[Armin Kuster]

| x_sh_error.c: In function 'sh_error_string':
| x_sh_error.c:1580:31: error: incompatible type for argument 1 of 'memmove'
|  #define VA_COPY(ap1, ap2) memmove ((ap1), (ap2), sizeof (va_list))
|^
| x_sh_error.c:1720:14: note: in expansion of macro 'VA_COPY'
|/*@i@*/VA_COPY(vl2, vl);
|   ^

this patch fixes the arm build failure.

Signed-off-by: Armin Kuster 
---
 recipes-security/samhain/samhain.inc | 4 
 1 file changed, 4 insertions(+)

diff --git a/recipes-security/samhain/samhain.inc 
b/recipes-security/samhain/samhain.inc
index d6f9f82..772aa7b 100644
--- a/recipes-security/samhain/samhain.inc
+++ b/recipes-security/samhain/samhain.inc
@@ -37,6 +37,10 @@ do_unpack_extra () {
 }
 addtask unpack_extra after do_unpack before do_patch
 
+do_configure_prepend_arm() {
+export sh_cv___va_copy=yes
+}
+
 # If we use oe_runconf in do_configure() it will by default
 # use the prefix --oldincludedir=/usr/include which is not
 # recognized by Samhain's configure script and would invariably
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Kernel driver for Turbosight TBS6285 DVB card

[Chris Tapp]

I need to include the kernel driver for the Turbosight TBS6285 DVB card in an 
image.

The official bundle at 
http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v140707.zip 
includes the drivers and a load of other "stuff" (e.g. a full V4L build).

LinuxTV.org have the drivers extracted into a .tar.bz2 at (e.g.) 
http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2, so I plan to 
use this as the download source.

So far I have a recipe which downloads from this URL and extracts the files 
into the work area and ${WORKAREA}/drivers/media includes a Makefile and 
Kconfig.

I've looked at the Yocto documentation, but this doesn't seem to be a good 
match for the "Out of tree" kernel module case.

How should I proceed from here? Is there another driver I can use as a starting 
point?

--

Chris Tapp
opensou...@keylevel.com
www.keylevel.com




-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Community Demo Area at ELCE

[Osier-mixon, Jeffrey]

At the Embedded Linux Conference in San Jose, CA USA this past spring, we
had six great demos in the Yocto Project booth. However, only two of those
were demos that we arrived with. Four were from community members who
spontaneously showed up, including a homebuilt audio player (hi nerdboy)
and we thank them very much for their support and willingness to share.

As a response to that, the Yocto Project would like to invite Embedded
Linux Conference Europe* participants to bring your projects to the Yocto
Project booth if you'd like to show off your work. We will have a screen,
keyboard, mouse, and power available. Small embedded projects are best, but
if you have a scale robotic dinosaur or a Yocto-powered Lamborghini, we
won't turn you away. (Probably.)

Please RSVP to me directly and let me know when to expect you.

If there is enough interest, we can also set up a table at lunchtime at the
Yocto Project Developer Day** following ELCE.

* http://events.linuxfoundation.org/events/embedded-linux-conference-europe
**
https://www.yoctoproject.org/tools-resources/events/yocto-project-developer-day-elce-2014
-- 
Jeff Osier-Mixon @Intel
Yocto Project Community Manager http://yoctoproject.org
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH] qemu: enable aarch64 support in yocto

[Kang Kai]

On 2014?08?15? 11:21, Kai Kang wrote:

qemu 2.1.0 support aarch64 targets, so add aarch64 to QEMU_TARGETS to
enable qemu aarch64 support. Var QEMU_TARGETS in poky.conf overrides the
var in qemu recipe, so add in poky.conf too.

Signed-off-by: Kai Kang 
---
  meta-yocto/conf/distro/poky.conf | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-yocto/conf/distro/poky.conf b/meta-yocto/conf/distro/poky.conf
index ec251f9..9a67b50 100644
--- a/meta-yocto/conf/distro/poky.conf
+++ b/meta-yocto/conf/distro/poky.conf
@@ -44,7 +44,7 @@ DISTRO_EXTRA_RDEPENDS_append_qemux86-64 = " ${POKYQEMUDEPS}"
  
  TCLIBCAPPEND = ""
  
-QEMU_TARGETS ?= "arm i386 mips mipsel ppc x86_64"

+QEMU_TARGETS ?= "arm aarch64 i386 mips mipsel ppc x86_64"
  # Other QEMU_TARGETS "mips64 mips64el sh4"
  
  PREMIRRORS ??= "\


Hi,

Any comment for this patch? Thanks.

--
Regards,
Neil | Kai Kang

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Kernel driver for Turbosight TBS6285 DVB card

[Bruce Ashfield]

On 2014-08-19, 5:26 PM, Chris Tapp wrote:

I need to include the kernel driver for the Turbosight TBS6285 DVB card in an 
image.

The official bundle at 
http://www.tbsdtv.com/download/document/common/tbs-linux-drivers_v140707.zip includes the 
drivers and a load of other "stuff" (e.g. a full V4L build).

LinuxTV.org have the drivers extracted into a .tar.bz2 at (e.g.) 
http://linuxtv.org/downloads/drivers/linux-media-LATEST.tar.bz2, so I plan to 
use this as the download source.

So far I have a recipe which downloads from this URL and extracts the files 
into the work area and ${WORKAREA}/drivers/media includes a Makefile and 
Kconfig.

I've looked at the Yocto documentation, but this doesn't seem to be a good match for the 
"Out of tree" kernel module case.


Hmm. At a glance, I'd say that it does sound like a typical out of
tree module build.

Did you try adopting the meta-skeleton hello-mod recipe and point it
at that source directory ?

Bruce



How should I proceed from here? Is there another driver I can use as a starting 
point?

--

Chris Tapp
opensou...@keylevel.com
www.keylevel.com






--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] how to use the new features of the toaster

[leimao...@cn.fujitsu.com]

Hi Alex

   Thanks for your reply

   I’m glad to join the phone conference if I can, although my English is not 
very good. ☺
   Could you tell me the date of the conference and how to join.


Thanks,

Lei Maohui



From: Alex Damian [mailto:alex.r.dam...@gmail.com]
Sent: Wednesday, August 20, 2014 12:08 AM
To: Lei, Maihui
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] how to use the new features of the toaster

Hi,
Thanks for keeping an eye on Toaster !
The builder part is still a work in progress. The building-related features are 
being outlined here:

https://wiki.yoctoproject.org/wiki/Toaster_1.7_design#Feature_list
While

A mockup of the functionality is here:

http://www.yoctoproject.org/toaster/project-no-targets.html

We currently work on implementing the project settings design part, and you can 
follow progress on the bugzilla items here:

https://bugzilla.yoctoproject.org/buglist.cgi?list_id=22&resolution=---&classification=Build%20System%20%26%20Metadata&query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=IN%20PROGRESS%20DESIGN&bug_status=IN%20PROGRESS%20DESIGN%20COMPLETE&bug_status=IN%20PROGRESS%20IMPLEMENTATION&bug_status=IN%20PROGRESS%20REVIEW&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=1.7&target_milestone=1.7%20M1&target_milestone=1.7%20M2&target_milestone=1.7%20M3&target_milestone=1.7%20M4&product=Toaster


We also meet every week on a phone conference, let me know if you would like to 
attend.
Cheers,
Alex


On Tue, Aug 19, 2014 at 3:25 AM, 
leimao...@cn.fujitsu.com 
mailto:leimao...@cn.fujitsu.com>> wrote:
Hi,

 Because I noticed that in poky(master), the toaster has the ability to trigger 
a build command, and have
 the build executed.
 --
 commit 6e71c276b582135228419d95174b7e7784d496b2
 Author: Alexandru DAMIAN 
mailto:alexandru.dam...@intel.com>>
 Date:   Mon Jun 30 18:33:04 2014 +0100

bitbake: toaster: add project main edit page

This is the first commit on the project main edit page.

At this point we have:
* the default settings for a newly created project
* the ability to add targets
* the ability to trigger a build command, and have
the build executed
..
 ---

 So, I tried to use the new features of the toaster. But I don't know how .

 Is there anybody tell me where can I find the documentation how to use the new 
features?

 Best Regards,
 Lei Maohui
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH] nmap: build QA Warnings

[Armin Kuster]

WARNING: QA Issue: nmap rdepends on libcrypto, but it isn't a build dependency? 
[build-deps]
WARNING: QA Issue: nmap rdepends on libssl, but it isn't a build dependency? 
[build-deps]

This fixes the above QA warnings.

Signed-off-by: Armin Kuster 
---
 recipes-security/nmap/nmap_6.46.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-security/nmap/nmap_6.46.bb 
b/recipes-security/nmap/nmap_6.46.bb
index 42db71f..52acf96 100644
--- a/recipes-security/nmap/nmap_6.46.bb
+++ b/recipes-security/nmap/nmap_6.46.bb
@@ -14,7 +14,7 @@ inherit autotools-brokensep
 
 DEPENDS = "libpcap"
 
-EXTRA_OECONF = "--without-liblua --without-zenmap --without-subversion 
--with-pcap=linux"
+EXTRA_OECONF = "--without-liblua --without-zenmap --without-subversion 
--with-pcap=linux --without-openssl"
 
 do_configure() {
 autoconf
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH] nmap: use pkgconfig and reorg

[Armin Kuster]

Added pkgconfig support
Since most binaries provided by nmap can be excluded via configure
  manage via pkgconfig
Aligned python packages with binaries so nmap-python is no longer needed

Signed-off-by: Armin Kuster 
---
 recipes-security/nmap/nmap_6.46.bb | 34 --
 1 file changed, 24 insertions(+), 10 deletions(-)

diff --git a/recipes-security/nmap/nmap_6.46.bb 
b/recipes-security/nmap/nmap_6.46.bb
index 52acf96..6fe3c6b 100644
--- a/recipes-security/nmap/nmap_6.46.bb
+++ b/recipes-security/nmap/nmap_6.46.bb
@@ -3,34 +3,48 @@ DESCRIPTION = "Nmap ("Network Mapper") is a free and open 
source (license) utili
 SECTION = "security"
 LICENSE = "GPL-2.0"
 LIC_FILES_CHKSUM = 
"file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6"
-FILES_${PN} += "${target_datadir}/ncat"
 
 SRC_URI = "http://nmap.org/dist/${BPN}-${PV}.tar.bz2";
 
 SRC_URI[md5sum] = "5a36ad3a63d5b7ea5514f745a397436a"
 SRC_URI[sha256sum] = 
"3f89d9053c69507fe9533c40188a6561d49607a37b1db6380aed9039d4883137"
 
-inherit autotools-brokensep
+inherit autotools-brokensep pkgconfig
 
-DEPENDS = "libpcap"
+PACKAGECONFIG ??= "ncat nping ndiff pcap"
 
-EXTRA_OECONF = "--without-liblua --without-zenmap --without-subversion 
--with-pcap=linux --without-openssl"
+PACKAGECONFIG[pcap] = "--with-pcap=linux, --without-pcap, libpcap"
+PACKAGECONFIG[ssl] = "--with-openssl=${STAGING_LIBDIR}/.., --without-openssl, 
openssl, openssl"
+
+#disable/enable packages
+PACKAGECONFIG[nping] = ",--without-nping,"
+PACKAGECONFIG[ncat] = ",--without-ncat,"
+PACKAGECONFIG[ndiff] = ",--without-ndiff,"
+
+#use nmap's Included or system's libs
+PACKAGECONFIG[lua] = "--with-liblua=${STAGING_LIBDIR}/.., 
--with-liblua=included, lua"
+PACKAGECONFIG[pcre] = "--with-libpcre=${STAGING_LIBDIR}/.., 
--with-libpcre=included, libpre"
+
+EXTRA_OECONF = "--without-zenmap"
 
 do_configure() {
 autoconf
 oe_runconf
 }
 
+PACKAGES = "${PN} ${PN}-dbg ${PN}-doc"
+
+FILES_${PN} = "${bindir}/nmap ${datadir}/nmap/*"
+
+# append packages if enabled
+FILES_${PN} += "${@bb.utils.contains("PACKAGECONFIG", "ncat", "${bindir}/ncat 
${target_datadir}/ncat", "", d)}"
+FILES_${PN} += "${@bb.utils.contains("PACKAGECONFIG", "nping", 
"${bindir}/nping", "", d)}"
+FILES_${PN} += "${@bb.utils.contains("PACKAGECONFIG", "ndiff", 
"${bindir}/ndiff ${libdir}/python${PYTHON_BASEVERSION}/site-packages/ndiff*", 
"", d)}"
+
 # should add a conditional for "--without-zenmap" test. 
 # zenmap builds if the below are uncommented. Not tested
 #PACKAGES =+ "${PN}-zenmap"
 #FILES_${PN}-zenmap = "/usr/share/zenmap/*"
 
-#  should add a conditional based for "--without-ndiff"
-PACKAGES =+ "${PN}-python"
-DESCRIPTION_${PN}-python = \
-"The ${PN}-python package includes the ndiff utility. \
-Ndiff is a tool to aid in the comparison of Nmap scans."
-FILES_${PN}-python = "${libdir}/python${PYTHON_BASEVERSION}/site-packages/*"
 
 
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH] v2] nmap: use pkgconfig and reorg

[Armin Kuster]

Added pkgconfig support
Since most binaries provided by nmap can be excluded via configure
  manage via pkgconfig
Aligned python packages with binaries so nmap-python is no longer needed

V2: Missed some options in EXTRA_OECONF changes

Signed-off-by: Armin Kuster 
---
 recipes-security/nmap/nmap_6.46.bb | 34 --
 1 file changed, 24 insertions(+), 10 deletions(-)

diff --git a/recipes-security/nmap/nmap_6.46.bb 
b/recipes-security/nmap/nmap_6.46.bb
index 52acf96..6fe3c6b 100644
--- a/recipes-security/nmap/nmap_6.46.bb
+++ b/recipes-security/nmap/nmap_6.46.bb
@@ -3,34 +3,48 @@ DESCRIPTION = "Nmap ("Network Mapper") is a free and open 
source (license) utili
 SECTION = "security"
 LICENSE = "GPL-2.0"
 LIC_FILES_CHKSUM = 
"file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6"
-FILES_${PN} += "${target_datadir}/ncat"
 
 SRC_URI = "http://nmap.org/dist/${BPN}-${PV}.tar.bz2";
 
 SRC_URI[md5sum] = "5a36ad3a63d5b7ea5514f745a397436a"
 SRC_URI[sha256sum] = 
"3f89d9053c69507fe9533c40188a6561d49607a37b1db6380aed9039d4883137"
 
-inherit autotools-brokensep
+inherit autotools-brokensep pkgconfig
 
-DEPENDS = "libpcap"
+PACKAGECONFIG ??= "ncat nping ndiff pcap"
 
-EXTRA_OECONF = "--without-liblua --without-zenmap --without-subversion 
--with-pcap=linux --without-openssl"
+PACKAGECONFIG[pcap] = "--with-pcap=linux, --without-pcap, libpcap"
+PACKAGECONFIG[ssl] = "--with-openssl=${STAGING_LIBDIR}/.., --without-openssl, 
openssl, openssl"
+
+#disable/enable packages
+PACKAGECONFIG[nping] = ",--without-nping,"
+PACKAGECONFIG[ncat] = ",--without-ncat,"
+PACKAGECONFIG[ndiff] = ",--without-ndiff,"
+
+#use nmap's Included or system's libs
+PACKAGECONFIG[lua] = "--with-liblua=${STAGING_LIBDIR}/.., 
--with-liblua=included, lua"
+PACKAGECONFIG[pcre] = "--with-libpcre=${STAGING_LIBDIR}/.., 
--with-libpcre=included, libpre"
+
+EXTRA_OECONF = "--without-zenmap"
 
 do_configure() {
 autoconf
 oe_runconf
 }
 
+PACKAGES = "${PN} ${PN}-dbg ${PN}-doc"
+
+FILES_${PN} = "${bindir}/nmap ${datadir}/nmap/*"
+
+# append packages if enabled
+FILES_${PN} += "${@bb.utils.contains("PACKAGECONFIG", "ncat", "${bindir}/ncat 
${target_datadir}/ncat", "", d)}"
+FILES_${PN} += "${@bb.utils.contains("PACKAGECONFIG", "nping", 
"${bindir}/nping", "", d)}"
+FILES_${PN} += "${@bb.utils.contains("PACKAGECONFIG", "ndiff", 
"${bindir}/ndiff ${libdir}/python${PYTHON_BASEVERSION}/site-packages/ndiff*", 
"", d)}"
+
 # should add a conditional for "--without-zenmap" test. 
 # zenmap builds if the below are uncommented. Not tested
 #PACKAGES =+ "${PN}-zenmap"
 #FILES_${PN}-zenmap = "/usr/share/zenmap/*"
 
-#  should add a conditional based for "--without-ndiff"
-PACKAGES =+ "${PN}-python"
-DESCRIPTION_${PN}-python = \
-"The ${PN}-python package includes the ndiff utility. \
-Ndiff is a tool to aid in the comparison of Nmap scans."
-FILES_${PN}-python = "${libdir}/python${PYTHON_BASEVERSION}/site-packages/*"
 
 
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH] nmap: Add gui support

[Armin Kuster]

Add zenmap to work with gtk+/x11

Signed-off-by: Armin Kuster 
---
 recipes-security/nmap/nmap_6.46.bb | 18 ++
 1 file changed, 10 insertions(+), 8 deletions(-)

diff --git a/recipes-security/nmap/nmap_6.46.bb 
b/recipes-security/nmap/nmap_6.46.bb
index 6fe3c6b..573187d 100644
--- a/recipes-security/nmap/nmap_6.46.bb
+++ b/recipes-security/nmap/nmap_6.46.bb
@@ -1,5 +1,5 @@
 SUMMARY = "network auditing tool"
-DESCRIPTION = "Nmap ("Network Mapper") is a free and open source (license) 
utility for network discovery and security auditing."
+DESCRIPTION = "Nmap ("Network Mapper") is a free and open source (license) 
utility for network discovery and security auditing.\nGui support via appending 
to IMAGE_FEATURES x11-base in local.conf"
 SECTION = "security"
 LICENSE = "GPL-2.0"
 LIC_FILES_CHKSUM = 
"file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6"
@@ -9,9 +9,10 @@ SRC_URI = "http://nmap.org/dist/${BPN}-${PV}.tar.bz2";
 SRC_URI[md5sum] = "5a36ad3a63d5b7ea5514f745a397436a"
 SRC_URI[sha256sum] = 
"3f89d9053c69507fe9533c40188a6561d49607a37b1db6380aed9039d4883137"
 
-inherit autotools-brokensep pkgconfig
+inherit autotools-brokensep pkgconfig distro_features_check
 
 PACKAGECONFIG ??= "ncat nping ndiff pcap"
+PACKAGECONFIG += " ${@bb.utils.contains("IMAGE_FEATURES", "x11-base", 
"zenmap", "", d)}"
 
 PACKAGECONFIG[pcap] = "--with-pcap=linux, --without-pcap, libpcap"
 PACKAGECONFIG[ssl] = "--with-openssl=${STAGING_LIBDIR}/.., --without-openssl, 
openssl, openssl"
@@ -25,7 +26,10 @@ PACKAGECONFIG[ndiff] = ",--without-ndiff,"
 PACKAGECONFIG[lua] = "--with-liblua=${STAGING_LIBDIR}/.., 
--with-liblua=included, lua"
 PACKAGECONFIG[pcre] = "--with-libpcre=${STAGING_LIBDIR}/.., 
--with-libpcre=included, libpre"
 
-EXTRA_OECONF = "--without-zenmap"
+#Add gui
+PACKAGECONFIG[zenmap] = "--with-zenmap, --without-zenmap, gtk+ python-core 
python-codecs python-io python-logging python-unittest python-xml 
python-netclient python-doctest python-subprocess python-pygtk, python-core 
python-codecs python-io python-logging python-netclient python-xml 
python-unittest python-doctest python-subprocess  python-pygtk gtk+"
+
+EXTRA_OECONF = "--with-libdnet=included --with-liblinear=included 
--without-subversion"
 
 do_configure() {
 autoconf
@@ -41,10 +45,8 @@ FILES_${PN} += "${@bb.utils.contains("PACKAGECONFIG", 
"ncat", "${bindir}/ncat ${
 FILES_${PN} += "${@bb.utils.contains("PACKAGECONFIG", "nping", 
"${bindir}/nping", "", d)}"
 FILES_${PN} += "${@bb.utils.contains("PACKAGECONFIG", "ndiff", 
"${bindir}/ndiff ${libdir}/python${PYTHON_BASEVERSION}/site-packages/ndiff*", 
"", d)}"
 
-# should add a conditional for "--without-zenmap" test. 
-# zenmap builds if the below are uncommented. Not tested
-#PACKAGES =+ "${PN}-zenmap"
-#FILES_${PN}-zenmap = "/usr/share/zenmap/*"
-
+PACKAGES += "${@bb.utils.contains("PACKAGECONFIG", "zenmap", "${PN}-zenmap", 
"", d)}"
 
+FILES_${PN}-zenmap = "${@bb.utils.contains("PACKAGECONFIG", "zenmap", 
"${bindir}/*zenmap ${bindir}/xnmap ${datadir}/applications/*  ${bindir}/nmapfe 
${datadir}/zenmap/* 
${libdir}/python${PYTHON_BASEVERSION}/site-packages/radialnet/* 
${libdir}/python${PYTHON_BASEVERSION}/site-packages/zenmap*", "", d)}"
 
+RDEPENDS_${PN}-zenmap = "nmap"
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto