tar-1.26 not unpacking archives with symlinks?

Natanael Copa natanael.copa at gmail.com
Wed Mar 14 09:46:06 UTC 2012

(resending due to uclibc blocked the uncompressed config.log)

On Wed, Mar 14, 2012 at 3:44 AM, Mike Frysinger <vapier at gentoo.org> wrote:
> On Tuesday 13 March 2012 17:40:38 Natanael Copa wrote:
>> I have seen this too and it only happens when the symlink is extracted
>> before the file it points to.
>> To reproduce:
>>   touch myfile
>>   ln -s myfile mylink
>>   tar -cf testcase1.tar mylink myfile
> i vaguely recall seeing this before and the issue came down to tar not
> detecting the right features.  might want to compare the config.log output
> between glibc and uclibc to see how they differ.

I don't have an glibc box handy available. Attached is the config.log
when building with uclibc on 84_64.

Natanael Copa
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.log.bz2
Type: application/x-bzip2
Size: 38284 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/uclibc/attachments/20120314/14493e4a/attachment-0001.bz2>

More information about the uClibc mailing list