Error on building

Error on building

[ratheesh kannoth]

I am getting following error. what is the problem. ? How can i get around this ?


ERROR: QA Issue: non -staticdev package contains static .a library:
sf-test path '/work/x86_64-wrs-linux/sf/1.0-r0/packages-split/sf-test/lib/snort_dynamicengine/libsf_engine.a'
ERROR: QA Issue: sf-test:
/work/x86_64-wrs-linux/sf/1.0-r0/packages-split/sf-test/lib/snort_dynamicengine/libsf_engine.so.0.0.0
contains probably-redundant RPATH /usr/lib64


Thanks,
Ratheesh

Re: Error on building

[Alex J Lennon]

On 05/03/2014 08:01, ratheesh kannoth wrote:
> I am getting following error. what is the problem. ? How can i get around this ?
>
>
> ERROR: QA Issue: non -staticdev package contains static .a library:
> sf-test path '/work/x86_64-wrs-linux/sf/1.0-r0/packages-split/sf-test/lib/snort_dynamicengine/libsf_engine.a'
> ERROR: QA Issue: sf-test:
> /work/x86_64-wrs-linux/sf/1.0-r0/packages-split/sf-test/lib/snort_dynamicengine/libsf_engine.so.0.0.0
> contains probably-redundant RPATH /usr/lib64
>

Ratheesh, I believe you would need to ensure that any static libraries
built are either removed or packaged appropriately so as not to trigger
the Q/A error.

One approach is to modify the recipe to add the static library to the
-staticdev package, i.e. to add

FILES_${PN}-staticdev += " path\to\static\library\libsf_engine.a"

What recipe are you trying to build?

Cheers,

Alex

> Thanks,
> Ratheesh
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
represent those of the company.

Re: Error on building

[ratheesh kannoth]

On Wed, Mar 5, 2014 at 2:55 PM, Alex J Lennon
<ajlennon@dynamicdevices.co.uk> wrote:
> Ratheesh, I believe you would need to ensure that any static libraries
> built are either removed or packaged appropriately so as not to trigger
> the Q/A error.
>
> One approach is to modify the recipe to add the static library to the
> -staticdev package, i.e. to add
>
> FILES_${PN}-staticdev += " path\to\static\library\libsf_engine.a"
>
> What recipe are you trying to build?
>
> Cheers,
>
> Alex

Alex,
Thanks. I am trying  to compile snort package.  I could easily get
around these problems using  INSANE_SKIP.  But a new problem popped
up. I have compiled  libdnet with out  a SONAME. So snort binary
contains , ( ldd shows ) a full path to the library.  So rootfs build
fails with
following error.

Computing transaction...error: Can't install sf-test-1.0-r0.6@x86_64:
no package provides
/workspace/linux/wrlinux/bitbake_build/tmp/sysroots/intel-x86-64/usr/lib64/libdnet()(64bit)

I can rebuild libdnet with  SONAME ( linker flag ) and solve this
problem  OR  I can put SKIP_FILEDEPS = "1" in  sf  recipe file. But
SKIP_FILEDEPS  will skip every check  in all recipes. I am looking
something similar  option like  INSANE_SKIP_${PN} += "dev-so" ??

-Ratheesh

Re: Error on building

[Alex J Lennon]

On 05/03/2014 16:15, ratheesh kannoth wrote:
> On Wed, Mar 5, 2014 at 2:55 PM, Alex J Lennon
> <ajlennon@dynamicdevices.co.uk> wrote:
>> Ratheesh, I believe you would need to ensure that any static libraries
>> built are either removed or packaged appropriately so as not to trigger
>> the Q/A error.
>>
>> One approach is to modify the recipe to add the static library to the
>> -staticdev package, i.e. to add
>>
>> FILES_${PN}-staticdev += " path\to\static\library\libsf_engine.a"
>>
>> What recipe are you trying to build?
>>
>> Cheers,
>>
>> Alex
> Alex,
> Thanks. I am trying  to compile snort package.  I could easily get
> around these problems using  INSANE_SKIP.  But a new problem popped
> up. I have compiled  libdnet with out  a SONAME. So snort binary
> contains , ( ldd shows ) a full path to the library.  So rootfs build
> fails with
> following error.
>
> Computing transaction...error: Can't install sf-test-1.0-r0.6@x86_64:
> no package provides
> /workspace/linux/wrlinux/bitbake_build/tmp/sysroots/intel-x86-64/usr/lib64/libdnet()(64bit)
>
> I can rebuild libdnet with  SONAME ( linker flag ) and solve this
> problem  OR  I can put SKIP_FILEDEPS = "1" in  sf  recipe file. But
> SKIP_FILEDEPS  will skip every check  in all recipes. I am looking
> something similar  option like  INSANE_SKIP_${PN} += "dev-so" ??

That's interesting Ratheesh. Is there a reason for not including the
soname attribute in libdnet?

