From owner-freebsd-threads@FreeBSD.ORG Mon Apr 18 06:24:17 2011 Return-Path: Delivered-To: freebsd-threads@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5EBAB106566B; Mon, 18 Apr 2011 06:24:17 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 675698FC13; Mon, 18 Apr 2011 06:24:16 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id JAA03098; Mon, 18 Apr 2011 09:24:11 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QBhsZ-000Ozc-J8; Mon, 18 Apr 2011 09:24:11 +0300 Message-ID: <4DABD90A.1080402@FreeBSD.org> Date: Mon, 18 Apr 2011 09:24:10 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110308 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: Alexander Kabaev References: <4DA98197.8060104@FreeBSD.org> <4DAAFBAF.90700@FreeBSD.org> <4DAB0DC4.4060504@FreeBSD.org> <20110417205438.69235fc4@kan.dnsalias.net> In-Reply-To: <20110417205438.69235fc4@kan.dnsalias.net> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-threads@FreeBSD.org, hackers@FreeBSD.org Subject: Re: puzzled: fork +libthr X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2011 06:24:17 -0000 on 18/04/2011 03:54 Alexander Kabaev said the following: > > I would blame it, and expressly at that. -pthread is a shortcut for > {-lpthread -lc} instead of just {-lc} in the place where implied libc > is provided by the compiler driver and has no magic properties you want > it it to have. If chromium build infrastructure circumvents that, it is > only said build infrastructure to blame. OK, I see, thank you. Still inconvenient. As in: if we know for a fact that "gcc ... -pthread -lc" results in a broken binary, then IMO we should do something about that. -- Andriy Gapon