From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: tar 1.33 symlinks : Cannot change mode to...
Date: Tue, 12 Jan 2021 19:03:07 +0100 [thread overview]
Message-ID: <87bldu119g.fsf@Rainer.invalid> (raw)
In-Reply-To: <3a435fba-bdd2-535d-2161-f2fb75e2a4af@cornell.edu> (Ken Brown via Cygwin's message of "Tue, 12 Jan 2021 11:55:10 -0500")
Ken Brown via Cygwin writes:
[…]
> I don't see how that could be expected to work, since several members
> of struct __stat32 have different sizes than the corresponding members
> of struct stat. I wonder if it worked by accident in the past, but
> the problem is just showing up with newer gcc because of changes in
> how it pads the two structs?
I've just rebuilt tar-1.32 with gcc10 and see this error there too now.
I guess your finding saves me the bother of rolling back binutils and
gcc…
> Corinna, can you shed some light on this?
That'd be highly appreciated.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada
next prev parent reply other threads:[~2021-01-12 18:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 19:57 Morgan King
2021-01-11 23:50 ` Ken Brown
2021-01-12 8:18 ` ASSI
2021-01-12 10:32 ` Marco Atzeri
2021-01-12 16:55 ` Ken Brown
2021-01-12 17:15 ` Corinna Vinschen
2021-01-12 17:49 ` Ken Brown
2021-01-12 18:16 ` Corinna Vinschen
2021-01-12 18:03 ` Achim Gratz [this message]
2021-01-30 14:58 ` Michael Soegtrop
2021-01-30 15:11 ` Marco Atzeri
2021-01-30 15:36 ` Michael Soegtrop
2021-01-30 16:57 ` Michael Soegtrop
2021-01-13 16:52 ` Ken Brown
2021-01-13 19:02 ` Corinna Vinschen
2021-01-13 21:07 ` Morgan King
2021-01-13 21:12 ` Ken Brown
2021-04-01 21:23 ` Vincent Rivière
-- strict thread matches above, loose matches on Subject: below --
2021-01-10 13:50 [ANNOUNCEMENT] Updated: tar-1.33-3 Achim Gratz
2021-01-11 15:27 ` tar 1.33 symlinks : Cannot change mode to Vincent Rivière
2021-01-11 17:54 ` Achim Gratz
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=87bldu119g.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).