I would have thought that in a situation like that where there's no
soname the snort binary shared library path should be fixed up to the
target path, a relative path, rather than an absolute host path?

Cheers,

Alex

> -Ratheesh

Re: Error on building

[ratheesh kannoth]

On Wed, Mar 5, 2014 at 10:07 PM, Alex J Lennon
<ajlennon@dynamicdevices.co.uk> wrote:
>
> On 05/03/2014 16:15, ratheesh kannoth wrote:
>> On Wed, Mar 5, 2014 at 2:55 PM, Alex J Lennon
>> <ajlennon@dynamicdevices.co.uk> wrote:
>>> Ratheesh, I believe you would need to ensure that any static libraries
>>> built are either removed or packaged appropriately so as not to trigger
>>> the Q/A error.
>>>
>>> One approach is to modify the recipe to add the static library to the
>>> -staticdev package, i.e. to add
>>>
>>> FILES_${PN}-staticdev += " path\to\static\library\libsf_engine.a"
>>>
>>> What recipe are you trying to build?
>>>
>>> Cheers,
>>>
>>> Alex
>> Alex,
>> Thanks. I am trying  to compile snort package.  I could easily get
>> around these problems using  INSANE_SKIP.  But a new problem popped
>> up. I have compiled  libdnet with out  a SONAME. So snort binary
>> contains , ( ldd shows ) a full path to the library.  So rootfs build
>> fails with
>> following error.
>>
>> Computing transaction...error: Can't install sf-test-1.0-r0.6@x86_64:
>> no package provides
>> /workspace/linux/wrlinux/bitbake_build/tmp/sysroots/intel-x86-64/usr/lib64/libdnet()(64bit)
>>
>> I can rebuild libdnet with  SONAME ( linker flag ) and solve this
>> problem  OR  I can put SKIP_FILEDEPS = "1" in  sf  recipe file. But
>> SKIP_FILEDEPS  will skip every check  in all recipes. I am looking
>> something similar  option like  INSANE_SKIP_${PN} += "dev-so" ??
>
> That's interesting Ratheesh. Is there a reason for not including the
> soname attribute in libdnet?
>
> I would have thought that in a situation like that where there's no
> soname the snort binary shared library path should be fixed up to the
> target path, a relative path, rather than an absolute host path?
>
> Cheers,
>
> Alex
>
>> -Ratheesh
>

I removed soname by mistake.

I would like to know about workarounds  if such problem comes in yocto. Could u
enlighten me

-Ratheesh

Re: Error on building

[Alex J Lennon]

On 05/03/2014 16:54, ratheesh kannoth wrote:
> On Wed, Mar 5, 2014 at 10:07 PM, Alex J Lennon
> <ajlennon@dynamicdevices.co.uk> wrote:
>> On 05/03/2014 16:15, ratheesh kannoth wrote:
>>> On Wed, Mar 5, 2014 at 2:55 PM, Alex J Lennon
>>> <ajlennon@dynamicdevices.co.uk> wrote:
>>>> Ratheesh, I believe you would need to ensure that any static libraries
>>>> built are either removed or packaged appropriately so as not to trigger
>>>> the Q/A error.
>>>>
>>>> One approach is to modify the recipe to add the static library to the
>>>> -staticdev package, i.e. to add
>>>>
>>>> FILES_${PN}-staticdev += " path\to\static\library\libsf_engine.a"
>>>>
>>>> What recipe are you trying to build?
>>>>
>>>> Cheers,
>>>>
>>>> Alex
>>> Alex,
>>> Thanks. I am trying  to compile snort package.  I could easily get
>>> around these problems using  INSANE_SKIP.  But a new problem popped
>>> up. I have compiled  libdnet with out  a SONAME. So snort binary
>>> contains , ( ldd shows ) a full path to the library.  So rootfs build
>>> fails with
>>> following error.
>>>
>>> Computing transaction...error: Can't install sf-test-1.0-r0.6@x86_64:
>>> no package provides
>>> /workspace/linux/wrlinux/bitbake_build/tmp/sysroots/intel-x86-64/usr/lib64/libdnet()(64bit)
>>>
>>> I can rebuild libdnet with  SONAME ( linker flag ) and solve this
>>> problem  OR  I can put SKIP_FILEDEPS = "1" in  sf  recipe file. But
>>> SKIP_FILEDEPS  will skip every check  in all recipes. I am looking
>>> something similar  option like  INSANE_SKIP_${PN} += "dev-so" ??
>> That's interesting Ratheesh. Is there a reason for not including the
>> soname attribute in libdnet?
>>
>> I would have thought that in a situation like that where there's no
>> soname the snort binary shared library path should be fixed up to the
>> target path, a relative path, rather than an absolute host path?
>>
>> Cheers,
>>
>> Alex
>>
>>> -Ratheesh
> I removed soname by mistake.
>
> I would like to know about workarounds  if such problem comes in yocto. Could u
> enlighten me

