I think this is off topic, but... Do not fear, Apache 2 will produce a working BONE build, expect some news in a couple of months on the Webserver Kit front. Cheers, Matt > Ted wrote: > >Next time try to do a ./configure with the prefix option, that way > > you > can > >hardcode the path yourself > > i wrote (emphasis added) ;) > > >>which is obviously a hardcoded linux path, _despite_ the fact that > > > i > used > >>the --prefix=/boot/home/apache/ in ./configure. > > > >>Just want to check if i am not making any mistakes before i file a > bug. > > i have checked david's apache 2.0 site (which he himself notes is out > of date), i have checked the perl script from bebits.com that uses > wget > to download and build apache (its broken in the URL its trying to > receive - but the ./configure options are exactly what i used). > > What i dont know right now is: is this a simple fix of a > misconfigured > file or is it emblematic of further problems on the BeOS portions of > apache 2.0. > > .. yes there is the webserver kit with apache 1.3.24 - but i am > currently more interested in getting 2.0 to compile painlessly from > the > nightly snapshot. > > Furthermore - does anyone know if bebits is currently in active > maintenance ?? ie are apps being checked to see if they even work > anymore ?? > > Regards, > Nick > >