Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA28566; Mon, 11 Mar 96 03:19:09 EST
Received: from YAZ-PISTACHIO.MIT.EDU by MIT.EDU with SMTP
	id AA12644; Mon, 11 Mar 96 03:18:26 EST
Received: by yaz-pistachio.MIT.EDU (5.57/4.7) id AA08517; Mon, 11 Mar 96 03:19:07 -0500
Message-Id: <9603110819.AA08517@yaz-pistachio.MIT.EDU>
To: skip@calendar.com (Skip Montanaro)
Cc: proven@MIT.EDU
Subject: Re: pthreads for BSDi 
In-Reply-To: Your message of "Sat, 09 Mar 1996 07:12:36 EST."
             <199603091212.HAA26222@dolphin.automatrix.com> 
Date: Mon, 11 Mar 1996 03:19:05 EST
From: Christopher Provenzano  <proven@MIT.EDU>


> 
> Chris,
> 
> I visited your Web site this morning looking for pthreads for BSDi v2.0.
> The FAQ said 1.60.5 was available and ran in my environment.  I could only
> find 1.60.4.1.  When I tried configuring it configure said:
> 

I don't have a BSDi system to test but it's close enough to FreeBSD and NetBSD
and people have sent patches to make it work so things should work with 
minimal patching. What does uname -s return? You'll what to edit
config/configure and modify the line i386-*-bsdi) to represent whatever
bsdi calls themselves these days. You should also make sure uname is in
/bin. That might be the problem too.

>     checking host system type... Invalid configuration `': machine `' not rec
> ognized
> 
>     checking target system type... Invalid configuration `': machine `' not r
> ecognized
> 
>     checking build system type... Invalid configuration `': machine `' not re
> cognized
> 
> so I suspect 1.60.4.1 doesn't run on BSDi.  Was 1.60.5 retracted shortly
> after release?

I'm getting ready to release it. A few more bugs have cropped up that I'm 
trying to kill before kicking it out the door. 

CAP
