From owner-freebsd-ports@FreeBSD.ORG Thu Jan 23 19:53:08 2014 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 164E842E for ; Thu, 23 Jan 2014 19:53:08 +0000 (UTC) Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C8C0413A7 for ; Thu, 23 Jan 2014 19:53:07 +0000 (UTC) Received: by mail-ob0-f172.google.com with SMTP id vb8so2594915obc.31 for ; Thu, 23 Jan 2014 11:53:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bluelife.at; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=NGo2Kdxt60ocAzVgS7LVZ3qXHDsHbDqHnOLMdT0dp40=; b=Krrpa2L5yQ9mlb1LZT2MWamhbY+G7XNgvMORw4Tf+IgKPTNi97ovxlkDObVevVfQXI LK0+u3JF1N/O4VsXBGLbwhtcz4/4nfnPo3ZKDYkPvH0Y8+Dx+gM40asRfZpXQWkFgHLG gNyRpEN8/hHPKYYCjQv2Zw+Zn0UWat6Le/vH8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=NGo2Kdxt60ocAzVgS7LVZ3qXHDsHbDqHnOLMdT0dp40=; b=Ys3MLAIRaLjIsUq58Sy0QU0FI79Cj79i5cvvk6M5Zi+HeGzQj+9mKolCJar8KbLTLb TqyhSaesUEJciW0nsuRU8rsGCwxepWVT8ma3QzJeG8W2J+MsZiXIERIAw4bAo2EVk1iM R0iI6WCnfdUN81iGZHTCcrRuxtYw7bkWv/TIuIRi2w+hAlA9ymmBgZP8Vs85hZT9Mu+H 467E0Qyv6ZVWTN7VpaU/dqlcCeO5itYG8wD/fndf5qsx+02rrHNDVaGoiWl7AFtk0veS OlpcqyHL2+8ekpTCkjFPKPJ1nff1bpCyO7qU1t5zOEso3c2xxW0XPZyjfXqb1kcn9j/J lsvw== X-Gm-Message-State: ALoCoQminlCUnDXPHh5FTE5lzkVTiklFrhTMeXAaPDoOuRld12pRgAoMf9/n2bayMi+qc/DYixCx MIME-Version: 1.0 X-Received: by 10.182.213.104 with SMTP id nr8mr1714921obc.81.1390506787034; Thu, 23 Jan 2014 11:53:07 -0800 (PST) Received: by 10.76.154.2 with HTTP; Thu, 23 Jan 2014 11:53:06 -0800 (PST) X-Originating-IP: [176.66.54.191] Received: by 10.76.154.2 with HTTP; Thu, 23 Jan 2014 11:53:06 -0800 (PST) In-Reply-To: <52E167BF.8050103@rawbw.com> References: <52DEE7EE.6010909@rawbw.com> <52DF0346.6000108@ShaneWare.Biz> <52E167BF.8050103@rawbw.com> Date: Thu, 23 Jan 2014 20:53:06 +0100 Message-ID: Subject: Re: USE_GCC doesn't set rpath From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= To: Yuri Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: ports@freebsd.org, 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 19:53:08 -0000 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 loads >> libtorrent-rasterbar.so.7 which tries to load libstdc++ and it is given >> 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 also 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 now 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 more 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.