Kenneth Hadley wrote:

> As yet ive seen now one even look into this issue except me....and ive only
> a few clues to go by..
> My guess is tar has a bug in either LRP 2.9.8 or Eiger ...im not sure
> which...

Probably so.  Could you detail what version of busybox (tar) is on both
of these distributions?  Give the output from:

# busybox

> But the end result is packages created under Eiger do not sometimes
> uncompress properly under LRP 2.9.8 and packages made on LRP 2.9.8 do not
> uncompress properly on Eiger (seti from lrp.gibbsoft.com is a example)

Sounds logical, given that there are almost certainly different versions
of busybox involved.

> Though strangley enough packages made on either LRP 2.9.4 or Eiger work just
> fine on one another...

Not strange at all.  Eiger was derived from 2.9.4; if busybox was never
changed, then it will work.

> This is also what stoped me dead in my tracks on creating a LRP2.9.8 image
> of PPPoE....my package does not uncompress properly...

It would be nice to see some tests:

* Compiled under 2.9.8, does it extract under Eiger?
* Compiled under Eiger, does it extract under 2.9.8?
* Compiled under 2.9.8, does it extract with GNU tar?
* Compiled under Eiger, does it extract with GNU tar?

> I do have a seti303.lrp package available that works on Eiger....email in
> private if you wish a copy...  ( and yes..it uncompresses fine on LRP2.9.4
> and Eiger but not LRP 2.9.8...or did...i'll confirm this tonight)

I seem to recall some tar bugs in busybox, but they should all be fixed
by now.

_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to