From owner-freebsd-ports@FreeBSD.ORG Wed Jun 28 15:23:30 2006 Return-Path: X-Original-To: FreeBSD-Ports@freebsd.org Delivered-To: FreeBSD-Ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2427316A403 for ; Wed, 28 Jun 2006 15:23:30 +0000 (UTC) (envelope-from hannes.hauswedell@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CD9944AA2 for ; Wed, 28 Jun 2006 15:23:29 +0000 (GMT) (envelope-from hannes.hauswedell@gmail.com) Received: by nf-out-0910.google.com with SMTP id c29so1225335nfb for ; Wed, 28 Jun 2006 08:23:28 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:disposition-notification-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=UwBJfhyhPcCtvmlPmcKNoSAYZUqguv3nYSYjZBTAOjoXlHF7SUTw91JfPJLLskvgw5+auTPWrxd4YNTHTsxG+GAGVVipvZbz6/DeBE4aazlBpIlYgayLuekCn5RzAwFCr9hTPtfTYJHr4WH6A+8/ZvjskBae4JjJIHNh/EzHlUU= Received: by 10.49.51.8 with SMTP id d8mr799682nfk; Wed, 28 Jun 2006 08:23:27 -0700 (PDT) Received: from ?192.168.2.80? ( [85.220.132.38]) by mx.gmail.com with ESMTP id p45sm888353nfa.2006.06.28.08.23.26; Wed, 28 Jun 2006 08:23:26 -0700 (PDT) From: Hannes Hauswedell To: FreeBSD-Ports@freebsd.org Date: Wed, 28 Jun 2006 15:44:59 +0000 User-Agent: KMail/1.9.1 References: <449CEB97.5020903@gmx.de> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200606281544.59900.hannes.hauswedell@gmail.com> Cc: Subject: Re: latest wine-kthread broken? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jun 2006 15:23:30 -0000 > This may well be. However, GNU/Linux systems using the pthread variant, > there is little hope anyone is ever going to fix the kthread variant. I > have included the kthread variant as an added benefit, but all development > and bug fixing really should go into the pthread variant. > > You did not mention whether this works for your applications, but I > assume it does not? > > Gerald just read this and wanted to say: the pthread binary of wine (the one without suffix) cannot execute a single game that i have (whereas there are some that DO run in kthreads mode)... so whats actually wrong? i thought POSIX compliance (e.g. threading ) actually means that if something works on platform a than it works an platform b too!? why isnt this the case, is it wines fault or is freebsd's pthread implementation not good? thanks