[yocto] [meta-security][PATCH] clamav: runtime fix local routing

[Armin Kuster]

This addes the localhost to resolve.conf to fix:

ERROR: Can't get information about database.clamav.net: Temporary failure in 
name resolution
ERROR: Can't download main.cvd from database.clamav.net
Giving up on database.clamav.net...

Signed-off-by: Armin Kuster 
---
 lib/oeqa/runtime/cases/clamav.py | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/lib/oeqa/runtime/cases/clamav.py b/lib/oeqa/runtime/cases/clamav.py
index 647861c..d0bc645 100644
--- a/lib/oeqa/runtime/cases/clamav.py
+++ b/lib/oeqa/runtime/cases/clamav.py
@@ -19,6 +19,8 @@ class ClamavTest(OERuntimeTestCase):
 f.write(os.linesep)
 f.write("nameserver 8.8.4.4")
 f.write(os.linesep)
+f.write("nameserver 127.0.0.1")
+f.write(os.linesep)
 
 @classmethod
 def tearDownClass(cls):
-- 
2.17.1

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

Re: [yocto] FileExistsError: [Errorno 17] File Exists

[Burton, Ross]

On Mon, 8 Apr 2019 at 07:17, Pandey, Kamal  wrote:
> Hi I was trying to compile Weston-6.0 using yocto recipe. For this I 
> backported some of the packages from master branch of poky to my own layer. 
> During this process, there was one package xorgproto which was used in master 
> branch of poky but in rocko branch this package is not there. However a 
> similar package is there called xproto. Now there is a conflict between these 
> two packages for installing the same headers. I appended xorgproto recipe and 
> removed the installation of similar header files. But after this I am getting 
> this error. However If I continue to compile these errors are ignored.

xproto != xorgproto.

https://www.phoronix.com/scan.php?page=news_item&px=Xorgproto-Debut-Release

