From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Angelo Graziosi <angelo.g0@libero.it>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Failure unpacking Emacs master tarball source [MSYS2/MINGW64]
Date: Fri, 7 May 2021 18:40:08 +0200 [thread overview]
Message-ID: <CAArVCkRyeAqyzA75uz_o3UCinxfXSpaiNOhCVvE48LmHB1LF8g@mail.gmail.com> (raw)
In-Reply-To: <831raid8gy.fsf@gnu.org>
Am Fr., 7. Mai 2021 um 14:39 Uhr schrieb Eli Zaretskii <eliz@gnu.org>:
>
> > Date: Fri, 7 May 2021 14:27:28 +0200 (CEST)
> > From: Angelo Graziosi <angelo.g0@libero.it>
> >
> > With the last commit (3ad239e1bc1228407ae656440327a29e7373f977) I get:
> >
> > $ wget http://git.savannah.gnu.org/cgit/emacs.git/snapshot/emacs-master.tar.gz
> >
> > $ tar -xvof emacs-master.tar.gz
> > [...]
> > tar: emacs-master/test/src/emacs-resources/seccomp-filter.bpf: impossibile creare un collegamento simbolico a "../../../lib-src/seccomp-filter.bpf": No such file or directory
> > tar: emacs-master/test/src/emacs-resources/seccomp-filter-exec.bpf: impossibile creare un collegamento simbolico a "../../../lib-src/seccomp-filter-exec.bpf": No such file or directory
> > tar: Uscita con stato di fallimento in base agli errori precedenti
> >
> > This breaks my script with which I have built Emacs for years..
>
> Philipp, please don't place any symlinks in the Git repository, it's
> not portable enough. Why cannot the tests reference the *.bpf files
> explicitly?
It's just easier to use the ert-resource-file macro. But I've now
removed the symlinks with commit
a2842a11728336fc8110eedb5176ecfbe71bbc79.
next prev parent reply other threads:[~2021-05-07 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 12:27 Failure unpacking Emacs master tarball source [MSYS2/MINGW64] Angelo Graziosi
2021-05-07 12:38 ` Eli Zaretskii
2021-05-07 13:00 ` Angelo Graziosi
2021-05-07 16:40 ` Philipp Stephani [this message]
2021-05-08 6:31 ` Eli Zaretskii
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=CAArVCkRyeAqyzA75uz_o3UCinxfXSpaiNOhCVvE48LmHB1LF8g@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=angelo.g0@libero.it \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.