Date: Mon, 18 Apr 2011 09:24:10 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Alexander Kabaev <kabaev@gmail.com> Cc: freebsd-threads@FreeBSD.org, hackers@FreeBSD.org Subject: Re: puzzled: fork +libthr Message-ID: <4DABD90A.1080402@FreeBSD.org> In-Reply-To: <20110417205438.69235fc4@kan.dnsalias.net> References: <4DA98197.8060104@FreeBSD.org> <4DAAFBAF.90700@FreeBSD.org> <Pine.GSO.4.64.1104171119110.5365@sea.ntplx.net> <4DAB0DC4.4060504@FreeBSD.org> <20110417205438.69235fc4@kan.dnsalias.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DABD90A.1080402>