target rpm build failure

target rpm build failure

[Giuseppe Condorelli]

[-- Attachment #1: Type: text/plain, Size: 473 bytes --]

Hi All,

I'm falling in error building rpm-5.4.0 for target.
It fails on undefined reference to xmalloc, xcalloc, etc... that however
are internally defined and used as wrapper for real malloc, etc...
Please, can somebody try to build this package for me?
NOTE: the rpm build inclusion is dued by the "package-management" added in
the IMAGE_FEATURE for core-image-minimal.
NOTE2: I've pulled latest oe-core since two hours.

Many thanks for your help.
Giuseppe

[-- Attachment #2: Type: text/html, Size: 587 bytes --]

Re: target rpm build failure

[Khem Raj]

On Wed, May 30, 2012 at 8:18 AM, Giuseppe Condorelli
<giuseppe.condorelli@gmail.com> wrote:
> It fails on undefined reference to xmalloc, xcalloc, etc... that however are
> internally defined and used as wrapper for real malloc, etc...
> Please, can somebody try to build this package for me?

are you using  uclibc for system C library ?

Re: target rpm build failure

[Giuseppe Condorelli]

[-- Attachment #1: Type: text/plain, Size: 642 bytes --]

Hi Khem,

2012/5/30 Khem Raj <raj.khem@gmail.com>

> On Wed, May 30, 2012 at 8:18 AM, Giuseppe Condorelli
> <giuseppe.condorelli@gmail.com> wrote:
> > It fails on undefined reference to xmalloc, xcalloc, etc... that however
> are
> > internally defined and used as wrapper for real malloc, etc...
> > Please, can somebody try to build this package for me?
>
> are you using  uclibc for system C library ?
>
Yes, I do!

>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>

[-- Attachment #2: Type: text/html, Size: 1399 bytes --]

Re: target rpm build failure

[Giuseppe Condorelli]

[-- Attachment #1: Type: text/plain, Size: 827 bytes --]

2012/5/31 Giuseppe Condorelli <giuseppe.condorelli@gmail.com>

> Hi Khem,
>
> 2012/5/30 Khem Raj <raj.khem@gmail.com>
>
>> On Wed, May 30, 2012 at 8:18 AM, Giuseppe Condorelli
>> <giuseppe.condorelli@gmail.com> wrote:
>> > It fails on undefined reference to xmalloc, xcalloc, etc... that
>> however are
>> > internally defined and used as wrapper for real malloc, etc...
>> > Please, can somebody try to build this package for me?
>>
>> are you using  uclibc for system C library ?
>>
> Yes, I do!
>
>

Is there some difference for uclibc? Please let me know.
Cheers,
Giuseppe

>
>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>
>

[-- Attachment #2: Type: text/html, Size: 2202 bytes --]

Re: target rpm build failure

[Khem Raj]

On Thu, May 31, 2012 at 5:35 AM, Giuseppe Condorelli
<giuseppe.condorelli@gmail.com> wrote:
> Is there some difference for uclibc? Please let me know.

opkg works well with uclibc based systems. Those functions are not
implemented in uclibc I am sure it can be fixed
by linking in other libs or may be creating one. However if you are
not bound to rpm then I would suggest to use opkg

in your local.conf set it

PACKAGE_CLASSES = "package_ipk"

-Khem

Re: target rpm build failure

[Giuseppe Condorelli]

[-- Attachment #1: Type: text/plain, Size: 918 bytes --]

Thanks for the reply,

unfortunately I depend from rpm, I need just rpm packages.
So can you confirm the target rpm for uclibc is not building?

Thanks again,
Giuseppe

2012/5/31 Khem Raj <raj.khem@gmail.com>

> On Thu, May 31, 2012 at 5:35 AM, Giuseppe Condorelli
> <giuseppe.condorelli@gmail.com> wrote:
> > Is there some difference for uclibc? Please let me know.
>
> opkg works well with uclibc based systems. Those functions are not
> implemented in uclibc I am sure it can be fixed
> by linking in other libs or may be creating one. However if you are
> not bound to rpm then I would suggest to use opkg
>
> in your local.conf set it
>
> PACKAGE_CLASSES = "package_ipk"
>
> -Khem
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>

[-- Attachment #2: Type: text/html, Size: 1690 bytes --]

Re: target rpm build failure

[Khem Raj]

On Thu, May 31, 2012 at 6:57 AM, Giuseppe Condorelli
<giuseppe.condorelli@gmail.com> wrote:
> unfortunately I depend from rpm, I need just rpm packages.
> So can you confirm the target rpm for uclibc is not building?

yes rpm needs to be patched for building on uclibc

Re: target rpm build failure

[Gary Thomas]

On 2012-05-31 07:57, Giuseppe Condorelli wrote:
> Thanks for the reply,
> unfortunately I depend from rpm, I need just rpm packages.

Why do you need RPM?

> So can you confirm the target rpm for uclibc is not building?
> Thanks again,
> Giuseppe
>
> 2012/5/31 Khem Raj <raj.khem@gmail.com <mailto:raj.khem@gmail.com>>
>
>     On Thu, May 31, 2012 at 5:35 AM, Giuseppe Condorelli
>     <giuseppe.condorelli@gmail.com <mailto:giuseppe.condorelli@gmail.com>> wrote:
>     >  Is there some difference for uclibc? Please let me know.
>
>     opkg works well with uclibc based systems. Those functions are not
>     implemented in uclibc I am sure it can be fixed
>     by linking in other libs or may be creating one. However if you are
>     not bound to rpm then I would suggest to use opkg
>
>     in your local.conf set it
>
>     PACKAGE_CLASSES = "package_ipk"

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: target rpm build failure

[Giuseppe Condorelli]

[-- Attachment #1: Type: text/plain, Size: 2128 bytes --]

because the current distribution I manage (not oe based) is rpm based so in
my intention I want to furnish (for a while) both installtion methods: via
oe build system and via rpm (chrooted or similar).
And to do the second I need to have the possibility to access to the dbpath
oe build system manages during image cretion/installation.
Adding "package-management" to IMAGE_FEATURES I'll have this available. But
it includes also target rpm build (honestly I don't need it) that is
failing.

Have new suggestions?
Many thanks,
Giuseppe

2012/5/31 Gary Thomas <gary@mlbassoc.com>

> On 2012-05-31 07:57, Giuseppe Condorelli wrote:
>
>> Thanks for the reply,
>> unfortunately I depend from rpm, I need just rpm packages.
>>
>
> Why do you need RPM?
>
>  So can you confirm the target rpm for uclibc is not building?
>> Thanks again,
>> Giuseppe
>>
>> 2012/5/31 Khem Raj <raj.khem@gmail.com <mailto:raj.khem@gmail.com>>
>>
>>
>>    On Thu, May 31, 2012 at 5:35 AM, Giuseppe Condorelli
>>    <giuseppe.condorelli@gmail.com <mailto:giuseppe.condorelli@**gmail.com<giuseppe.condorelli@gmail.com>>>
>> wrote:
>>    >  Is there some difference for uclibc? Please let me know.
>>
>>    opkg works well with uclibc based systems. Those functions are not
>>    implemented in uclibc I am sure it can be fixed
>>    by linking in other libs or may be creating one. However if you are
>>    not bound to rpm then I would suggest to use opkg
>>
>>    in your local.conf set it
>>
>>    PACKAGE_CLASSES = "package_ipk"
>>
>
> --
> ------------------------------**------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> ------------------------------**------------------------------
>
>
> ______________________________**_________________
> Openembedded-core mailing list
> Openembedded-core@lists.**openembedded.org<Openembedded-core@lists.openembedded.org>
> http://lists.linuxtogo.org/**cgi-bin/mailman/listinfo/**openembedded-core<http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core>
>

[-- Attachment #2: Type: text/html, Size: 3465 bytes --]

Re: target rpm build failure

[Mark Hatle]

On 5/31/12 9:47 AM, Giuseppe Condorelli wrote:
> because the current distribution I manage (not oe based) is rpm based so in my
> intention I want to furnish (for a while) both installtion methods: via oe build
> system and via rpm (chrooted or similar).
> And to do the second I need to have the possibility to access to the dbpath oe
> build system manages during image cretion/installation.
> Adding "package-management" to IMAGE_FEATURES I'll have this available. But it
> includes also target rpm build (honestly I don't need it) that is failing.
> Have new suggestions?

uclibc and glibc are incompatible with each other from a binary perspective. 
I've not seen anyone distribution an RPM based uclibc distribution before.  It's 
always been glibc based -- or some other package method on uclibc due to size 
and dependency requirements.

If you really need rpm (on the target) with uclibc, you'll have to go through 
RPM and all of it's dependencies and patch them for uclibc.  I'm happy to review 
the patches, and I don't see why they wouldn't be accepted into OE-core... but 
it wasn't the expectation when RPM functionality was added and tested.  (ipkg 
was expected to be used with uclibc, or no package manager on the target.)

--Mark

> Many thanks,
> Giuseppe
>
> 2012/5/31 Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com>>
>
>     On 2012-05-31 07:57, Giuseppe Condorelli wrote:
>
>         Thanks for the reply,
>         unfortunately I depend from rpm, I need just rpm packages.
>
>
>     Why do you need RPM?
>
>         So can you confirm the target rpm for uclibc is not building?
>         Thanks again,
>         Giuseppe
>
>         2012/5/31 Khem Raj <raj.khem@gmail.com <mailto:raj.khem@gmail.com>
>         <mailto:raj.khem@gmail.com <mailto:raj.khem@gmail.com>>>
>
>
>         On Thu, May 31, 2012 at 5:35 AM, Giuseppe Condorelli
>         <giuseppe.condorelli@gmail.com <mailto:giuseppe.condorelli@gmail.com>
>         <mailto:giuseppe.condorelli@__gmail.com
>         <mailto:giuseppe.condorelli@gmail.com>>> wrote:
>          > Is there some difference for uclibc? Please let me know.
>
>         opkg works well with uclibc based systems. Those functions are not
>         implemented in uclibc I am sure it can be fixed
>         by linking in other libs or may be creating one. However if you are
>         not bound to rpm then I would suggest to use opkg
>
>         in your local.conf set it
>
>         PACKAGE_CLASSES = "package_ipk"
>
>
>     --
>     ------------------------------__------------------------------
>     Gary Thomas | Consulting for the
>     MLB Associates | Embedded world
>     ------------------------------__------------------------------
>
>
>     _________________________________________________
>     Openembedded-core mailing list
>     Openembedded-core@lists.__openembedded.org
>     <mailto:Openembedded-core@lists.openembedded.org>
>     http://lists.linuxtogo.org/__cgi-bin/mailman/listinfo/__openembedded-core
>     <http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core>
>
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Re: target rpm build failure

[Khem Raj]

On Thu, May 31, 2012 at 7:47 AM, Giuseppe Condorelli
<giuseppe.condorelli@gmail.com> wrote:
> Have new suggestions?

I found a bit of time and fixed rpm compilation on uclibc. Its only
compiling though I don't know if it will run on target. Try it out.
The patch is here

http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/misc&id=3b7ab8bbaca0c7ce122e897a11370dd215b0eddd

This should get you going. Please test it out and I would prefer if you can
also try it out on target and see if it really runs too.

-Khem

Re: target rpm build failure

[Giuseppe Condorelli]

[-- Attachment #1: Type: text/plain, Size: 1433 bytes --]

Many thanks Khem,

I've applied your patches to my local repository.
Unfortunately the uclibc setup I'm using doesn't provide support for
mcheck, so I'm falling in the same error.
However I have in mind also to build the glibc version of the whole image
and so here I will haven't problem building rpm.

But regarding glibc support I can see there is eglibc support and not glibc.
I'm not deep informed about differencies, in oe-classis I had glibc and in
oe-core it seems not supported.
Please can you make light to this point?
I need glibc also, how can I obtain it?

Best Regards,
Giuseppe

2012/6/1 Khem Raj <raj.khem@gmail.com>

> On Thu, May 31, 2012 at 7:47 AM, Giuseppe Condorelli
> <giuseppe.condorelli@gmail.com> wrote:
> > Have new suggestions?
>
> I found a bit of time and fixed rpm compilation on uclibc. Its only
> compiling though I don't know if it will run on target. Try it out.
> The patch is here
>
>
> http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/misc&id=3b7ab8bbaca0c7ce122e897a11370dd215b0eddd
>
> This should get you going. Please test it out and I would prefer if you can
> also try it out on target and see if it really runs too.
>
> -Khem
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>

[-- Attachment #2: Type: text/html, Size: 2412 bytes --]

Re: target rpm build failure

[Khem Raj]

On Fri, Jun 1, 2012 at 7:07 AM, Giuseppe Condorelli
<giuseppe.condorelli@gmail.com> wrote:
> Many thanks Khem,
>
> I've applied your patches to my local repository.
> Unfortunately the uclibc setup I'm using doesn't provide support for mcheck,
> so I'm falling in the same error.

hmm strange. Are you using OE-Core provided uclibc or something else ?
I could compile rpm successfully after I used the patch
http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/misc&id=44ecbebf17d18471becaccd37733e6b0e806c80d

> However I have in mind also to build the glibc version of the whole image
> and so here I will haven't problem building rpm.
>
> But regarding glibc support I can see there is eglibc support and not glibc.
> I'm not deep informed about differencies, in oe-classis I had glibc and in
> oe-core it seems not supported.
> Please can you make light to this point?
> I need glibc also, how can I obtain it?

well there are no differences as far as ABI is concerned. eglibc has
additional bit to help cross building
and testing rest it is glibc only. You should be fine using eglibc
version provided by OE-Core and it should interoperate well
with glibc based system

>
> Best Regards,
> Giuseppe
>
> 2012/6/1 Khem Raj <raj.khem@gmail.com>
>>
>> On Thu, May 31, 2012 at 7:47 AM, Giuseppe Condorelli
>> <giuseppe.condorelli@gmail.com> wrote:
>> > Have new suggestions?
>>
>> I found a bit of time and fixed rpm compilation on uclibc. Its only
>> compiling though I don't know if it will run on target. Try it out.
>> The patch is here
>>
>>
>> http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/misc&id=3b7ab8bbaca0c7ce122e897a11370dd215b0eddd
>>
>> This should get you going. Please test it out and I would prefer if you
>> can
>> also try it out on target and see if it really runs too.
>>
>> -Khem
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>

Re: target rpm build failure

[Giuseppe Condorelli]

[-- Attachment #1: Type: text/plain, Size: 2909 bytes --]

Hi Khem,
2012/6/1 Khem Raj <raj.khem@gmail.com>

> On Fri, Jun 1, 2012 at 7:07 AM, Giuseppe Condorelli
> <giuseppe.condorelli@gmail.com> wrote:
> > Many thanks Khem,
> >
> > I've applied your patches to my local repository.
> > Unfortunately the uclibc setup I'm using doesn't provide support for
> mcheck,
> > so I'm falling in the same error.
>
> hmm strange. Are you using OE-Core provided uclibc or something else ?
> I could compile rpm successfully after I used the patch
>
> http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/misc&id=44ecbebf17d18471becaccd37733e6b0e806c80d
>
> No I don't, I'm using an own uclibc included as new recipe in the meta
layer I've created for my scope.
I'll have to extend it supporting mcheck.


> > However I have in mind also to build the glibc version of the whole image
> > and so here I will haven't problem building rpm.
> >
> > But regarding glibc support I can see there is eglibc support and not
> glibc.
> > I'm not deep informed about differencies, in oe-classis I had glibc and
> in
> > oe-core it seems not supported.
> > Please can you make light to this point?
> > I need glibc also, how can I obtain it?
>
> well there are no differences as far as ABI is concerned. eglibc has
> additional bit to help cross building
> and testing rest it is glibc only. You should be fine using eglibc
> version provided by OE-Core and it should interoperate well
> with glibc based system
>
>
That's great.

Cheers,
Giuseppe

>
>
>
> > Best Regards,
> > Giuseppe
> >
> > 2012/6/1 Khem Raj <raj.khem@gmail.com>
> >>
> >> On Thu, May 31, 2012 at 7:47 AM, Giuseppe Condorelli
> >> <giuseppe.condorelli@gmail.com> wrote:
> >> > Have new suggestions?
> >>
> >> I found a bit of time and fixed rpm compilation on uclibc. Its only
> >> compiling though I don't know if it will run on target. Try it out.
> >> The patch is here
> >>
> >>
> >>
> http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/misc&id=3b7ab8bbaca0c7ce122e897a11370dd215b0eddd
> >>
> >> This should get you going. Please test it out and I would prefer if you
> >> can
> >> also try it out on target and see if it really runs too.
> >>
> >> -Khem
> >>
> >> _______________________________________________
> >> Openembedded-core mailing list
> >> Openembedded-core@lists.openembedded.org
> >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
> >
> >
> >
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
> >
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>

[-- Attachment #2: Type: text/html, Size: 5528 bytes --]

Re: target rpm build failure

[Giuseppe Condorelli]

[-- Attachment #1: Type: text/plain, Size: 3722 bytes --]

Hi Khem,

how the site_config directory interacts in the uclibc build?
I mean, although it is available in the recipe-core/uclibc directory I
cannot see any reference to siteconfig in logs.
Also the uclibc recipe declares a prepend function for siteconfig_gencache,
so I can suppose
we want to use it. But how?
Currently I'm not understanding why the target rpm package is building in
your environment and failing in mine.
Maybe this is due to the wrong (incomplete) build of uclibc? I can see
reference to mtrace and mcheck.h in the
files contained in the site_config directory.

Please let me know.
Best Regards,
Giuseppe
2012/6/1 Giuseppe Condorelli <giuseppe.condorelli@gmail.com>

> Hi Khem,
> 2012/6/1 Khem Raj <raj.khem@gmail.com>
>
>> On Fri, Jun 1, 2012 at 7:07 AM, Giuseppe Condorelli
>> <giuseppe.condorelli@gmail.com> wrote:
>> > Many thanks Khem,
>> >
>> > I've applied your patches to my local repository.
>> > Unfortunately the uclibc setup I'm using doesn't provide support for
>> mcheck,
>> > so I'm falling in the same error.
>>
>> hmm strange. Are you using OE-Core provided uclibc or something else ?
>> I could compile rpm successfully after I used the patch
>>
>> http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/misc&id=44ecbebf17d18471becaccd37733e6b0e806c80d
>>
>> No I don't, I'm using an own uclibc included as new recipe in the meta
> layer I've created for my scope.
> I'll have to extend it supporting mcheck.
>
>
>> > However I have in mind also to build the glibc version of the whole
>> image
>> > and so here I will haven't problem building rpm.
>> >
>> > But regarding glibc support I can see there is eglibc support and not
>> glibc.
>> > I'm not deep informed about differencies, in oe-classis I had glibc and
>> in
>> > oe-core it seems not supported.
>> > Please can you make light to this point?
>> > I need glibc also, how can I obtain it?
>>
>> well there are no differences as far as ABI is concerned. eglibc has
>> additional bit to help cross building
>> and testing rest it is glibc only. You should be fine using eglibc
>> version provided by OE-Core and it should interoperate well
>> with glibc based system
>>
>>
> That's great.
>
> Cheers,
> Giuseppe
>
>>
>>
>  >
>> > Best Regards,
>> > Giuseppe
>> >
>> > 2012/6/1 Khem Raj <raj.khem@gmail.com>
>> >>
>> >> On Thu, May 31, 2012 at 7:47 AM, Giuseppe Condorelli
>> >> <giuseppe.condorelli@gmail.com> wrote:
>> >> > Have new suggestions?
>> >>
>> >> I found a bit of time and fixed rpm compilation on uclibc. Its only
>> >> compiling though I don't know if it will run on target. Try it out.
>> >> The patch is here
>> >>
>> >>
>> >>
>> http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/misc&id=3b7ab8bbaca0c7ce122e897a11370dd215b0eddd
>> >>
>> >> This should get you going. Please test it out and I would prefer if you
>> >> can
>> >> also try it out on target and see if it really runs too.
>> >>
>> >> -Khem
>> >>
>> >> _______________________________________________
>> >> Openembedded-core mailing list
>> >> Openembedded-core@lists.openembedded.org
>> >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>> >
>> >
>> >
>> > _______________________________________________
>> > Openembedded-core mailing list
>> > Openembedded-core@lists.openembedded.org
>> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>> >
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>
>

[-- Attachment #2: Type: text/html, Size: 6747 bytes --]