public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] boost 1.60.0-1
Date: Sun, 04 Sep 2016 09:23:00 -0000	[thread overview]
Message-ID: <a028d072-8a7d-bc77-f539-eaca2c799bda@gmail.com> (raw)
In-Reply-To: <CAPw2spiT1He_TFRuO=bwoVicr21T4nD3k19URJi3cRozQA94GA@mail.gmail.com>



On 04/09/2016 11:07, Frédéric Bron wrote:
> Hi Yaakov,
>
> Thanks for your message.
>
> I downloaded your files from cygwinports/boost and tried to apply the
> patches to boost 1.60.0 and got errors like this one:
>
> # the first one runs fine:
> $ patch -p1 --dry-run < ../cygport/fedora/boost-1.50.0-fix-non-utf8-files.patch
> checking file libs/units/example/autoprefixes.cpp
>
> # the second one gives this error:
> $ patch -p1 --dry-run < ../cygport/fedora/boost-1.58.0-pool.patch
> can't find file to patch at input line 5
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --------------------------
> |Index: boost/pool/pool.hpp
> |===================================================================
> |--- boost/pool/pool.hpp        (revision 78317)
> |+++ boost/pool/pool.hpp        (revision 78326)
> --------------------------
> File to patch:
>
> How do you deal with those errors? Do you just skip patches that do
> not work anymore?
>
> Thanks,
>
> Frédéric

try

   cygport boost.cygport prep

It will prepare the directory and applies all the patches in PATCH_URI
If one of the patch fails the build stops, so I assume all should
apply.

Regards
Marco





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

  reply	other threads:[~2016-09-04  9:23 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
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 [this message]
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=a028d072-8a7d-bc77-f539-eaca2c799bda@gmail.com \
    --to=marco.atzeri@gmail.com \
    --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).