unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: more windows confusions
Date: Wed, 18 Oct 2017 00:43:42 +0200	[thread overview]
Message-ID: <87376h2y5d.fsf@qcore> (raw)
In-Reply-To: 87infdif14.fsf@russet.org.uk

phillip.lord@russet.org.uk (Phillip Lord) writes:

> I'm currently scripting the windows build and have hit a snag. My
> dependency list has two packages for which there do not appear to be
> source.
>
> The two in question are these:
>
> mingw-w64-gcc-libs

This is part of gcc (mingw-w64-gcc/PKGBUILD).

> mingw-w64-libwinpthread-git

This is mingw-w64-libwinpthreads-git/PKGBUILD

(note the extra `s').

> Both pretty generic and indirect dependencies of most of the Emacs
> libraries dependencies. I'm trying to get the source from here.
>
> https://github.com/Alexpux/MINGW-packages
>
> I'm guessing this is because of some obscurity about the way packaging
> works for MSYS2/MINGW. Any suggestions welcome.

The MSYS2 maintainer uploads the source of each binary package he
builds. See for instance:

https://sourceforge.net/projects/msys2/files/REPOS/MINGW/Sources/

If you download the source from there, you are guaranteed to obtain the
corresponding source code of the binary package available on the same
server.




      reply	other threads:[~2017-10-17 22:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17 22:29 more windows confusions Phillip Lord
2017-10-17 22:43 ` Óscar Fuentes [this message]

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87376h2y5d.fsf@qcore \
    --to=ofv@wanadoo.es \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).