[gentoo-dev] Last rites: net-print/foomatic-filters-ppds
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
# Deprecated by upstream, Debian removed it in 2010.
# Contents of this package moved to foomatic-db{,-engine,-ppds}
# and cups-filters.
# Masking for removal in 30 days.
net-print/foomatic-filters-ppds
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0
iQJ8BAEBCgBmBQJUS8tYXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4MDA1RERERkM0ODM2QkE4MEY3NzY0N0M1
OEZCQTM2QzhEOUQ2MzVDAAoJEFj7o2yNnWNcKWQP/3NOhheSMwswhk3pO7p98juW
s78boQxlhUUB56O9Wd0pLEXwz8KLdwEf5plJiDCTQ1ulxs+SNNMJoR0/rCCr3a6+
h7v2rKsjoLhglRmxKFQJRg4akd8ZShLsP74wMXWQ6kPri8H97V70KWdBGMuQV9Zd
71Kr/LcD9Qvl1+OSm7/qg43dPX9LWQa3yhLlUGnsKVD9juzFedDhquL6O+HRIS7S
Ekjop5xkTsw/o5C6GBXabSPasp9Rw9p+0/BqSQJpo+yxsetbyv7eRMUnKfXnwqOu
6Q4SxZdsPBchkRjcoD1ClpwlHZF56fmlgBODDI5G6hi2a/RkYgP9nsqYDbB+LSLg
4Ko/BSEiFLkad94398oBf53dcxbhBaXb8K9/CI/9hpSOdbXSZuyKl22k7TDQ6Hxw
6VJo/gazDMMeU2oZTO/LSj9BTC7limh0hhkKhxvk8pGggMfkf2ilciXgVlrEaz4T
XwYR/Qt2VnIZl+kn8VAR8F0dLQ9scBRfB7n1Jb8QTNT5IdvbpMz6EyLtCu0DKgfQ
4LS2JVPkiAWE/AwPy/mFzuJXHM4ySLtgLXmfz1MRupDkcmpHaQD2WdT4oQ+vcFNq
uY6yWI/uFg4XTDvpuPPu+nDctTCBW7GDeGvmMVt4q7VnHKCKcoR7I0t+HrOyxWV1
rcQs4ExZzzG8Ry1sXlOk
=hpf9
-END PGP SIGNATURE-
Re: [gentoo-dev] status of bugs blocking gcc-4.8.3
On 25/10/14 13:09, Matthias Maier wrote: > >> Not sure if the llvm C++ runtime might help here or it is any better >> than the one provided by gnu, but might be a good time to gather >> volunteers to provide a mean to use clang as main compiler out of box. > > libc++ makes stricter ABI guarantees [1]. But from personal experience I > would not consider it a replacement for libstdc++ in the near future. Probably we could join forces with FreeBSD to help pushing fixes to applications upstream. > I have set up some lxc containers with clang/libc++ with promising > results (and I plan to keep up testing with it once in a while). Could you please blog or add some notes to the wiki about it? lu
Re: [gentoo-dev] status of bugs blocking gcc-4.8.3
> Not sure if the llvm C++ runtime might help here or it is any better > than the one provided by gnu, but might be a good time to gather > volunteers to provide a mean to use clang as main compiler out of box. libc++ makes stricter ABI guarantees [1]. But from personal experience I would not consider it a replacement for libstdc++ in the near future. I have set up some lxc containers with clang/libc++ with promising results (and I plan to keep up testing with it once in a while). Best, Matthias [1] http://clang-developers.42468.n3.nabble.com/libc-ABI-stability-td2976682.html
Re: [gentoo-dev] status of bugs blocking gcc-4.8.3
On 24/10/14 19:12, Anthony G. Basile wrote: > bug 513386 - net-libs/webkit-gtk-2.4.3 - ./.libs/libwebkitgtk-3.0.so: > undefined reference to `_ZNSt6chrono12steady_clock3nowEv@GLIBCXX_3.4.17' > -> This is a problem. It relates to abi mismatching with libstdc++. The ABI mismatch is due the library not being versioned properly as "usual"? > The bug details how you can hit it in gentoo. Martin von Gagern pushed > the issue upstream and pretty much got the answer "we're on our own" So > we'll have to deal with this as we go forward. > Seehttps://gcc.gnu.org/bugzilla/show_bug.cgi?id=61758 Not sure if the llvm C++ runtime might help here or it is any better than the one provided by gnu, but might be a good time to gather volunteers to provide a mean to use clang as main compiler out of box. Being on your own is not an answer I like to hear. Nor the whole approach to the discussion. lu
Re: [gentoo-dev] Re: RFC: News item regarding c++98 vs c++11
On 10/24/14 7:29 PM, Anthony G. Basile wrote: > So I don't have to keep email the entire item to the list, how about > just adding it as follows: > > "Nor is c++11 code compiled with gcc-4.7 ABI-compatible with c++11 > compiled with 4.8, and vice versa. An example can be see in ref. > [2]" > > Ref. [2] https://bugs.gentoo.org/show_bug.cgi?id=513386 I think this could still be clearer about the user/sysadmin perspective more than a developer perspective, i.e. present this more like "both gcc-4.7 and 4.8 installed with 4.7 being active" than "not ABI-compatible with C++11 compiled with 4.8". Here's my suggested draft: -%<- CUT HERE -%<- GCC 4.7 introduced the new experimental 2011 ISO C++ standard [1]. Users that wish to try enabling C++11 globally (e.g. using CXXFLAGS) should exercise caution because it is not ABI-compatible with C++98. Packages which are self-contained or do not link against any libraries written in C++ are not affected. Note that some packages like www-client/chromium and net-libs/webkit-gtk among others are already using C++11 features. Even having different versions of gcc installed simultaneously might lead to problems, especially if the active version of gcc is older. Please see [2] for example known bug with webkit-gtk. It is recommended to set the latest installed version of gcc as active; some packages may work when an older version is selected, but GCC upstream provides no guarantees of C++11 ABI stability for code compiled with gcc-4.x and 4.y for any x != y [3]. Ref. [1] http://www.stroustrup.com/C++11FAQ.html [2] https://bugs.gentoo.org/show_bug.cgi?id=513386 [3] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61758 -%<- CUT HERE -%<- Paweł signature.asc Description: OpenPGP digital signature
[gentoo-dev] last rites: dev-util/cmockery
# Tim Harder (25 Oct 2014) # Deprecated project, devwlopment continues in dev-util/cmocka. # Masked for removal in 30 days. dev-util/cmockery pgpFbqYtjXuY2.pgp Description: PGP signature
[gentoo-dev] last rites: dev-python/pry
# Tim Harder (25 Oct 2014) # Upstream migrated to nose for testing instead of their own framework. # Masked for removal in 30 days. dev-python/pry pgpjRV0rQHQab.pgp Description: PGP signature
