AW: Issue with tar (Busybox 1.20.2): unknown file type

[Rob Landley]

On 06/13/2013 04:57:36 AM, piquemal michel wrote:
> Thanks a lot Dietmar for this clear explanation: looking at the code,  
> I was
> also suspecting something around stat.
> Actually du seems to have same problem: not traversing directories...  
> (while
> not signaling problems)
> 
> I guess I'm hit by a toolchain discrepancy: I build with recent  
> Aboriginal
> prebuilt images (uClibc  0.9.33.2, etc) while my target system is on  
> much older
> uClibc 0.9.28...

 From 2005? I'm surprised it didn't segfault immediately.

uClibc doesn't really provide a stable API between releases. If you  
don't want to deply the C libraries from the build environment, static  
linking is your friend...

> I've been lucky with apps I built so far, but it seems over with  
> tar...at least:(
> 
> I guess I will have to build my own Aboriginal image or be lucky  
> enough to find
> an older version that matches uClibc version...

 From 2005.  Hmmm... That pretty much predates the current generation  
of aboriginal linux.

If you're using 32 bit x86, I have a craptacularly ancient version at
http://landley.net/aboriginal/old/downloads/devel-uml that's a user  
mode linux executable running a development environment that's got  
uClibc 0.9.28. And gcc 4.0.2 and busybox 1.0.0-pre1 because that's what  
was available at the time. (That's actually from the previous  
incarnation of aboriginal linux, before I relaunched it based on qemu  
instead of uml and started targeting non-x86 platforms.) And even then  
there's no guarantee that the uClibc .config matches the one on the  
system you're deploying to, so you can _still_ have ABI skew.

I repeat: "static linking is your friend". :)

Rob