Mailing List Archive: Gentoo: Embedded

tar-1.26 not unpacking archives with symlinks?

Index | Next | Previous | View Threaded

lists at wildgooses

Feb 29, 2012, 9:33 AM

Post #1 of 3 (450 views)
Permalink

tar-1.26 not unpacking archives with symlinks?

Hi, I'm hitting an error when trying to unpack archives with the
recently unmasked tar-1.26. Basically any symlinks in the archive
trigger an "unknown file" error. This prevents me using emerge -k
amongst other things

I only see this on uclibc-0.9.33 based system, not on the build host
which uses glibc amd64

Can anyone else repro this and shed any light on what the problem might
be? Problem in tar or uclibc?

Thanks

Ed W

vapier at gentoo

Apr 1, 2012, 9:38 PM

Post #2 of 3 (405 views)
Permalink

Re: tar-1.26 not unpacking archives with symlinks? [In reply to]

On Wednesday 29 February 2012 12:33:02 Ed W wrote:
> Hi, I'm hitting an error when trying to unpack archives with the
> recently unmasked tar-1.26. Basically any symlinks in the archive
> trigger an "unknown file" error. This prevents me using emerge -k
> amongst other things
>
> I only see this on uclibc-0.9.33 based system, not on the build host
> which uses glibc amd64
>
> Can anyone else repro this and shed any light on what the problem might
> be? Problem in tar or uclibc?

fchmodat() is a syscall that takes 3 args. uClibc was providing a stub that
treated it as 4. i fixed things up, so if you want to try with the fix i just
committed, that'd be nice ...
-mike

Attachments:

signature.asc (0.82 KB)

lists at wildgooses

Apr 3, 2012, 6:35 AM

Post #3 of 3 (398 views)
Permalink

Re: tar-1.26 not unpacking archives with symlinks? [In reply to]

On 02/04/2012 05:38, Mike Frysinger wrote:
> On Wednesday 29 February 2012 12:33:02 Ed W wrote:
>> Hi, I'm hitting an error when trying to unpack archives with the
>> recently unmasked tar-1.26. Basically any symlinks in the archive
>> trigger an "unknown file" error. This prevents me using emerge -k
>> amongst other things
>>
>> I only see this on uclibc-0.9.33 based system, not on the build host
>> which uses glibc amd64
>>
>> Can anyone else repro this and shed any light on what the problem might
>> be? Problem in tar or uclibc?
> fchmodat() is a syscall that takes 3 args. uClibc was providing a stub that
> treated it as 4. i fixed things up, so if you want to try with the fix i just
> committed, that'd be nice ...
> -mike

Excellent - many thanks

Out of the country at present - will verify on my return

Again many thanks

Ed W

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads