From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] boost-1.63 dependency confusion
Date: Sat, 11 Nov 2017 16:08:10 +0000 [thread overview]
Message-ID: <24767286.I84CqeEpta@peak> (raw)
In-Reply-To: <9b7aeac3-8f70-600f-fffa-5b02bbc18e84@googlemail.com>
On Saturday, 11 November 2017 15:40:18 GMT Jens Pelzetter wrote:
> Hello all,
>
> alternativly you can do manual step wise update (which work at least for
> me):
>
> # emerge -va --oneshot =dev-util/boost-build-1.63
> # emerge -va --oneshot =dev-libs/boost-1.63
>
> After that, emerge should behave normal.
That didn't work for me: boost-build refused to build without my first
emerging boost.
--
Regards,
Peter.
next prev parent reply other threads:[~2017-11-11 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-11 10:37 [gentoo-user] boost-1.63 dependency confusion Mick
2017-11-11 11:32 ` Philip Webb
2017-11-11 11:45 ` David M. Fellows
2017-11-11 12:20 ` Mick
2017-11-11 13:36 ` Peter Humphrey
2017-11-11 23:02 ` Bill Kenworthy
2017-11-11 15:40 ` Jens Pelzetter
2017-11-11 16:08 ` Peter Humphrey [this message]
2017-11-11 22:34 ` Neil Bothwick
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=24767286.I84CqeEpta@peak \
--to=peter@prh.myzen.co.uk \
--cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox