From owner-freebsd-ports@FreeBSD.ORG Thu Jan 23 20:53:35 2014 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 61BC9181; Thu, 23 Jan 2014 20:53:35 +0000 (UTC) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 21AA019C2; Thu, 23 Jan 2014 20:53:35 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id lx4so1832715iec.41 for ; Thu, 23 Jan 2014 12:53:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2KYhdhRqSJo/mFzEinIfmjrq6ILVy/+73TKbRRH4V8A=; b=jKbcxChL4suBVSfSLZ10wTpR0s3hyx4w0qFGRdFwpUXT5ooT0K2+NSi/Z8LGBn5J1t 2jPLGMerRo+Wa4gwCVVYqiMS1YpcY8t6Jzw4bjOy1EovzesjRRqr0yuMVq6269GTYxIT aBaTqPRfvhHbKxCl/BcEOMXHnU75WGim/JKqGO7w/fgw6vglkmODswv6qGH1LLN5dAJW ZPL1aKqrMHPtRulREPmagDAFffdrMsUnvnF6tuc+v1dUHFZ2vckOlv1nHtdTfW7quLRz QbCg/kOMBAABbM1F+Lrlh1TSp7AKfxLJH5N2T89VqFUqPdB8zfIOINMRmebkV4LFPBcn G56Q== MIME-Version: 1.0 X-Received: by 10.43.129.70 with SMTP id hh6mr2641941icc.68.1390510414570; Thu, 23 Jan 2014 12:53:34 -0800 (PST) Received: by 10.64.89.2 with HTTP; Thu, 23 Jan 2014 12:53:34 -0800 (PST) In-Reply-To: <52E173E4.2050003@marino.st> References: <52DEE7EE.6010909@rawbw.com> <52DF0346.6000108@ShaneWare.Biz> <52E167BF.8050103@rawbw.com> <52E173E4.2050003@marino.st> Date: Thu, 23 Jan 2014 22:53:34 +0200 Message-ID: Subject: Re: USE_GCC doesn't set rpath From: "Andrew W. Nosenko" To: marino@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD Ports , Yuri , =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= , Gerald Pfeifer , Shane Ambler X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jan 2014 20:53:35 -0000 On Thu, Jan 23, 2014 at 9:56 PM, John Marino wro= te: > On 1/23/2014 20:53, Bernhard Fr=F6hlich wrote: > > Am 23.01.2014 20:04 schrieb "Yuri" : > >> > >> On 01/21/2014 15:31, Shane Ambler wrote: > >>> > >>> I think you will find that qbittorrent will need to be built with the > >>> same gcc version as libtorrent-rasterbar. > >>> > >>> I believe qbittorrent is loading /usr/lib/libstdc++.so.6 then it load= s > >>> libtorrent-rasterbar.so.7 which tries to load libstdc++ and it is giv= en > >>> the already open copy which doesn't have GLIBCXX_3.4.15 that it needs > to > >>> run. > >> > >> > >> Yes, you are right, thst's what is happening. > >> So if any dependency has USE_GCC set, all dependent packages should al= so > > have USE_GCC set. Can ports build infrastructure automatically set > USE_GCC > > for dependent ports? Because doing this by hand in each port is tedious > and > > error prone. > >> > >> Yuri > > > > No it can't right now and this is why we need a ports compiler. Right n= ow > > we are hiding this problems by the fact that we are able to build 95% > > percent of the tree with clang and everyone is happy. We add dozens of > > patches to compile with clang or add this rpath workarounds to even mor= e > > ports just because nobody wants to acknowledge that this is shit and > won't > > work properly unless really everything is build with one compiler. > > > > The rpath stuff is only a workaround that works in a few cases but it > > doesn't work in all cases. You will still see very hard to diagnose > runtime > > crashes. > > While I basically agree with this sentiment, is not it just ports that > use C++ that are affected? Could not this be narrowed down to "We need > a single compiler for ports that use C++" ? > No. Everything that uses language- or feature-support library are affected. I'm, for example, unable to use OpenMP higher than 2.5 even if compiler is gcc-4.8, which is openmp-3.x capable). But, from my point of view, the problem is not a compiler nor rpath. rpath is unneeded indeed, and library indeed may be only one (under /lib). The real problem is that this is ancient library, not the most recent one. They are especially designed to be backward compatible and have the same so-number for a reason. --=20 Andrew W. Nosenko