public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: heroxbd@gentoo.org
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] How to support C++11 in libraries?
Date: Thu, 19 Dec 2013 10:45:37 +0900	[thread overview]
Message-ID: <86ioultxz2.fsf@moguhome00.in.awa.tohoku.ac.jp> (raw)
In-Reply-To: <52B1E1CF.504@pathscale.com> ("C. \=\?utf-8\?Q\?Bergstr\=C3\=B6m\=22\?\= \=\?utf-8\?Q\?'s\?\= message of "Thu, 19 Dec 2013 00:56:31 +0700")

"C. Bergström" <cbergstrom@pathscale.com> writes:

> "Best case" both build and you end up with a linker problem (can be
> worked around with compiler patches)
> /usr/lib64/libboost.so
> /usr/lib64-c++11/libboost.so

This is the right way to do, but as scary as our multilib where a
couple of USE flags are introduced to every package globally.

  reply	other threads:[~2013-12-19  1:45 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18  7:54 [gentoo-dev] How to support C++11 in libraries? Michał Górny
2013-12-18  8:20 ` "C. Bergström"
2013-12-18 18:07   ` Michał Górny
2013-12-18 13:58 ` heroxbd
2013-12-18 16:29   ` Jan Kundrát
2013-12-18 16:37     ` "C. Bergström"
2013-12-18 16:50       ` Jan Kundrát
2013-12-18 17:05         ` "C. Bergström"
2013-12-18 17:33           ` Jan Kundrát
2013-12-18 17:47             ` Kent Fredric
2013-12-18 17:56               ` "C. Bergström"
2013-12-19  1:45                 ` heroxbd [this message]
2013-12-19  8:20                 ` Michał Górny
2013-12-19  8:28                   ` "C. Bergström"
2013-12-19  8:35                     ` Michał Górny
2013-12-19  8:44                       ` "C. Bergström"
2013-12-19 12:28                         ` Jan Kundrát
2013-12-19  8:45                       ` Jan Kundrát
2013-12-19  8:47                   ` Georg Rudoy
2013-12-18 17:49             ` "C. Bergström"
2013-12-18 18:28             ` Georg Rudoy
2013-12-19  1:41             ` heroxbd
2013-12-19  8:43               ` Jan Kundrát
2013-12-19  9:18                 ` Michał Górny
2013-12-19 13:47                   ` heroxbd
2013-12-19 14:46                     ` Michał Górny
2013-12-19 15:12                       ` heroxbd
2013-12-19 16:56                     ` Ciaran McCreesh
2013-12-19 15:17                   ` Jan Kundrát
2013-12-19 16:29                     ` vivo75
2013-12-19 16:51                       ` Jan Kundrát
2013-12-21  2:36                   ` [gentoo-dev] " Ryan Hill
2013-12-18 18:15   ` [gentoo-dev] " Michał Górny
2013-12-18 20:58     ` [gentoo-dev] " Martin Vaeth
2013-12-19  2:01     ` [gentoo-dev] " heroxbd
2013-12-18 14:27 ` Ian Stakenvicius
2013-12-18 18:10 ` Anthony G. Basile
2013-12-18 18:28   ` Ian Stakenvicius
2013-12-19  8:58 ` Sven Eden
2013-12-19  9:07   ` Michał Górny
2013-12-19 15:00     ` Ian Stakenvicius
2013-12-19 15:23       ` Jan Kundrát
2013-12-19 16:00         ` Anthony G. Basile
2013-12-20  9:00         ` [gentoo-dev] " Martin Vaeth
2013-12-20 12:35           ` [gentoo-dev] " Jan Kundrát
2013-12-20 17:35             ` [gentoo-dev] " Martin Vaeth
2013-12-20 11:56         ` [gentoo-dev] " Sven Eden
2013-12-20 12:45           ` Jan Kundrát
2013-12-20 12:54             ` Georg Rudoy
2013-12-20 17:49             ` [gentoo-dev] " Martin Vaeth
2013-12-20 15:10           ` [gentoo-dev] " Ian Stakenvicius
2013-12-19 15:51       ` Anthony G. Basile

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=86ioultxz2.fsf@moguhome00.in.awa.tohoku.ac.jp \
    --to=heroxbd@gentoo.org \
    --cc=gentoo-dev@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