I'm no expert I'm afraid Ratheesh. I try to avoid the workarounds
as they usually cause me problems down the road, but I'd probably
look at the same thing as you with INSANE_SKIP_

...

Hunting around a little it does look as though you can do per-recipe dep
skips though,
and indeed per-package skips

http://patches.openembedded.org/patch/43457/


> -Ratheesh

Re: Error on building

[ratheesh kannoth]

On Wed, Mar 5, 2014 at 10:31 PM, Alex J Lennon
<ajlennon@dynamicdevices.co.uk> wrote:
>
> On 05/03/2014 16:54, ratheesh kannoth wrote:
>> On Wed, Mar 5, 2014 at 10:07 PM, Alex J Lennon
>> <ajlennon@dynamicdevices.co.uk> wrote:
>>> On 05/03/2014 16:15, ratheesh kannoth wrote:
>>>> On Wed, Mar 5, 2014 at 2:55 PM, Alex J Lennon
>>>> <ajlennon@dynamicdevices.co.uk> wrote:
>>>>> Ratheesh, I believe you would need to ensure that any static libraries
>>>>> built are either removed or packaged appropriately so as not to trigger
>>>>> the Q/A error.
>>>>>
>>>>> One approach is to modify the recipe to add the static library to the
>>>>> -staticdev package, i.e. to add
>>>>>
>>>>> FILES_${PN}-staticdev += " path\to\static\library\libsf_engine.a"
>>>>>
>>>>> What recipe are you trying to build?
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Alex
>>>> Alex,
>>>> Thanks. I am trying  to compile snort package.  I could easily get
>>>> around these problems using  INSANE_SKIP.  But a new problem popped
>>>> up. I have compiled  libdnet with out  a SONAME. So snort binary
>>>> contains , ( ldd shows ) a full path to the library.  So rootfs build
>>>> fails with
>>>> following error.
>>>>
>>>> Computing transaction...error: Can't install sf-test-1.0-r0.6@x86_64:
>>>> no package provides
>>>> /workspace/linux/wrlinux/bitbake_build/tmp/sysroots/intel-x86-64/usr/lib64/libdnet()(64bit)
>>>>
>>>> I can rebuild libdnet with  SONAME ( linker flag ) and solve this
>>>> problem  OR  I can put SKIP_FILEDEPS = "1" in  sf  recipe file. But
>>>> SKIP_FILEDEPS  will skip every check  in all recipes. I am looking
>>>> something similar  option like  INSANE_SKIP_${PN} += "dev-so" ??
>>> That's interesting Ratheesh. Is there a reason for not including the
>>> soname attribute in libdnet?
>>>
>>> I would have thought that in a situation like that where there's no
>>> soname the snort binary shared library path should be fixed up to the
>>> target path, a relative path, rather than an absolute host path?
>>>
>>> Cheers,
>>>
>>> Alex
>>>
>>>> -Ratheesh
>> I removed soname by mistake.
>>
>> I would like to know about workarounds  if such problem comes in yocto. Could u
>> enlighten me
>
> I'm no expert I'm afraid Ratheesh. I try to avoid the workarounds
> as they usually cause me problems down the road, but I'd probably
> look at the same thing as you with INSANE_SKIP_
>
> ...
>
> Hunting around a little it does look as though you can do per-recipe dep
> skips though,
> and indeed per-package skips
>
> http://patches.openembedded.org/patch/43457/
>
>
>> -Ratheesh
>

This wont work. I dont think this patch ever went into pain.

Re: Error on building

[Alex J Lennon]

On 05/03/2014 17:03, ratheesh kannoth wrote:
> This wont work. I dont think this patch ever went into pain. 

I could be wrong, but looking at my current
poky/meta/classes/package.bbclass it looks like it's in there around
line 1288

http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/package.bbclass#n1288

A/

Re: Error on building

[Khem Raj]

On Wed, Mar 5, 2014 at 12:01 AM, ratheesh kannoth
<ratheesh.ksz@gmail.com> wrote:
> ERROR: QA Issue: non -staticdev package contains static .a library:
> sf-test path '/work/x86_64-wrs-linux/sf/1.0-r0/packages-split/sf-test/lib/snort_dynamicengine/libsf_engine.a'

for this you have to adjust packaging FILES_${PN}-staticdev +=
"${base_libdir}/snort_dynamicengine/libsf_engine.a"

> ERROR: QA Issue: sf-test:
> /work/x86_64-wrs-linux/sf/1.0-r0/packages-split/sf-test/lib/snort_dynamicengine/libsf_engine.so.0.0.0
> contains probably-redundant RPATH /usr/lib64

This is a bit harder one, you need to look into build system of sf and
see if it using wrong version of libtool or somesuch
where its not setting up -rpath or -rpath-link or -rpath-dynamic
properly relative to sysroot.