From: Joel Sherrill <joel@rtems.org>
To: Newlib <newlib@sourceware.org>, Chris Johns <chrisj@rtems.org>
Subject: Symlinks in Newlib break mingw host builds
Date: Mon, 10 Feb 2020 16:09:00 -0000 [thread overview]
Message-ID: <CAF9ehCW0Z1s9j3Sx5wqmix5--wBFgpgypkhZk8OmaW-uDMcSNw@mail.gmail.com> (raw)
Hi
The following patch in newlib adds links as part of the i386/x86_64 fenv
support. Windows does not have symlinks and it is emulated as copy.
This complicates a bsdtar extraction of source.
https://github.com/RTEMS/sourceware-mirror-newlib-
cygwin/commit/cfc4955234828881145a20987c8a0a3cd373585c
We tried to extract the tar file a second time, this has worked with
other tar files with symlinks however it does not work. We don't know why.
My current best idea is to replace all the symlinks in those libm
directories
with a short file that includes the file instead of symlinking to it.
Any other thoughts to eliminate the symlinks since they cause issues.
--joel
next reply other threads:[~2020-02-10 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 16:09 Joel Sherrill [this message]
2020-02-10 19:54 ` Keith Packard
2020-02-10 21:47 ` Jeff Johnston
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=CAF9ehCW0Z1s9j3Sx5wqmix5--wBFgpgypkhZk8OmaW-uDMcSNw@mail.gmail.com \
--to=joel@rtems.org \
--cc=chrisj@rtems.org \
--cc=newlib@sourceware.org \
/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).