I got the latest cvs and it's just fine actually. The only thing I didn't
have after building with ssl added in, is a 443 vhost. I'm going to mess
with it some more and see.
--
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-9023
email: [EMAIL PROTECTED]
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 14, 2001 2:13 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: 2.0.18 compile problem
>
>
>
> Any changes that happened after 2.0.18 will not be available
> until 2.0.19
> is rolled. As it happens, I did a quick search, and there
> haven't been
> any changes to htpasswd.c since 2.0.18. However, I build
> this everyday,
> and I don't have this problem.
>
> I believe that the problem you are having is that 2.0.18 is not a good
> snapshot. I think these problems should make 2.0.18 fail
> your testing,
> and you should wait until 2.0.19 is released. Hopefully we
> will be fixing
> the major bugs soon, and we can release it sometime next week.
>
> Ryan
>
>
> On Thu, 14 Jun 2001, Gonyou, Austin wrote:
>
> > But it's about 2.0.18 tarballs, not 2.0.19.
> >
> > --
> > Austin Gonyou
> > Systems Architect, CCNA
> > Coremetrics, Inc.
> > Phone: 512-796-9023
> > email: [EMAIL PROTECTED]
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > > Sent: Thursday, June 14, 2001 11:06 AM
> > > To: '[EMAIL PROTECTED]'
> > > Subject: RE: 2.0.18 compile problem
> > >
> > >
> > >
> > > There are still some major problems with the current HEAD of
> > > the tree, so
> > > Apache 2.0.19 has not been released yet.
> > >
> > > Ryan
> > >
> > > On Thu, 14 Jun 2001, Gonyou, Austin wrote:
> > >
> > > > Then have the new tarballs been rolled yet? The one I
> was using from
> > > > apache.org/dist is the one with the problem.
> > > >
> > > > --
> > > > Austin Gonyou
> > > > Systems Architect, CCNA
> > > > Coremetrics, Inc.
> > > > Phone: 512-796-9023
> > > > email: [EMAIL PROTECTED]
> > > >
> > > > > -----Original Message-----
> > > > > From: Justin Erenkrantz [mailto:[EMAIL PROTECTED]]
> > > > > Sent: Wednesday, June 13, 2001 7:31 PM
> > > > > To: [EMAIL PROTECTED]
> > > > > Subject: Re: 2.0.18 compile problem
> > > > >
> > > > >
> > > > > On Wed, Jun 13, 2001 at 05:50:01PM -0500, Gonyou,
> Austin wrote:
> > > > > > Could someone _please_ tell me if they know what's going on
> > > > > here with the
> > > > > > sha1_base64 deal. What do I need, or better, what does apr
> > > > > need, to make
> > > > > > htpasswd compile properly? I'd really like to test this new
> > > > > release, but it
> > > > > > won't get past it, unless I comment out the offending
> > > > > lines, but there's
> > > > > > more affected than just htpasswd.
> > > > >
> > > > > You are using 2.0.18, right? I think there were some recent
> > > > > commits for
> > > > > htpasswd.c after we tagged and rolled 2.0.18.
> > > > >
> > > > > Try with the latest CVS copy. htpasswd compiles for me.
> > > This seems
> > > > > like one of the auto-generated export files might be bad
> > > or something.
> > > > > (If you are using Win32, I have no clue - maybe the
> DSPs are bad.)
> > > > > -- justin
> > > > >
> > > >
> > > >
> > >
> > >
> > > ______________________________________________________________
> > > _________________
> > > Ryan Bloom [EMAIL PROTECTED]
> > > 406 29th St.
> > > San Francisco, CA 94131
> > > --------------------------------------------------------------
> > > -----------------
> > >
> >
> >
>
>
> ______________________________________________________________
> _________________
> Ryan Bloom [EMAIL PROTECTED]
> 406 29th St.
> San Francisco, CA 94131
> --------------------------------------------------------------
> -----------------
>
