* lconfig-native is not endian safe
@ 2011-03-30 14:47 Richard Purdie
2011-03-30 15:43 ` Mark Hatle
0 siblings, 1 reply; 9+ messages in thread
From: Richard Purdie @ 2011-03-30 14:47 UTC (permalink / raw)
To: poky@yoctoproject.org, openembedded-core
Hi,
Poky has had a ldconfig-native recipe in for a while. Back in the times
our RPATHS were totally broken adding in an ld.so.cache was useful. In
modern times I'm having trouble working out when this would be useful on
a standard system as libraries are pretty much always in one of the two
default search locations.
ldconfig-native is 32/64 bit safe. I've just been looking at PPC and it
is certainly not endian safe though. The endianess of the target system
need to match that of the build system for it to work. It wouldn't be
much work to make it endian safe though although the codebase will
diverge further from that in (e)glibc though.
Short term we need to disable it at least for ppc, longer term what
should we do?
Cheers,
Richard
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: lconfig-native is not endian safe
2011-03-30 14:47 lconfig-native is not endian safe Richard Purdie
@ 2011-03-30 15:43 ` Mark Hatle
2011-03-31 1:59 ` Kamble, Nitin A
0 siblings, 1 reply; 9+ messages in thread
From: Mark Hatle @ 2011-03-30 15:43 UTC (permalink / raw)
To: openembedded-core
On 3/30/11 9:47 AM, Richard Purdie wrote:
> Hi,
>
> Poky has had a ldconfig-native recipe in for a while. Back in the times
> our RPATHS were totally broken adding in an ld.so.cache was useful. In
> modern times I'm having trouble working out when this would be useful on
> a standard system as libraries are pretty much always in one of the two
> default search locations.
>
> ldconfig-native is 32/64 bit safe. I've just been looking at PPC and it
> is certainly not endian safe though. The endianess of the target system
> need to match that of the build system for it to work. It wouldn't be
> much work to make it endian safe though although the codebase will
> diverge further from that in (e)glibc though.
>
> Short term we need to disable it at least for ppc, longer term what
> should we do?
On ARM, are the structures packed in the same way as the target system?
I know I prefer to NOT use ldconfig in the systems I design, but I understand
why people want it.
I suggest we disable it on PPC for now, and work on updating endian support,
(packing if necessary) and make sure that it supports the latest ldconfig
features of being able to use referenced directories and such.
--Mark
> Cheers,
>
> Richard
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: lconfig-native is not endian safe
2011-03-30 15:43 ` Mark Hatle
@ 2011-03-31 1:59 ` Kamble, Nitin A
2011-03-31 2:02 ` Kamble, Nitin A
0 siblings, 1 reply; 9+ messages in thread
From: Kamble, Nitin A @ 2011-03-31 1:59 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
I have updated the ldconfig-native to match the version of eglibc 2.12.1, but that still does not solve the endienness problem of cross ppc.
Thanks,
Nitin
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> Mark Hatle
> Sent: Wednesday, March 30, 2011 8:44 AM
> To: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] lconfig-native is not endian safe
>
> On 3/30/11 9:47 AM, Richard Purdie wrote:
> > Hi,
> >
> > Poky has had a ldconfig-native recipe in for a while. Back in the
> times
> > our RPATHS were totally broken adding in an ld.so.cache was useful.
> In
> > modern times I'm having trouble working out when this would be useful
> on
> > a standard system as libraries are pretty much always in one of the
> two
> > default search locations.
> >
> > ldconfig-native is 32/64 bit safe. I've just been looking at PPC and
> it
> > is certainly not endian safe though. The endianess of the target
> system
> > need to match that of the build system for it to work. It wouldn't be
> > much work to make it endian safe though although the codebase will
> > diverge further from that in (e)glibc though.
> >
> > Short term we need to disable it at least for ppc, longer term what
> > should we do?
>
> On ARM, are the structures packed in the same way as the target system?
>
> I know I prefer to NOT use ldconfig in the systems I design, but I
> understand
> why people want it.
>
> I suggest we disable it on PPC for now, and work on updating endian
> support,
> (packing if necessary) and make sure that it supports the latest
> ldconfig
> features of being able to use referenced directories and such.
>
> --Mark
>
> > Cheers,
> >
> > Richard
> >
> >
> > _______________________________________________
> > 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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: lconfig-native is not endian safe
2011-03-31 1:59 ` Kamble, Nitin A
@ 2011-03-31 2:02 ` Kamble, Nitin A
2011-03-31 2:09 ` Kamble, Nitin A
0 siblings, 1 reply; 9+ messages in thread
From: Kamble, Nitin A @ 2011-03-31 2:02 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> Kamble, Nitin A
> Sent: Wednesday, March 30, 2011 7:00 PM
> To: Patches and discussions about the oe-core layer
> Subject: Re: [OE-core] lconfig-native is not endian safe
>
> I have updated the ldconfig-native to match the version of eglibc
> 2.12.1, but that still does not solve the endienness problem of cross
> ppc.
BTW ldconfig's endienness issue is also for mips & armeb.
>
> Thanks,
> Nitin
>
>
> > -----Original Message-----
> > From: openembedded-core-bounces@lists.openembedded.org
> > [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf
> Of
> > Mark Hatle
> > Sent: Wednesday, March 30, 2011 8:44 AM
> > To: openembedded-core@lists.openembedded.org
> > Subject: Re: [OE-core] lconfig-native is not endian safe
> >
> > On 3/30/11 9:47 AM, Richard Purdie wrote:
> > > Hi,
> > >
> > > Poky has had a ldconfig-native recipe in for a while. Back in the
> > times
> > > our RPATHS were totally broken adding in an ld.so.cache was useful.
> > In
> > > modern times I'm having trouble working out when this would be
> useful
> > on
> > > a standard system as libraries are pretty much always in one of the
> > two
> > > default search locations.
> > >
> > > ldconfig-native is 32/64 bit safe. I've just been looking at PPC
> and
> > it
> > > is certainly not endian safe though. The endianess of the target
> > system
> > > need to match that of the build system for it to work. It wouldn't
> be
> > > much work to make it endian safe though although the codebase will
> > > diverge further from that in (e)glibc though.
> > >
> > > Short term we need to disable it at least for ppc, longer term what
> > > should we do?
> >
> > On ARM, are the structures packed in the same way as the target
> system?
> >
> > I know I prefer to NOT use ldconfig in the systems I design, but I
> > understand
> > why people want it.
> >
> > I suggest we disable it on PPC for now, and work on updating endian
> > support,
> > (packing if necessary) and make sure that it supports the latest
> > ldconfig
> > features of being able to use referenced directories and such.
> >
> > --Mark
> >
> > > Cheers,
> > >
> > > Richard
> > >
> > >
> > > _______________________________________________
> > > 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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: lconfig-native is not endian safe
2011-03-31 2:02 ` Kamble, Nitin A
@ 2011-03-31 2:09 ` Kamble, Nitin A
2011-03-31 9:02 ` Hatle, Mark
2011-04-05 2:15 ` lconfig-native " Khem Raj
0 siblings, 2 replies; 9+ messages in thread
From: Kamble, Nitin A @ 2011-03-31 2:09 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
> > I have updated the ldconfig-native to match the version of eglibc
> > 2.12.1, but that still does not solve the endienness problem of cross
> > ppc.
>
> BTW ldconfig's endienness issue is also for mips & armeb.
Another solution I was thinking of was:
Use the target ldconfig in qemu shell. (like the glibc locales were generated earlier).
Does it make sense to do it that way, or is it better to just not generate the ld.so.cache?
>
> >
> > Thanks,
> > Nitin
> >
> >
> > > -----Original Message-----
> > > From: openembedded-core-bounces@lists.openembedded.org
> > > [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf
> > Of
> > > Mark Hatle
> > > Sent: Wednesday, March 30, 2011 8:44 AM
> > > To: openembedded-core@lists.openembedded.org
> > > Subject: Re: [OE-core] lconfig-native is not endian safe
> > >
> > > On 3/30/11 9:47 AM, Richard Purdie wrote:
> > > > Hi,
> > > >
> > > > Poky has had a ldconfig-native recipe in for a while. Back in the
> > > times
> > > > our RPATHS were totally broken adding in an ld.so.cache was
> useful.
> > > In
> > > > modern times I'm having trouble working out when this would be
> > useful
> > > on
> > > > a standard system as libraries are pretty much always in one of
> the
> > > two
> > > > default search locations.
> > > >
> > > > ldconfig-native is 32/64 bit safe. I've just been looking at PPC
> > and
> > > it
> > > > is certainly not endian safe though. The endianess of the target
> > > system
> > > > need to match that of the build system for it to work. It
> wouldn't
> > be
> > > > much work to make it endian safe though although the codebase
> will
> > > > diverge further from that in (e)glibc though.
> > > >
> > > > Short term we need to disable it at least for ppc, longer term
> what
> > > > should we do?
> > >
> > > On ARM, are the structures packed in the same way as the target
> > system?
> > >
> > > I know I prefer to NOT use ldconfig in the systems I design, but I
> > > understand
> > > why people want it.
> > >
> > > I suggest we disable it on PPC for now, and work on updating endian
> > > support,
> > > (packing if necessary) and make sure that it supports the latest
> > > ldconfig
> > > features of being able to use referenced directories and such.
> > >
> > > --Mark
> > >
> > > > Cheers,
> > > >
> > > > Richard
> > > >
> > > >
> > > > _______________________________________________
> > > > 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
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: lconfig-native is not endian safe
2011-03-31 2:09 ` Kamble, Nitin A
@ 2011-03-31 9:02 ` Hatle, Mark
2011-03-31 10:40 ` Richard Purdie
2011-04-05 2:15 ` lconfig-native " Khem Raj
1 sibling, 1 reply; 9+ messages in thread
From: Hatle, Mark @ 2011-03-31 9:02 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
Cc: Patches and discussions about the oe-core layer
My opinion is to avoid it vs run in a qemu shell. I really don't like being forced to have qemu to run a build of any type.
On Mar 30, 2011, at 9:15 PM, "Kamble, Nitin A" <nitin.a.kamble@intel.com> wrote:
>
>
>>> I have updated the ldconfig-native to match the version of eglibc
>>> 2.12.1, but that still does not solve the endienness problem of cross
>>> ppc.
>>
>> BTW ldconfig's endienness issue is also for mips & armeb.
>
> Another solution I was thinking of was:
> Use the target ldconfig in qemu shell. (like the glibc locales were generated earlier).
> Does it make sense to do it that way, or is it better to just not generate the ld.so.cache?
>
>
>>
>>>
>>> Thanks,
>>> Nitin
>>>
>>>
>>>> -----Original Message-----
>>>> From: openembedded-core-bounces@lists.openembedded.org
>>>> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf
>>> Of
>>>> Mark Hatle
>>>> Sent: Wednesday, March 30, 2011 8:44 AM
>>>> To: openembedded-core@lists.openembedded.org
>>>> Subject: Re: [OE-core] lconfig-native is not endian safe
>>>>
>>>> On 3/30/11 9:47 AM, Richard Purdie wrote:
>>>>> Hi,
>>>>>
>>>>> Poky has had a ldconfig-native recipe in for a while. Back in the
>>>> times
>>>>> our RPATHS were totally broken adding in an ld.so.cache was
>> useful.
>>>> In
>>>>> modern times I'm having trouble working out when this would be
>>> useful
>>>> on
>>>>> a standard system as libraries are pretty much always in one of
>> the
>>>> two
>>>>> default search locations.
>>>>>
>>>>> ldconfig-native is 32/64 bit safe. I've just been looking at PPC
>>> and
>>>> it
>>>>> is certainly not endian safe though. The endianess of the target
>>>> system
>>>>> need to match that of the build system for it to work. It
>> wouldn't
>>> be
>>>>> much work to make it endian safe though although the codebase
>> will
>>>>> diverge further from that in (e)glibc though.
>>>>>
>>>>> Short term we need to disable it at least for ppc, longer term
>> what
>>>>> should we do?
>>>>
>>>> On ARM, are the structures packed in the same way as the target
>>> system?
>>>>
>>>> I know I prefer to NOT use ldconfig in the systems I design, but I
>>>> understand
>>>> why people want it.
>>>>
>>>> I suggest we disable it on PPC for now, and work on updating endian
>>>> support,
>>>> (packing if necessary) and make sure that it supports the latest
>>>> ldconfig
>>>> features of being able to use referenced directories and such.
>>>>
>>>> --Mark
>>>>
>>>>> Cheers,
>>>>>
>>>>> Richard
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>
>> _______________________________________________
>> 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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: lconfig-native is not endian safe
2011-03-31 9:02 ` Hatle, Mark
@ 2011-03-31 10:40 ` Richard Purdie
2011-03-31 17:27 ` ldconfig-native " Kamble, Nitin A
0 siblings, 1 reply; 9+ messages in thread
From: Richard Purdie @ 2011-03-31 10:40 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On Thu, 2011-03-31 at 09:02 +0000, Hatle, Mark wrote:
> My opinion is to avoid it vs run in a qemu shell. I really don't like
> being forced to have qemu to run a build of any type.
Agreed, I think we can avoid this.
For reference, I have half he endian problem resolved with:
http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/gcc-sharedwork&id=0711c7c065c6e1caa04f452069d08a056c3caabe
which handles reading in the data from the elf files in an endian safe
way. Someone needs to go through and change the dl cache file handling
code to be endian safe though, then compare the result with a file
generated on a target device.
Cheers,
Richard
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: ldconfig-native is not endian safe
2011-03-31 10:40 ` Richard Purdie
@ 2011-03-31 17:27 ` Kamble, Nitin A
0 siblings, 0 replies; 9+ messages in thread
From: Kamble, Nitin A @ 2011-03-31 17:27 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> Richard Purdie
> Sent: Thursday, March 31, 2011 3:41 AM
> To: Patches and discussions about the oe-core layer
> Subject: Re: [OE-core] lconfig-native is not endian safe
>
> On Thu, 2011-03-31 at 09:02 +0000, Hatle, Mark wrote:
> > My opinion is to avoid it vs run in a qemu shell. I really don't
> like
> > being forced to have qemu to run a build of any type.
>
> Agreed, I think we can avoid this.
>
> For reference, I have half he endian problem resolved with:
>
> http://git.yoctoproject.org/cgit.cgi/poky-
> contrib/commit/?h=rpurdie/gcc-
> sharedwork&id=0711c7c065c6e1caa04f452069d08a056c3caabe
>
> which handles reading in the data from the elf files in an endian safe
> way. Someone needs to go through and change the dl cache file handling
> code to be endian safe though, then compare the result with a file
> generated on a target device.
>
> Cheers,
>
> Richard
>
Richard,
I upgraded ldconfig-native to 2.12.1 ( our eglibc version), I rebased your patch to it, and will implement rest of the endianness handling code.
Thanks,
Nitin
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: lconfig-native is not endian safe
2011-03-31 2:09 ` Kamble, Nitin A
2011-03-31 9:02 ` Hatle, Mark
@ 2011-04-05 2:15 ` Khem Raj
1 sibling, 0 replies; 9+ messages in thread
From: Khem Raj @ 2011-04-05 2:15 UTC (permalink / raw)
To: openembedded-core
On 3/30/2011 7:09 PM, Kamble, Nitin A wrote:
>
>
>>> I have updated the ldconfig-native to match the version of eglibc
>>> 2.12.1, but that still does not solve the endienness problem of cross
>>> ppc.
>>
>> BTW ldconfig's endienness issue is also for mips& armeb.
>
> Another solution I was thinking of was:
> Use the target ldconfig in qemu shell. (like the glibc locales were generated earlier).
> Does it make sense to do it that way, or is it better to just not generate the ld.so.cache?
>
hmm we got rid of qemu for locales for a reason :). Think of people who
do not build for qemu machines but real hardware now they have to build
qemu just for this.
>
>>
>>>
>>> Thanks,
>>> Nitin
>>>
>>>
>>>> -----Original Message-----
>>>> From: openembedded-core-bounces@lists.openembedded.org
>>>> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf
>>> Of
>>>> Mark Hatle
>>>> Sent: Wednesday, March 30, 2011 8:44 AM
>>>> To: openembedded-core@lists.openembedded.org
>>>> Subject: Re: [OE-core] lconfig-native is not endian safe
>>>>
>>>> On 3/30/11 9:47 AM, Richard Purdie wrote:
>>>>> Hi,
>>>>>
>>>>> Poky has had a ldconfig-native recipe in for a while. Back in the
>>>> times
>>>>> our RPATHS were totally broken adding in an ld.so.cache was
>> useful.
>>>> In
>>>>> modern times I'm having trouble working out when this would be
>>> useful
>>>> on
>>>>> a standard system as libraries are pretty much always in one of
>> the
>>>> two
>>>>> default search locations.
>>>>>
>>>>> ldconfig-native is 32/64 bit safe. I've just been looking at PPC
>>> and
>>>> it
>>>>> is certainly not endian safe though. The endianess of the target
>>>> system
>>>>> need to match that of the build system for it to work. It
>> wouldn't
>>> be
>>>>> much work to make it endian safe though although the codebase
>> will
>>>>> diverge further from that in (e)glibc though.
>>>>>
>>>>> Short term we need to disable it at least for ppc, longer term
>> what
>>>>> should we do?
>>>>
>>>> On ARM, are the structures packed in the same way as the target
>>> system?
>>>>
>>>> I know I prefer to NOT use ldconfig in the systems I design, but I
>>>> understand
>>>> why people want it.
>>>>
>>>> I suggest we disable it on PPC for now, and work on updating endian
>>>> support,
>>>> (packing if necessary) and make sure that it supports the latest
>>>> ldconfig
>>>> features of being able to use referenced directories and such.
>>>>
>>>> --Mark
>>>>
>>>>> Cheers,
>>>>>
>>>>> Richard
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>
>> _______________________________________________
>> 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
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2011-04-05 2:18 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-03-30 14:47 lconfig-native is not endian safe Richard Purdie
2011-03-30 15:43 ` Mark Hatle
2011-03-31 1:59 ` Kamble, Nitin A
2011-03-31 2:02 ` Kamble, Nitin A
2011-03-31 2:09 ` Kamble, Nitin A
2011-03-31 9:02 ` Hatle, Mark
2011-03-31 10:40 ` Richard Purdie
2011-03-31 17:27 ` ldconfig-native " Kamble, Nitin A
2011-04-05 2:15 ` lconfig-native " Khem Raj
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox