From owner-freebsd-current Wed Jan 31 7: 2: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (ns.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 4743837B491 for ; Wed, 31 Jan 2001 07:00:27 -0800 (PST) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f0VExiT03601; Wed, 31 Jan 2001 16:59:59 +0200 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.1/8.9.3) with ESMTP id f0VExn861426; Wed, 31 Jan 2001 16:59:49 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3A782864.AE795925@FreeBSD.org> Date: Wed, 31 Jan 2001 16:59:49 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: "Andrey A. Chernov" Cc: eischen@vigrid.com, current@FreeBSD.org Subject: Re: New threads way questions References: <20010131174457.A19255@nagual.pp.ru> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Andrey A. Chernov" wrote: > I have some questions about new threads way. Daniel says that new way is: > > > gcc -Wall -o foo foo.c -lc_r > > 1) What about libgcc_r.a? Is it picked automatically in this case or > not? Is it ever needed now? libgcc_r is gone (merged into libgcc.a). In the meantime you should replace it manually with a symlink to libgcc.a (many ports still assume that gcc_r exists). > 2) Is new way is backward-compatible with old way? I.e. can we just change > ports to use new way and assume that still works on -stable? This issue is actually is more complicated than that. While this change has been MFC'ed to the stable, but this option is still required for the older versions (4.2-RELEASE and downward), so ideally __FreeBSD_version should be bumped and -lgcc_r placed into a conditional in all ports that make use of gcc_r. > 3) Is -D_THREAD_SAFE required now? AFAIK yes. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message