From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1QyrQU-0003t3-Mv for garchives@archives.gentoo.org; Wed, 31 Aug 2011 20:30:22 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0FE2521C0E1; Wed, 31 Aug 2011 20:30:13 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 7625121C0C0 for ; Wed, 31 Aug 2011 20:29:39 +0000 (UTC) Received: from vapier.localnet (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 05A8B1B401A for ; Wed, 31 Aug 2011 20:29:39 +0000 (UTC) From: Mike Frysinger Organization: wh0rd.org To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] glibc-2.14 and changes in rpc support (libtirpc) Date: Wed, 31 Aug 2011 16:29:38 -0400 User-Agent: KMail/1.13.7 (Linux/3.0.3; KDE/4.6.3; x86_64; ; ) References: <201106111611.36160.vapier@gentoo.org> In-Reply-To: <201106111611.36160.vapier@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5850106.uGzvEqOffv"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201108311629.39323.vapier@gentoo.org> X-Archives-Salt: X-Archives-Hash: 186be8dc9753d18aafc9a5a616b3b991 --nextPart5850106.uGzvEqOffv Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Saturday, June 11, 2011 16:11:35 Mike Frysinger wrote: > historically, glibc provided all the ugly rpc support (while not nearly as > relevant today, it still is used by way of nfs support). the glibc > maintainers have opted to stop supporting this. at first they declined to > accept new features, but now they've started removing support for new code > to build against it. >=20 > libtirpc started off to support the new features (namely ipv6 support), b= ut > has now taken on a new roll of supporting all the rpc code. >=20 > so if you have a build bug due to glibc-2.14 due to missing rpc/ or rpcsv= c/ > header, you're going to have to convert over to libtirpc. >=20 > something like: > inherit toolchain-funcs > ... > append-cppflags $($(tc-getPKG_CONFIG) libtirpc --cflags) > export LIBS+=3D" $($(tc-getPKG_CONFIG) libtirpc --libs)" >=20 > obviously the LIBS part will need tweaking based on your package. after seeing the feedback of broken packages, and libtirpc itself not being= =20 ready as a full replacement for the rpc symbols, i plan on implementing the= =20 same kind of hack that fedora is using atm: re-exporting the symbols and=20 headers. this will give us time to migrate packages over to libtirpc witho= ut=20 being stuck on glibc-2.13 indefinitely. the ABI will not be adversely affected long or short or any other term. =2Dmike --nextPart5850106.uGzvEqOffv Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iQIcBAABAgAGBQJOXpmzAAoJEEFjO5/oN/WBkwYP/3QFZ9KgtNwv9mlTe+A4wJNW BkhJMC/tLo3KlUSMPuqsvLEolxhOtrPXWmEcPKuyKjSA305H4lWJhEktzhLZulq/ wHOG9RlleKOCi8Zo5m3XTqr6trdhGmeow2RyHv4+IpvAD03guYLzejfGpaT243sp Ad+3htVyELse3nxsqIMK8i4+xtGSBZiflckAfuNecbevNhcYAsTSrAdKB5LC1gGL AnGOsFJ0MoJtYyt/LCKO1M/pToH6DxPIxY9wq5g1EF6sa+qJxBwMMiMGlNYyce1Y d0ruVuci0DbzJ6fjFnj0RGbndIcP8l42ZageI0w8jxR/mcwmwbQhktAcUxTcDXce hi9tYELiQ8aNkXyJz6i9+bUmql91b0dtq81Rj0lcmdgyNz0GKZDbOnzfxr5nTNe2 ZTgEnFavn8o3bZc7ifUlVEfSRxOmstOX2c4pP2ZNHhfgCfJPLYfSAHiQ9IhU2yjF NrJpb/xCXE3qrnt/HB6ghhaCoApj0EkEo8pMYpdrQQNxb4h4DKJOgcYe8Jzlhiuh QRQm5oRBgMBU7/zlzA3/kOn6p5mORXHGx2pgNyIFHqXAQkezGs4oGbnEK14+kmHQ 1E7NkF6mx6s/7DIiZeCdDgykjbtHmBIJifnQHvoT8x81h42AwEvQ/G31dDL+knGX U+Gu9nUMxcCSM/5N0zsh =e7pj -----END PGP SIGNATURE----- --nextPart5850106.uGzvEqOffv--