From owner-freebsd-current@FreeBSD.ORG Sun Sep 21 01:25:10 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9E3E16A4C1; Sun, 21 Sep 2003 01:25:10 -0700 (PDT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C83843FCB; Sun, 21 Sep 2003 01:25:10 -0700 (PDT) (envelope-from DougB@freebsd.org) Received: from master.dougb.net (12-234-17-181.client.attbi.com[12.234.17.181]) by comcast.net (rwcrmhc13) with SMTP id <2003092108250901500gh7hfe>; Sun, 21 Sep 2003 08:25:09 +0000 Date: Sun, 21 Sep 2003 01:25:09 -0700 (PDT) From: Doug Barton To: deischen@freebsd.org In-Reply-To: Message-ID: <20030921011930.K9576@znfgre.qbhto.arg> References: Organization: http://www.FreeBSD.org/ X-message-flag: Outlook -- Not just for spreading viruses anymore! MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Fixing -pthreads (Re: ports and -current) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2003 08:25:10 -0000 On Sun, 21 Sep 2003, Daniel Eischen wrote: > Well, actually it is directly related. Part of the plan to > transition to libpthread is making ports PTHREAD_LIBS compliant. > As stated in that thread, if a libpthread exists on the system, > autoconf/configure will pick it up and the port will also end up > using -pthread and/or PTHREAD_LIBS. If PTHREAD_LIBS is set > to libthr or libc_r (something other than libpthread), then > the port ends up linking to both libraries. This doesn't work > but you don't know it until your run the application and very > weird things happen. Causing a clean breakage is better because > you know at compile-time that something is wrong. So ports need to > first be PTHREAD_LIBS compliant before we make the switch. Soon > after ports are fixed, we can rename it. Where the ports are concerned, I think this is a reasonable course of action, and I'd like to thank you for backing out the -pthread change on HEAD. I am a little confused about one thing though. What is going to happen to third party apps that use -pthread that aren't compiled through the ports? Doug -- This .signature sanitized for your protection