All of the xorg-proto/*proto.bb recipes were replaced by xorgproto.
As part of the backporting you can most likely just replace xorgproto
with the name of the relevant proto recipe.

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

Re: [yocto] shared cmake modules

[Gabriele Zampieri]

bump

Il giorno mer 3 apr 2019 alle ore 12:07 Gabriele Zampieri <
gabbla.mal...@gmail.com> ha scritto:

> Hi all,
>
> I'm setting up a layer that will compile our applications and libraries.
> All the applications are based on cmake and they share modules. Before
> using yocto I kept the modules in /cmake (under version control)
> alongside applications and libraries. With yocto I wrote a recipe that
> checkout the module repo and install them in
> "${STAGING_DATADIR}/cmake/Modules/". I took this path from
> "meta/classes/cmake.bbclass". If i build the module target, I get the files
> installed in the target recipe datadir. If I want to build a library (that
> depends also on my modules recipe) the task do_configure fails because
> cmake cannot find none of my include. Digging around I found that the
> toolchain.cmake file points to a module location that doesn't exist in the
> library workdir, but in module recipe (${STAGING_DATADIR}/cmake/Modules/).
>
> The module recipe looks like as follow:
>
> MODULES_DEST_PATH = "${STAGING_DATADIR}/cmake/Modules"
> FILES_${PN}-dev = "${MODULES_DEST_PATH}/*"
>
> do_install() {
> DEST_DIR=${MODULES_DEST_PATH}
>
> # Create the destination folder
> install -d $DEST_DIR
> install -m 0444 ${S}/my/module.cmake $DEST_DIR
> ..
> }
>
> So my question is: where should I install the shared modules
> (MODULE_DEST_PATH int the above snippet)? and how to update the
> CMAKE_MODULE_PATH properly to append that location?
>
> Thanks,
> Gabriele
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Development environment for Grub bootloader and Linux

[Srinivasa RaoW]

Dear All,
I have a requirement of modifying Grub bootloader for x86 architecture but Just 
read the Wiki Page of Yocto and it states as below"
"The Yocto Project is an open-source project that 
delivers a set of tools that create operating system images for embedded Linux 
systems"
Towards this I have below questions:

  1.  Does Yocto project support only Linux systems?
  2.  Do we have repositories/build tool chain for Grub bootloader?
  3.  Which is the bootloader that Yocto project recommends for x86 
architecture?
I am trying to setup a development environment under Ubunt Host for x86 target 
architecture.  Goal is to build Grub bootloader, Ubuntu linux and root file 
system all together under one umbrella.
Please let me know if Yocto has anything for this.
Appreciate any input on this.
Regards
Srinivasa


L&T Technology Services Ltd

www.LTTS.com

This Email may contain confidential or privileged information for the intended 
recipient (s). If you are not the intended recipient, please do not use or 
disseminate the information, notify the sender and delete it from your system.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Installation help

[Karshi Hasanov]

Hi all,

I have followed the

https://www.yoctoproject.org/docs/2.6.1/brief-yoctoprojectqs/brief-yoctoprojectqs.html

when issue the "bitbake core-image-minimal"

I am keep getting this error:

ERROR:  OE-core's config sanity checker detected a potential 
misconfiguration.
    Either fix the cause of this error or at your own risk disable the 
checker (see sanity.conf).

    Following is the list of potential problems / advisories:

    Fetcher failure for URL: 'https://www.example.com/'. URL 
https://www.example.com/ doesn't work.

    Please ensure your host's network is configured correctly,
    or set BB_NO_NETWORK = "1" to disable network access if
    all required sources are on local disk.

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

[yocto] problem with ruby

[Clément Cherbeix]

Hello all,

I’m trying to add the MIB mechanics in my yocto project, for that I use dadi
(ruby depenedent) but I get an error when bitbake try to compile :

DEBUG: Executing shell function do_compile

ERROR:  Loading command: build (LoadError)

cannot load such file -- zlib

ERROR:  While executing gem ... (NoMethodError)

undefined method `invoke_with_build_args' for nil:NilClass

WARNING:
/home/modem/tkh/build/tmp/work/x86_64-linux/libxml-ruby-native/2.8.0-r0/temp
/run.do_compile.567:1 exit 1 from 'LANG="en_US.UTF-8" LC_ALL="en_US.UTF-8"
gem build $gem'

 

I have tried to build the gem in an environment outside of Yocto and it was
correct but when I try to do it in Yocto, I get my error.
Did someone have an idea on what to do ?
what is the recommended way of building ruby via gem in yocto ?

 

Here is my build environment :

BB_VERSION   = "1.40.0"

BUILD_SYS= "x86_64-linux"

NATIVELSBSTRING  = "universal"

TARGET_SYS   = "x86_64-poky-linux"

DISTRO   = "poky"

DISTRO_VERSION   = "2.6.1"

TUNE_FEATURES= "m64 corei7"

 

Thanks in advance !

 

Clément C.

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

[yocto] Yocto Project Unassigned Bugs - Help Needed

[sjolley.yp.pm]

All,

 

The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the triage team)
are therefore going to start reporting out the currently 281 unassigned
bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.

 

Bugs are split into two types, "true bugs" where things don't work as they
should and "enhancements" which are features we'd want to add to the system.

 

There are also roughly four different "priority" classes right now, "2.7",
"2.8", "2.9', "2.99" and "Future", the more pressing/urgent issues being in
"2.7" and then "2.8".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me
(stephen.k.jol...@intel.com  ) an e-mail
with the bug number you would like and I will assign it to you (please make
sure you have a Bugzilla account).

 

The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

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

Re: [yocto] shared cmake modules

[Henrik Lindblom]

>
> FILES_${PN}-dev = "${MODULES_DEST_PATH}/*"
>

Does your library recipe explicitly depend on -dev? Can you
share the failing recipe?

Cheers,
Henrik

On Wed, Apr 3, 2019 at 1:18 PM Gabriele Zampieri 
wrote:

> Hi all,
>
> I'm setting up a layer that will compile our applications and libraries.
> All the applications are based on cmake and they share modules. Before
> using yocto I kept the modules in /cmake (under version control)
> alongside applications and libraries. With yocto I wrote a recipe that
> checkout the module repo and install them in
> "${STAGING_DATADIR}/cmake/Modules/". I took this path from
> "meta/classes/cmake.bbclass". If i build the module target, I get the files
> installed in the target recipe datadir. If I want to build a library (that
> depends also on my modules recipe) the task do_configure fails because
> cmake cannot find none of my include. Digging around I found that the
> toolchain.cmake file points to a module location that doesn't exist in the
> library workdir, but in module recipe (${STAGING_DATADIR}/cmake/Modules/).
>
> The module recipe looks like as follow:
>
> MODULES_DEST_PATH = "${STAGING_DATADIR}/cmake/Modules"
> FILES_${PN}-dev = "${MODULES_DEST_PATH}/*"
>
> do_install() {
> DEST_DIR=${MODULES_DEST_PATH}
>
> # Create the destination folder
> install -d $DEST_DIR
> install -m 0444 ${S}/my/module.cmake $DEST_DIR
> ..
> }
>
> So my question is: where should I install the shared modules
> (MODULE_DEST_PATH int the above snippet)? and how to update the
> CMAKE_MODULE_PATH properly to append that location?
>
> Thanks,
> Gabriele
> --
> ___
> 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] Installation help

[Nataliya Korovkina]

Hello Karshi,

I had the same message. I added:

CONNECTIVITY_CHECK_URIS=""

in conf/local.conf as a QUICK FIX. I hope someone has better solution,
please?

Thanks,
Nataliya


On Mon, Apr 8, 2019 at 12:43 PM Karshi Hasanov 
wrote:

> Hi all,
>
> I have followed the
>
>
> https://www.yoctoproject.org/docs/2.6.1/brief-yoctoprojectqs/brief-yoctoprojectqs.html
>
> when issue the "bitbake core-image-minimal"
>
> I am keep getting this error:
>
> ERROR:  OE-core's config sanity checker detected a potential
> misconfiguration.
>  Either fix the cause of this error or at your own risk disable the
> checker (see sanity.conf).
>  Following is the list of potential problems / advisories:
>
>  Fetcher failure for URL: 'https://www.example.com/'. URL
> https://www.example.com/ doesn't work.
>  Please ensure your host's network is configured correctly,
>  or set BB_NO_NETWORK = "1" to disable network access if
>  all required sources are on local disk.
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>


-- 


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

Re: [yocto] Installation help

[Burton, Ross]

The better fix is to fix your network.  If you need a proxy, set it in
local.conf.

Ross

On Mon, 8 Apr 2019 at 18:09, Nataliya Korovkina
 wrote:
>
> Hello Karshi,
>
> I had the same message. I added:
>
> CONNECTIVITY_CHECK_URIS=""
>
> in conf/local.conf as a QUICK FIX. I hope someone has better solution, please?
>
> Thanks,
> Nataliya
>
>
> On Mon, Apr 8, 2019 at 12:43 PM Karshi Hasanov  
> wrote:
>>
>> Hi all,
>>
>> I have followed the
>>
>> https://www.yoctoproject.org/docs/2.6.1/brief-yoctoprojectqs/brief-yoctoprojectqs.html
>>
>> when issue the "bitbake core-image-minimal"
>>
>> I am keep getting this error:
>>
>> ERROR:  OE-core's config sanity checker detected a potential
>> misconfiguration.
>>  Either fix the cause of this error or at your own risk disable the
>> checker (see sanity.conf).
>>  Following is the list of potential problems / advisories:
>>
>>  Fetcher failure for URL: 'https://www.example.com/'. URL
>> https://www.example.com/ doesn't work.
>>  Please ensure your host's network is configured correctly,
>>  or set BB_NO_NETWORK = "1" to disable network access if
>>  all required sources are on local disk.
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
> --
>
>
> Nataliya Korovkina
>
> --
> ___
> 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] problem with ruby

[Khem Raj]

On Mon, Apr 8, 2019 at 9:44 AM Clément Cherbeix
 wrote:
>
> Hello all,
>
> I’m trying to add the MIB mechanics in my yocto project, for that I use dadi 
> (ruby depenedent) but I get an error when bitbake try to compile :
>
> DEBUG: Executing shell function do_compile
>
> ERROR:  Loading command: build (LoadError)
>
> cannot load such file -- zlib
>
> ERROR:  While executing gem ... (NoMethodError)
>
> undefined method `invoke_with_build_args' for nil:NilClass
>
> WARNING: 
> /home/modem/tkh/build/tmp/work/x86_64-linux/libxml-ruby-native/2.8.0-r0/temp/run.do_compile.567:1
>  exit 1 from 'LANG="en_US.UTF-8" LC_ALL="en_US.UTF-8" gem build $gem'
>
>
>
> I have tried to build the gem in an environment outside of Yocto and it was 
> correct but when I try to do it in Yocto, I get my error.
> Did someone have an idea on what to do ?
> what is the recommended way of building ruby via gem in yocto ?
>
>

It seems that it is using ruby-native but does not have zlib-native
and it cant find this library. Can you add zlib to DEPENDS in ruby
recipe and see if that helps.

>
> Here is my build environment :
>
> BB_VERSION   = "1.40.0"
>
> BUILD_SYS= "x86_64-linux"
>
> NATIVELSBSTRING  = "universal"
>
> TARGET_SYS   = "x86_64-poky-linux"
>
> DISTRO   = "poky"
>
> DISTRO_VERSION   = "2.6.1"
>
> TUNE_FEATURES= "m64 corei7"
>
>
>
> Thanks in advance !
>
>
>
> Clément C.
>
> --
> ___
> 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] Development environment for Grub bootloader and Linux

[Khem Raj]

On Mon, Apr 8, 2019 at 9:39 AM Srinivasa RaoW  wrote:
>
> Dear All,
>
> I have a requirement of modifying Grub bootloader for x86 architecture but 
> Just read the Wiki Page of Yocto and it states as below”
>
> “The Yocto Project is an open-source project that delivers a set of tools 
> that create operating system images for embedded Linux systems”
>
> Towards this I have below questions:
>
> Does Yocto project support only Linux systems?

yes

> Do we have repositories/build tool chain for Grub bootloader?


> Which is the bootloader that Yocto project recommends for x86 architecture?

It supports multiple bootloaders e.g. grub2, syslinux, systemd-boot
etc. its upto distro to choose which ever they want

I would suggest to look into devtool workflow with yocto/OE this is
recommended tool for doing cross development

http://events17.linuxfoundation.org/sites/events/files/slides/2017%20ELC%20--%20Using%20devtool%20to%20Streamline%20your%20Yocto%20Project%20Workflow.pdf

>
> I am trying to setup a development environment under Ubunt Host for x86 
> target architecture.  Goal is to build Grub bootloader, Ubuntu linux and root 
> file system all together under one umbrella.
>
> Please let me know if Yocto has anything for this.
>
> Appreciate any input on this.
>
> Regards
>
> Srinivasa
>
>
>
> L&T Technology Services Ltd
>
> www.LTTS.com
>
> This Email may contain confidential or privileged information for the 
> intended recipient (s). If you are not the intended recipient, please do not 
> use or disseminate the information, notify the sender and delete it from your 
> system.
>
> --
> ___
> 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] Installation help

[Burton, Ross]

There must be if example.com can't be downloaded from...

On Mon, 8 Apr 2019 at 19:49, Karshi Hasanov  wrote:
>
> There is nothing wrong with my network network!
>
> For now the issue is resolved.
>
> Thanks any way.
>
>
> On 2019-04-08 1:10 p.m., Burton, Ross wrote:
> > The better fix is to fix your network.  If you need a proxy, set it in
> > local.conf.
> >
> > Ross
> >
> > On Mon, 8 Apr 2019 at 18:09, Nataliya Korovkina
> >  wrote:
> >> Hello Karshi,
> >>
> >> I had the same message. I added:
> >>
> >> CONNECTIVITY_CHECK_URIS=""
> >>
> >> in conf/local.conf as a QUICK FIX. I hope someone has better solution, 
> >> please?
> >>
> >> Thanks,
> >> Nataliya
> >>
> >>
> >> On Mon, Apr 8, 2019 at 12:43 PM Karshi Hasanov  
> >> wrote:
> >>> Hi all,
> >>>
> >>> I have followed the
> >>>
> >>> https://www.yoctoproject.org/docs/2.6.1/brief-yoctoprojectqs/brief-yoctoprojectqs.html
> >>>
> >>> when issue the "bitbake core-image-minimal"
> >>>
> >>> I am keep getting this error:
> >>>
> >>> ERROR:  OE-core's config sanity checker detected a potential
> >>> misconfiguration.
> >>>   Either fix the cause of this error or at your own risk disable the
> >>> checker (see sanity.conf).
> >>>   Following is the list of potential problems / advisories:
> >>>
> >>>   Fetcher failure for URL: 'https://www.example.com/'. URL
> >>> https://www.example.com/ doesn't work.
> >>>   Please ensure your host's network is configured correctly,
> >>>   or set BB_NO_NETWORK = "1" to disable network access if
> >>>   all required sources are on local disk.
> >>>
> >>> --
> >>> ___
> >>> yocto mailing list
> >>> yocto@yoctoproject.org
> >>> https://lists.yoctoproject.org/listinfo/yocto
> >>
> >>
> >> --
> >>
> >>
> >> Nataliya Korovkina
> >>
> >> --
> >> ___
> >> 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] Installation help

[Nataliya Korovkina]

"example.com" is not working. If someone needs to check their connection
this way, please use CONNECTIVITY_CHECK_URIS="https://www.yoctoproject.org";

N

On Mon, Apr 8, 2019 at 2:50 PM Burton, Ross  wrote:

> There must be if example.com can't be downloaded from...
>
> On Mon, 8 Apr 2019 at 19:49, Karshi Hasanov 
> wrote:
> >
> > There is nothing wrong with my network network!
> >
> > For now the issue is resolved.
> >
> > Thanks any way.
> >
> >
> > On 2019-04-08 1:10 p.m., Burton, Ross wrote:
> > > The better fix is to fix your network.  If you need a proxy, set it in
> > > local.conf.
> > >
> > > Ross
> > >
> > > On Mon, 8 Apr 2019 at 18:09, Nataliya Korovkina
> > >  wrote:
> > >> Hello Karshi,
> > >>
> > >> I had the same message. I added:
> > >>
> > >> CONNECTIVITY_CHECK_URIS=""
> > >>
> > >> in conf/local.conf as a QUICK FIX. I hope someone has better
> solution, please?
> > >>
> > >> Thanks,
> > >> Nataliya
> > >>
> > >>
> > >> On Mon, Apr 8, 2019 at 12:43 PM Karshi Hasanov <
> karshi.hasa...@gmail.com> wrote:
> > >>> Hi all,
> > >>>
> > >>> I have followed the
> > >>>
> > >>>
> https://www.yoctoproject.org/docs/2.6.1/brief-yoctoprojectqs/brief-yoctoprojectqs.html
> > >>>
> > >>> when issue the "bitbake core-image-minimal"
> > >>>
> > >>> I am keep getting this error:
> > >>>
> > >>> ERROR:  OE-core's config sanity checker detected a potential
> > >>> misconfiguration.
> > >>>   Either fix the cause of this error or at your own risk disable
> the
> > >>> checker (see sanity.conf).
> > >>>   Following is the list of potential problems / advisories:
> > >>>
> > >>>   Fetcher failure for URL: 'https://www.example.com/'. URL
> > >>> https://www.example.com/ doesn't work.
> > >>>   Please ensure your host's network is configured correctly,
> > >>>   or set BB_NO_NETWORK = "1" to disable network access if
> > >>>   all required sources are on local disk.
> > >>>
> > >>> --
> > >>> ___
> > >>> yocto mailing list
> > >>> yocto@yoctoproject.org
> > >>> https://lists.yoctoproject.org/listinfo/yocto
> > >>
> > >>
> > >> --
> > >>
> > >>
> > >> Nataliya Korovkina
> > >>
> > >> --
> > >> ___
> > >> yocto mailing list
> > >> yocto@yoctoproject.org
> > >> https://lists.yoctoproject.org/listinfo/yocto
>


-- 


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

Re: [yocto] m4-mative: "Please port gnulib fseeko.c to your platform!"

[Robert P. J. Day]

On Mon, 8 Apr 2019, Robert P. J. Day wrote:

>
>   a few months ago, i ran into (and asked about) a failure building
> m4-native that you can read here:
>
> https://yocto.yoctoproject.narkive.com/6KyM5UvS/m4-native-zedboard-please-port-gnulib-fseeko-c-to-your-platform
>
> first, i will admit i'm not sure where the fault lies -- is it m4, or
> gnulib, or glibc, and whose responsibility is it to fix what. i'll be
> honest -- i don't understand what the bug is or who should be
> resolving it.
>
>   i ask all this as i just had *exactly* the same error trying to
> build agl-image-minimal with the AGL code base. what is the proper
> solution to this? BTW, i'm trying this on fedora 30 branched, so this
> is definitely not a supported build distro, but i'm still curious as
> to what would be the proper fix.
>
>   finally, it occurs to me that, if building a native package like
> "m4" fails, would it be a reasonable workaround to simply say
>
>   ASSUME_PROVIDED += "m4"
>
> for the time being, to avoid having to build it until i know what the
> proper fix is?

  trying ASSUME_PROVIDED didn't work all that well, either ...

...
| autom4te: need GNU m4 1.4 or later: m4
| make[2]: *** [Makefile:641: autoconf.in] Error 1
...

  that's just weird as my installed version of m4 is 1.4.18, precisely
the version AGL is trying to build. i'm confused.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
 http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

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

[yocto] m4-mative: "Please port gnulib fseeko.c to your platform!"

[Robert P. J. Day]

  a few months ago, i ran into (and asked about) a failure building
m4-native that you can read here:

https://yocto.yoctoproject.narkive.com/6KyM5UvS/m4-native-zedboard-please-port-gnulib-fseeko-c-to-your-platform

first, i will admit i'm not sure where the fault lies -- is it m4, or
gnulib, or glibc, and whose responsibility is it to fix what. i'll be
honest -- i don't understand what the bug is or who should be
resolving it.

  i ask all this as i just had *exactly* the same error trying to
build agl-image-minimal with the AGL code base. what is the proper
solution to this? BTW, i'm trying this on fedora 30 branched, so this
is definitely not a supported build distro, but i'm still curious as
to what would be the proper fix.

  finally, it occurs to me that, if building a native package like
"m4" fails, would it be a reasonable workaround to simply say

  ASSUME_PROVIDED += "m4"

for the time being, to avoid having to build it until i know what the
proper fix is?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
 http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

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

Re: [yocto] m4-mative: "Please port gnulib fseeko.c to your platform!"

[Burton, Ross]

Looks like that bug in gnulib that broke m4 (and others) when glibc changed.

Fixed upstream 
https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=4af4a4a718
and oe-core master/thud/possibly sumo also carry the relevant patch
for m4.

If you're using older releases against a newer release then 1) this is
why we have supported host distros and 2) the patch is easy to
backport.

Ross

On Mon, 8 Apr 2019 at 21:45, Robert P. J. Day  wrote:
>
>
>   a few months ago, i ran into (and asked about) a failure building
> m4-native that you can read here:
>
> https://yocto.yoctoproject.narkive.com/6KyM5UvS/m4-native-zedboard-please-port-gnulib-fseeko-c-to-your-platform
>
> first, i will admit i'm not sure where the fault lies -- is it m4, or
> gnulib, or glibc, and whose responsibility is it to fix what. i'll be
> honest -- i don't understand what the bug is or who should be
> resolving it.
>
>   i ask all this as i just had *exactly* the same error trying to
> build agl-image-minimal with the AGL code base. what is the proper
> solution to this? BTW, i'm trying this on fedora 30 branched, so this
> is definitely not a supported build distro, but i'm still curious as
> to what would be the proper fix.
>
>   finally, it occurs to me that, if building a native package like
> "m4" fails, would it be a reasonable workaround to simply say
>
>   ASSUME_PROVIDED += "m4"
>
> for the time being, to avoid having to build it until i know what the
> proper fix is?
>
> rday
>
> --
>
> 
> Robert P. J. Day Ottawa, Ontario, CANADA
>  http://crashcourse.ca
>
> Twitter:   http://twitter.com/rpjday
> LinkedIn:   http://ca.linkedin.com/in/rpjday
> 
> --
> ___
> 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] [sumo] [PATCH v1] systemd: fix musl compilation

[Sinan Kaya]

On 3/29/2019 10:42 AM, Sinan Kaya wrote:

musl compilation has been broken since systemd: fix CVE-2018-6954. Fixing this
by placing #ifdef for glob definition.

Signed-off-by: Sinan Kaya


I didn't see any comments here but I wanted to let everyone know that
sumo-next branch is currently broken with MUSL unless this patch is
applied.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [sumo] [PATCH v1] systemd: fix musl compilation

[akuster]

On 4/9/19 5:45 AM, Sinan Kaya wrote:
> On 3/29/2019 10:42 AM, Sinan Kaya wrote:
>> musl compilation has been broken since systemd: fix CVE-2018-6954.
>> Fixing this
>> by placing #ifdef for glob definition.
>>
>> Signed-off-by: Sinan Kaya
>
> I didn't see any comments here but I wanted to let everyone know that
> sumo-next branch is currently broken with MUSL unless this patch is
> applied.

Thanks for the reminder. it will be in my next merge series.

- armin

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

[yocto] [meta-security][PATCH] clamav: add clamav-cvd package for cvd db

[Armin Kuster]

Add native package to support creating a mirror
of the clamav cvd and supply it in a new package.

Provide a INSTALL_CLAMAV_CVD flag to bypass this creation

Signed-off-by: Armin Kuster 
---
 recipes-security/clamav/clamav_0.99.4.bb   |  41 +++-
 .../clamav/files/freshclam-native.conf | 224 +
 2 files changed, 259 insertions(+), 6 deletions(-)
 create mode 100644 recipes-security/clamav/files/freshclam-native.conf

diff --git a/recipes-security/clamav/clamav_0.99.4.bb 
b/recipes-security/clamav/clamav_0.99.4.bb
index 3fc48e7..32dc59c 100644
--- a/recipes-security/clamav/clamav_0.99.4.bb
+++ b/recipes-security/clamav/clamav_0.99.4.bb
@@ -4,8 +4,9 @@ HOMEPAGE = "http://www.clamav.net/index.html";
 SECTION = "security"
 LICENSE = "LGPL-2.1"
 
-DEPENDS = "libtool db libmspack chrpath-replacement-native"
-
+DEPENDS = "libtool db libmspack chrpath-replacement-native clamav-native"
+DEPENDS_class-native = "db-native"
+ 
 LIC_FILES_CHKSUM = 
"file://COPYING.LGPL;beginline=2;endline=3;md5=4b89c05acc71195e9a06edfa2fa7d092"
 
 SRCREV = "b66e5e27b48c0a07494f9df9b809ed933cede047"
@@ -15,6 +16,7 @@ SRC_URI = 
"git://github.com/vrtadmin/clamav-devel;branch=rel/0.99 \
 file://freshclam.conf \
 file://volatiles.03_clamav \
 file://${BPN}.service \
+file://freshclam-native.conf \
 "
 
 S = "${WORKDIR}/git"
@@ -28,6 +30,7 @@ inherit autotools-brokensep pkgconfig useradd systemd
 
 UID = "clamav"
 GID = "clamav"
+INSTALL_CLAMAV_CVD ?= "1"
 
 # Clamav has a built llvm version 2 but does not build with gcc 6.x,
 # disable the internal one. This is a known issue
@@ -58,12 +61,27 @@ EXTRA_OECONF += " --with-user=${UID}  --with-group=${GID} \
 --disable-rpath \
 "
 
+EXTRA_OECONF_class-native += "--without-libcheck-prefix --disable-unrar \
+--with-system-llvm --with-llvm-linking=dynamic --disable-llvm \
+--disable-mempool \
+--program-prefix="" \
+--disable-yara \
+--without-libbz2-prefix --without-zlib \
+"
+
 do_configure () {
 cd ${S}
 ./configure ${CONFIGUREOPTS} ${EXTRA_OECONF} 
+install -d ${S}/clamav_db
 }
 
-do_compile_append() {
+do_configure_class-native () {
+cd ${S}
+./configure ${CONFIGUREOPTS} ${EXTRA_OECONF} 
+}
+
+
+do_compile_append_class-target() {
 # brute force removing RPATH
 chrpath -d  ${B}/libclamav/.libs/libclamav.so.${SO_VER}
 chrpath -d  ${B}/sigtool/.libs/sigtool
@@ -72,9 +90,14 @@ do_compile_append() {
 chrpath -d  ${B}/clamconf/.libs/clamconf
 chrpath -d  ${B}/clamd/.libs/clamd
 chrpath -d  ${B}/freshclam/.libs/freshclam
+
+if [ "${INSTALL_CLAMAV_CVD}" = "1" ]; then
+bbnote "CLAMAV creating cvd"
+${STAGING_BINDIR_NATIVE}/freshclam --datadir=${S}/clamav_db 
--config=${WORKDIR}/freshclam-native.conf
+fi
 }
 
-do_install_append() {
+do_install_append_class-target () {
 install -d ${D}/${sysconfdir}
 install -d ${D}/${localstatedir}/lib/clamav
 install -d ${D}${sysconfdir}/clamav ${D}${sysconfdir}/default/volatiles
@@ -84,6 +107,7 @@ do_install_append() {
 install -m 0644 ${WORKDIR}/volatiles.03_clamav  
${D}${sysconfdir}/default/volatiles/volatiles.03_clamav
 sed -i -e 's#${STAGING_DIR_HOST}##g' ${D}${libdir}/pkgconfig/libclamav.pc
 rm ${D}/${libdir}/libclamav.so
+install -m 666 ${S}/clamav_db/* ${D}/${localstatedir}/lib/clamav/.
 if ${@bb.utils.contains('DISTRO_FEATURES','systemd','true','false',d)};then
 install -D -m 0644 ${WORKDIR}/clamav.service 
${D}${systemd_unitdir}/system/clamav.service
 fi
@@ -93,11 +117,11 @@ pkg_postinst_ontarget_${PN} () {
 if [ -e /etc/init.d/populate-volatile.sh ] ; then
 ${sysconfdir}/init.d/populate-volatile.sh update
 fi
-chown ${UID}:${GID} ${localstatedir}/lib/clamav
+chown -R ${UID}:${GID} ${localstatedir}/lib/clamav
 }
 
 
-PACKAGES = "${PN} ${PN}-dev ${PN}-dbg ${PN}-daemon ${PN}-doc \
+PACKAGES = "${PN} ${PN}-dev ${PN}-dbg ${PN}-daemon ${PN}-doc ${PN}-cvd \
 ${PN}-clamdscan ${PN}-freshclam ${PN}-libclamav ${PN}-staticdev"
 
 FILES_${PN} = "${bindir}/clambc ${bindir}/clamscan ${bindir}/clamsubmit \
@@ -140,6 +164,8 @@ FILES_${PN}-doc = "${mandir}/man/* \
${datadir}/man/* \
${docdir}/* "
 
+FILES_${PN}-cvd =  "${localstatedir}/lib/clamav/*.cvd 
${localstatedir}/lib/clamav/*.dat"
+
 USERADD_PACKAGES = "${PN}"
 GROUPADD_PARAM_${PN} = "--system ${UID}"
 USERADD_PARAM_${PN} = "--system -g ${GID} --home-dir  \
@@ -152,3 +178,6 @@ RCONFLICTS_${PN} += "${PN}-systemd"
 SYSTEMD_SERVICE_${PN} = "${BPN}.service"
 
 RDEPENDS_${PN} += "openssl ncurses-libncurses libbz2 ncurses-libtinfo 
clamav-freshclam clamav-libclamav"
+RDEPENDS_${PN}_class-native = ""
+
+BBCLASSEXTEND = "native"
diff --git a/recipes-security/clamav/files/freshclam-native.conf 
b/recipes-security/clamav/files/freshclam-native.conf
new file mode 100644
index 000..aaa8cf4