From owner-freebsd-ports Mon Jan 22 20:38:20 2001 Delivered-To: freebsd-ports@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id F423C37B402; Mon, 22 Jan 2001 20:38:01 -0800 (PST) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.9.3/8.9.3) with SMTP id XAA92448; Mon, 22 Jan 2001 23:37:27 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <000701c084f6$d5290370$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Jeremy Lea" , "Daniel Eischen" Cc: References: <3A6CA399.7F8B801E@vigrid.com> <20010122200425.A63549@shale.csir.co.za> Subject: Re: HEADS UP: -pthread is going to break under -current soon Date: Mon, 22 Jan 2001 23:42:02 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > > On Mon, Jan 22, 2001 at 04:18:17PM -0500, Daniel Eischen wrote: > > In a couple of days, I'll be committing changes to libc and libc_r > > to allow them to be linked together via -lc_r. libc_r will only > > contain the thread functions and will not contain any libc functions > > as it does currently. We currently use -pthread as a non-standard > > hack to link to libc_r and to prevent linking to libc. After I > > commit these changes, using -pthread will not work; it will produce > > an executable that is only linked to libc_r but which also needs to > > be linked to libc. This also means that all (shared) threaded apps > > will need to be recompiled under -current. > > I would like to object to this change. Using -pthread to link threaded > applications has been well advertised as a FreeBSD way of doing things, > and you are going to break lots of ports, many of which will be non > trivial to fix to work on both -current and -stable. Well, as someone who recently added FreeBSD to the list of supported platforms for an open source application, I won't begin to go through the pain and heartache that I had to endure to a) understand and b) work around the way FreeBSD does threads. GNU automake, autoconf and to some extent, gcc, all don't like the way that we do this. I would rather see us change to the "GNU standard" of doing this, especially since it would eliminate one more strangness that surrounds FreeBSD. After all, we're going to have to do it eventually -- now's just as good a time as any! -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message