mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "A. Wilcox" <awilfox@adelielinux.org>
To: musl@lists.openwall.com
Subject: Re: Possible issue around utime() and symlinks on at least MIPS64
Date: Wed, 18 Apr 2018 16:51:31 -0500	[thread overview]
Message-ID: <89968ffc-d4ae-93d1-0810-345ad03f2a53@adelielinux.org> (raw)
In-Reply-To: <20180418200014.GG3094@brightrain.aerifal.cx>


[-- Attachment #1.1: Type: text/plain, Size: 1894 bytes --]

On 04/18/18 15:00, Rich Felker wrote:
> On Thu, Jul 06, 2017 at 02:50:16PM +0100, Adam Hill wrote:
>> Hi,
>> 
>> Not carried out ANY investigation around this... unfortunately I
>> don't have any time atm. Could also have been mentioned already or
>> actually be a bug in tar itself etc. but I couldn't find anything
>> with my quick search. Just thought I'd mention it in case anyone
>> does feel inclined to investigate.
>> 
>> I compiled OpenWrt using pretty much default build settings for an
>> octeon chip... it uses musl-1.1.16. The only real change I made was
>> to use GNU tar rather than busybox. The resulting tar binary can't
>> fix the modification/access times on any extracted symbolic links,
>>  resulting in for example:
>> 
>> tar: usr/share/zoneinfo/Africa: Cannot utime: Invalid argument
>> 
>> I didn't have strace available so can't even be sure tar's using
>> utime()... just going by the error message alone.
>> 
>> I recompiled OpenWrt changing only the C library ( to GCC ) and the
>> resulting tar binary worked fine... so I can only *assume* it's
>> something to do with musl.
> 
> Did anyone ever get a chance to look further into this? It's been on 
> my todo for a long time, but without sufficient information to 
> reproduce I don't know where to begin. I spent about 20 minutes 
> looking at the musl and kernel code now and it does not seem likely 
> that this is mips64-specific.
> 
> Rich
> 

This really sounds like broken cross-compiling.  When we cross-compile
cp, it's unable to handle xattrs until it's re-compiled on native
hardware.  I'd suggest poking around at autoconf for GNU tar and seeing
what it is 'guessing' the environment is like, and perhaps overriding
some with ac_*={yes,no} on the configure line.

Best,
--arw

-- 
A. Wilcox (awilfox)
Project Lead, Adélie Linux
http://adelielinux.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-04-18 21:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 13:50 Adam Hill
2018-04-18 20:00 ` Rich Felker
2018-04-18 21:51   ` A. Wilcox [this message]
2018-04-18 22:37     ` Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=89968ffc-d4ae-93d1-0810-345ad03f2a53@adelielinux.org \
    --to=awilfox@adelielinux.org \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).