public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Lluís Batlle i Rossell" <viric@viric.name>
To: cygwin@cygwin.com
Subject: Re: Boost wrongly built for 'context' lib
Date: Fri, 18 Dec 2020 14:00:35 +0100	[thread overview]
Message-ID: <19541ecb.ANAAAI15lDoAAAAAAAAAALFruKAAARpcY_sAAAAAAAeRJgBf3KgI@mailjet.com> (raw)
In-Reply-To: <20201216131223.hdd4tvvol2d54ozh@vicerveza>

I could get a change to boost upstream that will fix it likely in the next
release.

But that would require the cygwin boost maintainer at least to provide
that boost lib available. Nevertheless the fix is interesting as a patch
for previous boost versions though.

This patch:

https://github.com/boostorg/context/commit/e785657ec4d6a885ba2fd49c3ad8eaeac1f71a34

On Wed, Dec 16, 2020 at 02:12:23PM +0100, Lluís Batlle i Rossell wrote:
> Hello,
> 
> the boost library (1.66, quite outdated) is wrongly built for cygwin
> regarding the 'context' lib, in a way that makes the 'coroutine2' lib
> crash.
> 
> b2 should be called with "context-impl=ucontext" argument when building
> it.
> 
> And programs using boost context/coroutine2 should build with the flag
> -DBOOST_USE_UCONTEXT
> 
> These options are documented at the bottom of this page:
> https://www.boost.org/doc/libs/1_75_0/libs/context/doc/html/context/architectures.html
> 
> And that would fix the problem here reported for the nix program.
> https://github.com/NixOS/nix/issues/4360
> 
> Can someone make that fix?
> 
> I haven't tried explicitly 1.66 with that build flag, but 1.75 failed the
> same way until I added that build flag.
> 
> Thank you,
> Lluís.
> 
> -- 
> (Escriu-me xifrat si saps PGP / Write ciphered if you know PGP)
> PGP key 7CBD1DA5 - https://emailselfdefense.fsf.org/

-- 
(Escriu-me xifrat si saps PGP / Write ciphered if you know PGP)
PGP key 7CBD1DA5 - https://emailselfdefense.fsf.org/

       reply	other threads:[~2020-12-18 13:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201216131223.hdd4tvvol2d54ozh@vicerveza>
2020-12-18 13:00 ` Lluís Batlle i Rossell [this message]
2020-12-18 16:56   ` Ken Brown
2020-12-16 13:12 Lluís Batlle i Rossell

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=19541ecb.ANAAAI15lDoAAAAAAAAAALFruKAAARpcY_sAAAAAAAeRJgBf3KgI@mailjet.com \
    --to=viric@viric.name \
    --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).