From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] boost 1.60.0-1
Date: Sat, 03 Sep 2016 09:39:00 -0000 [thread overview]
Message-ID: <db7bbc3c-b79a-dde3-6376-b59eb7137934@tiscali.co.uk> (raw)
In-Reply-To: <5acf2494-0351-bba7-7672-662c2fe10767@cygwin.com>
On 02/09/16 23:48, Yaakov Selkowitz wrote:
> On 2016-09-02 14:38, Frédéric Bron wrote:
>> Could you tell me where I can find the patches applied to boost and
>> the commands that you use? I would like to compile boost 1.61.0 with
>> g++-6.[12].0 that I have just compiled. But I get errors when I build
>> boost and do not known how to fix them.
>
> Every package has a source package containing the upstream sources,
> .cygport file, and patches used to build the binaries. You can
> actually install the source package with the setup installer, in which
> case they will be unpacked under /usr/src.
>
> Or, wrt my packages (and that's it atm) the .cygport and patches are
> also online:
>
> https://github.com/cygwinports/boost
Could / should other package maintainers be using this repo?
Dave.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-09-03 9:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 9:28 Yaakov Selkowitz
2016-09-02 19:39 ` Frédéric Bron
2016-09-02 22:49 ` Yaakov Selkowitz
2016-09-03 9:39 ` David Stacey [this message]
2016-09-03 14:24 ` Marco Atzeri
2016-09-03 15:38 ` Corinna Vinschen
2016-09-03 16:26 ` Marco Atzeri
2016-09-03 22:43 ` David Stacey
2016-09-04 9:08 ` Frédéric Bron
2016-09-04 9:23 ` Marco Atzeri
2016-09-04 19:42 ` Frédéric Bron
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=db7bbc3c-b79a-dde3-6376-b59eb7137934@tiscali.co.uk \
--to=drstacey@tiscali.co.uk \
--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).