Win32 build

Hello,

Just for fun, I tried again to get chrokee compiled on win32, using 
Mingw, Msys and the configure script (not the Makefile.Mingw)

I got it working with some changes (there are probably some remaining bugs).

I attach to this mail a diff file containing some changes.
Notice, some modifications are needed on Makefiles. I made those on 
Makefile.in, but it will probably best to be done in Makefile.am(but I 
do not have a working automake in this win32 beast)
Notice also, that those modifications are done to get cherokee running 
on win32, and cannot be used on linux.

Changes are :
cherokee/Makefile.in
    Add and "export all symbols" option to the linker flags. (plus regex 
to only include symbols starting with "cherokee_")
    Can probably be done with CHEROKEE_EXPORT, but it's more simple 
using this.
    Add some references to plugins/libraries, since a win32 executable 
cannot be linked with unresolved symbols.
    Need probably to add some WIN32 checks
cherokee/main.c
    I do not know why but "HAVE_GETOPT_H" is not defined. So, I added a 
little ifdef before including getopt.h
cherokee/module_read_config.c
    Modified path contatenation to handle win32 pahs (using \ in place of /)
cherokee/read_config_grammar.y
cherokee/read_config_scanner.l

Re: Win32 build

Olivier Samyn wrote:

 > Just for fun, I tried again to get chrokee compiled on win32, using
 > Mingw, Msys and the configure script (not the Makefile.Mingw)
 >
 > I got it working with some changes (there are probably some
 > remaining bugs).

   I have also been trying to fix it.  Yesterday I found a weird
   problem around the I/O support on Windows. The following part of
   your patch is related to it..

 > --- cherokee-0.4.31b5/cherokee/util.c	Mon Jan 30 23:06:32 2006
 > +++ cherokee-0.4.31b5-os/cherokee/util.c	Tue Jan 31 14:41:34 2006
 >  <at>  <at>  -187,8 +187,13  <at>  <at> 
 >          *limit = OPEN_MAX;         /* need to include limits.h somehow */
 >  	return ret_ok;
 >  #else
 > +#ifdef _WIN32
 > +        *limit = 256;
 > +  return ret_ok;
 > +#else
 >          *limit = FD_SETSIZE;
 >  	return ret_ok;
 > +#endif
 >  #endif
 >  #endif
 >  #endif

    As far as I've seen, Windows doesn't return the file descriptor

mime_grammar.y

Compiling this file on MingW doesn't work here:

mime_grammar.y: In function `yy_mime_parse':
mime_grammar.y:89: warning: implicit declaration of function `cherokee_mime_add'
mime_grammar.y:93: warning: implicit declaration of function `MIME_ENTRY_NAME'
mime_grammar.y:93: warning: passing arg 1 of `cherokee_buffer_add' makes pointer from integer without
a cast
mime_grammar.y:110: warning: implicit declaration of function `MIME_ENTRY_AGE'
mime_grammar.y:110: error: invalid lvalue in assignment

I used rev. 183 from SVN. Any ideas?

--gv

Redirection issues

OK, so I finally upgraded to 0.4.31b6, and I'm still running into numerous redirection
issues. Was it only the 0.5.0 alpha that had the fixed redirection code? I can't
remember what was said on the list.

Here's one of the issues that I'm running into: if I show the redirection, I get the
page I'm after. If I hide the redirection, I get a 404 error. This problem is limited
to the second rule, for my monthly archives).

Directory /blog {
 Handler redir {
  Rewrite "^/$" "/wordpress/index.php"
  Rewrite "^/([0-9][0-9][0-9][0-9])_([0-9][0-9])\.html$" "/wordpress/index.php?m=$1$2"
  Rewrite "^/(.+)\.html$" "/wordpress/index.php?name=$1"
 }
}

The odd thing is that adding "Show" to the last rule shows the redirections for ALL of
the preceding rules, but adding "Show" to the second rule has no effect. Only the
second rules in this set is experiencing any issues.

My question is, do I have to run the 0.5.0 alphas in order to avoid redirection
problems? I'm pretty sure my redirection rules are syntactically correctly, unless
anyone sees anything glaringly out-of-place.

Thank you for any advice anyone can offer!

Sincerely,
Kurt McKee

Re: mime_grammar.y

Gisle Vanem wrote:

 > Compiling this file on MingW doesn't work here:

   I have been working on Windows all the weekend.. I implemented the
   CGI/PHP support and fixed a bunch of bugs. I'll commit all those
   changes this evening 

 > mime_grammar.y: In function `yy_mime_parse':
 > [..]
 >
 > I used rev. 183 from SVN. Any ideas?

   mime_grammar.y doesn't exist any longer. I removed that grammar when
   we switched to use standard mime definition files.

   BTW, I've been compiling it with the automake thing, and I have to
   say it has been working smoothly.  I know we talked about this
   before, but it'd be a good idea to try to use that on Windows too.

--

-- 
Greetings, alo.

Re: Redirection issues

Kurt McKee wrote:

 > Here's one of the issues that I'm running into: if I show the
 > redirection, I get the page I'm after. If I hide the redirection, I
 > get a 404 error. This problem is limited to the second rule, for my
 > monthly archives).
 >
 > Directory /blog {
 >  Handler redir {
 >   Rewrite "^/$" "/wordpress/index.php"
 >   Rewrite "^/([0-9][0-9][0-9][0-9])_([0-9][0-9])\.html$" "/wordpress/index.php?m=$1$2"
 >   Rewrite "^/(.+)\.html$" "/wordpress/index.php?name=$1"
 >  }
 > }
 >
 > The odd thing is that adding "Show" to the last rule shows the
 > redirections for ALL of the preceding rules, but adding "Show" to
 > the second rule has no effect. Only the second rules in this set is
 > experiencing any issues.

   It is definitely a bug (well, or a couple of them). Could you please
   log it? [1] I'll take a look ASAP, and I'll let you know..

     1.- http://www.0x50.org/bugs/

 > My question is, do I have to run the 0.5.0 alphas in order to avoid
 > redirection problems? I'm pretty sure my redirection rules are
 > syntactically correctly, unless anyone sees anything glaringly
 > out-of-place.

Many Questions

Hi

I have a many questions. 
I'm using Cherokee 0.4.8 (I think, yes is very old) but now I think
using FreeBDS, and my first question is:
 - Is possible compile and install Cherokee with FreeBSD?
Ok, 
 - Is possible that cherokee working with PHP5
 - Is possible that Cherokee working with Chroot in FreeBSD

Thanks a lot

--

-- 
http://vctrsnts.dyndns.org
"Hay 10 tipos de personas en este mundo."
"Las que saben binario y las que no."

Re: Many Questions

Ogoshi wrote:
> Hi
> 
> I have a many questions. 
> I'm using Cherokee 0.4.8 (I think, yes is very old) but now I think
> using FreeBDS, and my first question is:
>  - Is possible compile and install Cherokee with FreeBSD?

http://www.0x50.org/doc/Compiling_and_Installing.html
"We have compiled Cherokee in various platforms with different
compilers, so it shouldn't be a problem"

> Ok, 
>  - Is possible that cherokee working with PHP5

http://www.0x50.org/doc/PHP_execution.html
"... it will work with PHP3, PHP4 and PHP5."

>  - Is possible that Cherokee working with Chroot in FreeBSD

Yes, it may be simple..... ok, this may require a brief howto in
documentation site.

Rodolfo

_______________________________________________
Cherokee mailing list
Cherokee <at> 0x50.org
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee

Re: Many Questions

Rodolfo Pilas wrote:

 >> - Is possible that Cherokee working with Chroot in FreeBSD
 >
 > Yes, it may be simple..... ok, this may require a brief howto in
 > documentation site.

   Yeah, I ought to improve the documentation.  Yesterday I replied a
   mail about the log rotation feature.  Actually, that is a pretty
   cool feature that only support Cherokee: nor Apache, nor the rest,
   and it is not on the documentation. Definitely we must improve it..

   BTW, Ogoshi, the compilation should be pretty straight forward, and
   it should work smoothly, so if you have any kind of problem with the
   latest release, please log a bug 

       http://www.0x50.org/bugs/

--

-- 
Greetings, alo.

Re: Many Questions

Alvaro Lopez Ortega wrote:

  (Yep, I do love to reply to myself..)

 >  >> - Is possible that Cherokee working with Chroot in FreeBSD
 >  >
 >  > Yes, it may be simple..... ok, this may require a brief howto in
 >  > documentation site.
 >
 >   Yeah, I ought to improve the documentation.

   Actually, where I said "I ought to" I was meaning "We ought to",
   there is a Wiki for it in which everyone is welcome to contribute :)

     http://www.0x50.org/wiki/

--

-- 
Greetings, alo.