Mailing List Archive: Cherokee: users

FreeBSD Port

Index | Next | Previous | View Threaded

jbozza at mindsites

Jun 18, 2009, 6:14 AM

Post #1 of 20 (1465 views)
Permalink

FreeBSD Port

Hello all,

I'm starting to implement Cherokee on a FreeBSD system and I'd like to talk with anyone else doing the same. The current FreeBSD port is quite behind, so I've modified it (mostly) to handle the latest version. I'd like to talk with anyone else that has done the same to make sure all "fixes" are accounted for. Once I'm good with the updates I'll port it to the PR system in hopes of getting it (fairly) quickly updated in the tree.

You can contact me directly (off the list) to avoid filling the list with lots of OS-Specific talk.

Thanks!

Jaime Bozza

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

frankgroeneveld at gmail

Jun 18, 2009, 6:30 AM

Post #2 of 20 (1432 views)
Permalink

Re: FreeBSD Port [In reply to]

What doesn't work with the "vanilla" source code? I can compile and
use it on Mac OS X without problems...

Frank

2009/6/18 Jaime Bozza <jbozza [at] mindsites>:
> Hello all,
>
> I'm starting to implement Cherokee on a FreeBSD system and I'd like to talk with anyone else doing the same. The current FreeBSD port is quite behind, so I've modified it (mostly) to handle the latest version. I'd like to talk with anyone else that has done the same to make sure all "fixes" are accounted for. Once I'm good with the updates I'll port it to the PR system in hopes of getting it (fairly) quickly updated in the tree.
>
> You can contact me directly (off the list) to avoid filling the list with lots of OS-Specific talk.
>
> Thanks!
>
> Jaime Bozza
>
> _______________________________________________
> Cherokee mailing list
> Cherokee [at] lists
> http://lists.octality.com/listinfo/cherokee
>
_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

jbozza at mindsites

Jun 18, 2009, 6:55 AM

Post #3 of 20 (1438 views)
Permalink

Re: FreeBSD Port [In reply to]

Frank,

It's not just a question of whether or not it compiles when dealing with the FreeBSD port. The port needs to uninstall cleanly, removing all files created by the port. It also needs to handle the different configuration options and depend on other ports if needed. For instance, with or without LDAP/MySQL/GeoIP, etc. Some people may even want to have the option to skip the admin installation. Perhaps they build their configuration on one system and bring the config over, so their production system may not need Python.

Also, there are things in there that are no longer needed. For instance, I believe previously bison was needed for the configuration file. As near as I can tell, Cherokee doesn't need this anymore so it can be removed from the port.

I don't think Cherokee supports the GnuTLS library anymore, so that configuration option needs to be removed.

There are some other things I need to verify - For instance, the port has a requirement on a few gnome items (pkgconfig, gnometarget, etc) that don't seem to be needed anymore.

Regardless - Yes, it seems to compile cleanly and work fine without any patches, but to get updated in the ports system it needs to do a bit more than just compile and run.

Jaime

-----Original Message-----
From: Frank Groeneveld [mailto:frankgroeneveld [at] gmail]
Sent: Thursday, June 18, 2009 8:31 AM
To: Jaime Bozza
Cc: cherokee [at] lists
Subject: Re: [Cherokee] FreeBSD Port

What doesn't work with the "vanilla" source code? I can compile and
use it on Mac OS X without problems...

Frank

2009/6/18 Jaime Bozza <jbozza [at] mindsites>:
> Hello all,
>
> I'm starting to implement Cherokee on a FreeBSD system and I'd like to talk with anyone else doing the same. The current FreeBSD port is quite behind, so I've modified it (mostly) to handle the latest version. I'd like to talk with anyone else that has done the same to make sure all "fixes" are accounted for. Once I'm good with the updates I'll port it to the PR system in hopes of getting it (fairly) quickly updated in the tree.
>
> You can contact me directly (off the list) to avoid filling the list with lots of OS-Specific talk.
>
> Thanks!
>
> Jaime Bozza
>
> _______________________________________________
> Cherokee mailing list
> Cherokee [at] lists
> http://lists.octality.com/listinfo/cherokee
>
_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

superman.jason at gmail

Jun 18, 2009, 7:08 AM

Post #4 of 20 (1431 views)
Permalink

Re: FreeBSD Port [In reply to]

Jaime Bozza <jbozza <at> mindsites.com> writes:

>
> Hello all,
>
> I'm starting to implement Cherokee on a FreeBSD system and I'd like to talk
with anyone else doing the same.
> The current FreeBSD port is quite behind, so I've modified it (mostly) to
handle the latest version. I'd
> like to talk with anyone else that has done the same to make sure all "fixes"
are accounted for. Once I'm good
> with the updates I'll port it to the PR system in hopes of getting it (fairly)
quickly updated in the tree.
>
> You can contact me directly (off the list) to avoid filling the list with lots
of OS-Specific talk.
>
> Thanks!
>
> Jaime Bozza
>

Hi Jaime,

I've been using my own modified ports tree to install the latest cherokee. But
the last couple of times I just was using the same configuration that ports used
and compiling the source directly from cherokee. I found I had to modify the
Makefile in /contrib for it to work. (If I compile with the port, the patches it
applies seem to allow it to compile fine.) I just tried it that way to see if
the port was "out of line", I had to use the rc script from the port though.

A few things I noticed with the port Makefile are:

there no longer is an --enable or --disable-tls flag, so that choice is no
longer valid, it seems configure just looks for libssl/openssl and compiles with
it if it exists and doesn't if it can't find it.

the pkg-plist seems incomplete because when I deinstall the old port to install
a newer one there is always a list of files/folders that were not removed. (The
only thing that should be left behind is any customized files like cherokee.conf
I think.)

Besides that I notice this error on a running cherokee: spawner.c:258: WARNING:
Couldn't unlock spawning semaphore..

I'm running cherokee with the www user & group, but apparently looking through
the commmits the above error was fixed, but maybe FreeBSD works somewhat
differently in this case.

Otherwise cherokee runs great, and I've actually been able to disable apache and
use cherokee exclusively. Tthe new wizards really helped with some more complex
setup I couldn't get to work before.

That's about all the input I have regarding this.

Thanks,
Jason

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

santagada at gmail

Jun 18, 2009, 7:54 AM

Post #5 of 20 (1436 views)
Permalink

Re: FreeBSD Port [In reply to]

On Jun 18, 2009, at 10:55 AM, Jaime Bozza wrote:

> Frank,
>
> It's not just a question of whether or not it compiles when dealing
> with the FreeBSD port. The port needs to uninstall cleanly,
> removing all files created by the port. It also needs to handle the
> different configuration options and depend on other ports if
> needed. For instance, with or without LDAP/MySQL/GeoIP, etc. Some
> people may even want to have the option to skip the admin
> installation. Perhaps they build their configuration on one system
> and bring the config over, so their production system may not need
> Python.

Ahh you meant a port port :). Can you send the url to the resulting
portfile (or whatever it is called on FreeBSD) so that people doing
the macports portfile could use it for guidance?

I don't know if freebsd has default options but I personally would
prefer that by default it depends on python and has the admin (and
probably also LDAP support).

--
Leonardo Santagada
santagada at gmail.com

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

jbozza at mindsites

Jun 18, 2009, 8:12 AM

Post #6 of 20 (1432 views)
Permalink

Re: FreeBSD Port [In reply to]

Not a problem - Once it's cleaned up. :)

FreeBSD does have defaults - Admin/Python would be a default since only advanced users would be interested in something without. I'm not so sure about LDAP though. From a consistency point of view, LDAP isn't installed by default in FreeBSD and isn't a default config for other web software ports. Apache and Lighttpd both have LDAP options that are off by default.

Here's the URL To the current port, which is good for 0.99.2 I think:
http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/cherokee/

Most of it doesn't really apply anymore, which is why I want to get it updated.

Jaime

-----Original Message-----
From: Leonardo Santagada [mailto:santagada [at] gmail]
Sent: Thursday, June 18, 2009 9:54 AM
To: Jaime Bozza
Cc: Frank Groeneveld; cherokee [at] lists
Subject: Re: [Cherokee] FreeBSD Port

On Jun 18, 2009, at 10:55 AM, Jaime Bozza wrote:

> Frank,
>
> It's not just a question of whether or not it compiles when dealing
> with the FreeBSD port. The port needs to uninstall cleanly,
> removing all files created by the port. It also needs to handle the
> different configuration options and depend on other ports if
> needed. For instance, with or without LDAP/MySQL/GeoIP, etc. Some
> people may even want to have the option to skip the admin
> installation. Perhaps they build their configuration on one system
> and bring the config over, so their production system may not need
> Python.

Ahh you meant a port port :). Can you send the url to the resulting
portfile (or whatever it is called on FreeBSD) so that people doing
the macports portfile could use it for guidance?

I don't know if freebsd has default options but I personally would
prefer that by default it depends on python and has the admin (and
probably also LDAP support).

--
Leonardo Santagada
santagada at gmail.com

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

jbozza at mindsites

Jun 18, 2009, 8:33 AM

Post #7 of 20 (1427 views)
Permalink

Re: FreeBSD Port [In reply to]

Jason,

Yes - TLS is no longer an option. Since OpenSSL is part of FreeBSD, this would just be removed.

Some things would need DEPENDS. Right now, the Cherokee Port depends on PCRE and GeoIP. GeoIP can become an option, though I'm thinking this may be defaulted to on. GeoIP isn't necessarily a requirement for many people (I personally don't have a use for it), so it would be nice to disable it since Cherokee's configure allows for it.

The current patches add some additional includes that were definitely required previously. I'm not so sure now, so I have to do a bit more testing.

I'll see if I can figure out the spawner problem. Could you let me know any specifics on the issue? When exactly does the error show up? This is more of a potential bug, so it would be more appropriate to get the fix into Cheroke itself, but if I can duplicate it I may be able to get it fixed.

pkg-plist is very much out of date. Lots of changes have been made to the admin interface, so that will have to be regenerated.

Thanks!

Jaime

-----Original Message-----
From: cherokee-bounces [at] lists [mailto:cherokee-bounces [at] lists] On Behalf Of Jason
Sent: Thursday, June 18, 2009 9:09 AM
To: cherokee [at] lists
Subject: Re: [Cherokee] FreeBSD Port

Jaime Bozza <jbozza <at> mindsites.com> writes:

>
> Hello all,
>
> I'm starting to implement Cherokee on a FreeBSD system and I'd like to talk
with anyone else doing the same.
> The current FreeBSD port is quite behind, so I've modified it (mostly) to
handle the latest version. I'd
> like to talk with anyone else that has done the same to make sure all "fixes"
are accounted for. Once I'm good
> with the updates I'll port it to the PR system in hopes of getting it (fairly)
quickly updated in the tree.
>
> You can contact me directly (off the list) to avoid filling the list with lots
of OS-Specific talk.
>
> Thanks!
>
> Jaime Bozza
>

Hi Jaime,

I've been using my own modified ports tree to install the latest cherokee. But
the last couple of times I just was using the same configuration that ports used
and compiling the source directly from cherokee. I found I had to modify the
Makefile in /contrib for it to work. (If I compile with the port, the patches it
applies seem to allow it to compile fine.) I just tried it that way to see if
the port was "out of line", I had to use the rc script from the port though.

A few things I noticed with the port Makefile are:

there no longer is an --enable or --disable-tls flag, so that choice is no
longer valid, it seems configure just looks for libssl/openssl and compiles with
it if it exists and doesn't if it can't find it.

the pkg-plist seems incomplete because when I deinstall the old port to install
a newer one there is always a list of files/folders that were not removed. (The
only thing that should be left behind is any customized files like cherokee.conf
I think.)

Besides that I notice this error on a running cherokee: spawner.c:258: WARNING:
Couldn't unlock spawning semaphore..

I'm running cherokee with the www user & group, but apparently looking through
the commmits the above error was fixed, but maybe FreeBSD works somewhat
differently in this case.

Otherwise cherokee runs great, and I've actually been able to disable apache and
use cherokee exclusively. Tthe new wizards really helped with some more complex
setup I couldn't get to work before.

That's about all the input I have regarding this.

Thanks,
Jason

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee
_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

superman.jason at gmail

Jun 18, 2009, 9:50 AM

Post #8 of 20 (1427 views)
Permalink

Re: FreeBSD Port [In reply to]

Jaime Bozza <jbozza <at> mindsites.com> writes:

>
> Jason,
>
> Yes - TLS is no longer an option. Since OpenSSL is part of FreeBSD, this
would just be removed.
>
> Some things would need DEPENDS. Right now, the Cherokee Port depends on PCRE
and GeoIP. GeoIP can become an
> option, though I'm thinking this may be defaulted to on. GeoIP isn't
necessarily a requirement for many
> people (I personally don't have a use for it), so it would be nice to disable
it since Cherokee's configure
> allows for it.
>
> The current patches add some additional includes that were definitely required
previously. I'm not so
> sure now, so I have to do a bit more testing.
>
> I'll see if I can figure out the spawner problem. Could you let me know any
specifics on the issue? When
> exactly does the error show up? This is more of a potential bug, so it would
be more appropriate to get the fix
> into Cheroke itself, but if I can duplicate it I may be able to get it fixed.
>
> pkg-plist is very much out of date. Lots of changes have been made to the
admin interface, so that will have to
> be regenerated.
>
> Thanks!
>
> Jaime

Hi Jaime,

Actually looking more closely at the spawning semaphore error...it calls it a
warning. I think it just shows up after a server restart when the first php page
is called. It probably looks for a running instance of php-cgi, and not finding
one causes the warning. After the first php call the warning never shows again,
so I think that is what it's all about.

You can see it if you stop cherokee, and start it from a CLI and keep it
attached, or I also see it as a console message when I restart it with the rc
script via ssh and then access a php page on the server.

As for GeoIP, yes I don't think it's something I would generally need either,
but it would be nice to have the option available.

I also notice that the debian package has a separate package for the streaming
module, so I wonder if that is another option available to config.

And yes as far as I can see the port is only at 0.99.2, and only because I sent
a nudge message to the current maintainer. I think he is either really busy, has
lost interest in it, or has gone off the grid.
(http://www.freshports.org/www/cherokee/)

On the tls note, FreeBSD only has openssl 0.9.8e in the base system which
doesn't have SNI, therefore per virtual host SSL doesn't work. I tried updating
using the port (0.9.8k), but for some reason a recompiled cherokee doesn't seem
pick up the new version. I read in some the posts I could find that the port
overwrites the base version, but it doesn't update the version number in the
system although openssl is actually updated. Maybe cherokee reads the version
that openssl returns rather than the actual version it is and disables SNI. It
would be nice to get SNI working as that is a major reason to switch to cherokee
on top of the other great reasons! Maybe someone has figured this openssl
base/port thing already?

Jason

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

jbozza at mindsites

Jun 18, 2009, 11:05 AM

Post #9 of 20 (1432 views)
Permalink

Re: FreeBSD Port [In reply to]

> Actually looking more closely at the spawning semaphore error...it
> calls it a warning. I think it just shows up after a server restart
> when the first php page is called. It probably looks for a running
> instance of php-cgi, and not finding one causes the warning. After
> the first php call the warning never shows again, so I think that
> is what it's all about.
>
> You can see it if you stop cherokee, and start it from a CLI and keep
> it attached, or I also see it as a console message when I restart it
> with the rc script via ssh and then access a php page on the server.

I'll check that out - thanks for the details.

> As for GeoIP, yes I don't think it's something I would generally need
> either, but it would be nice to have the option available.
>
> I also notice that the debian package has a separate package for the
> streaming module, so I wonder if that is another option available to
> config.

Yes - It's in there as an option now, defaults to yes for POLA. Same thing with Admin interface. FFMPEG will be an option (defaults to no) that depends on the ffmpeg port.

PCRE support defaults to using the port, but there seems to be an option to use the built-in library, so I added that as an option (defaults to no).

> And yes as far as I can see the port is only at 0.99.2, and only
> because I sent a nudge message to the current maintainer. I think
> he is either really busy, has lost interest in it, or has gone off
> the grid. (http://www.freshports.org/www/cherokee/)

I tried contacting him as well when I originally started testing Cherokee. Never received a response from him, even though I had the port mostly updated.

> On the tls note, FreeBSD only has openssl 0.9.8e in the base system
> which doesn't have SNI, therefore per virtual host SSL doesn't work.
> I tried updating using the port (0.9.8k), but for some reason a
> recompiled cherokee doesn't seem pick up the new version. I read in
> some the posts I could find that the port overwrites the base
> version, but it doesn't update the version number in the system
> although openssl is actually updated. Maybe cherokee reads the
> version that openssl returns rather than the actual version it is
> and disables SNI. It would be nice to get SNI working as that is
> a major reason to switch to cherokee on top of the other great
> reasons! Maybe someone has figured this openssl base/port thing
> already?

By default, the OpenSSL port doesn't overwrite the base OpenSSL. You need to turn a few knobs for that. First, you need to have WITH_OPENSSL_BASE=yes in your /etc/make.conf and also place WITHOUT_OPENSSL=true in /etc/src.conf if you regularly update your FreeBSD system from the source. This is correct for FreeBSD 7.x, so if you're using <7.x, check the src READMEs for specifics.

After that, you'll need to recompile Cherokee to catch the new version. Cherokee just checks for SSL_CTRL_SET_TLSEXT_HOSTNAME, so if that's set in the include files, it should work fine. If it isn't, you may have two versions of ssl.h on your system, one from the base and one from the port. The system will catch the base version first.

On that note, 0.9.8k was just importing into HEAD, so you can always tried finding out if it'll be backported to RELENG_7. Unlikely, but it's always possible!

Jaime

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

superman.jason at gmail

Jun 18, 2009, 11:28 AM

Post #10 of 20 (1437 views)
Permalink

Re: FreeBSD Port [In reply to]

Jaime Bozza <jbozza <at> mindsites.com> writes:

>
> > Actually looking more closely at the spawning semaphore error...it
> > calls it a warning. I think it just shows up after a server restart
> > when the first php page is called. It probably looks for a running
> > instance of php-cgi, and not finding one causes the warning. After
> > the first php call the warning never shows again, so I think that
> > is what it's all about.
> >
> > You can see it if you stop cherokee, and start it from a CLI and keep
> > it attached, or I also see it as a console message when I restart it
> > with the rc script via ssh and then access a php page on the server.
>
> I'll check that out - thanks for the details.
>
> > As for GeoIP, yes I don't think it's something I would generally need
> > either, but it would be nice to have the option available.
> >
> > I also notice that the debian package has a separate package for the
> > streaming module, so I wonder if that is another option available to
> > config.
>
> Yes - It's in there as an option now, defaults to yes for POLA. Same thing
with Admin interface. FFMPEG will be
> an option (defaults to no) that depends on the ffmpeg port.
>
> PCRE support defaults to using the port, but there seems to be an option to
use the built-in library, so I
> added that as an option (defaults to no).
>
> > And yes as far as I can see the port is only at 0.99.2, and only
> > because I sent a nudge message to the current maintainer. I think
> > he is either really busy, has lost interest in it, or has gone off
> > the grid. (http://www.freshports.org/www/cherokee/)
>
> I tried contacting him as well when I originally started testing Cherokee.
Never received a response from
> him, even though I had the port mostly updated.
>
> > On the tls note, FreeBSD only has openssl 0.9.8e in the base system
> > which doesn't have SNI, therefore per virtual host SSL doesn't work.
> > I tried updating using the port (0.9.8k), but for some reason a
> > recompiled cherokee doesn't seem pick up the new version. I read in
> > some the posts I could find that the port overwrites the base
> > version, but it doesn't update the version number in the system
> > although openssl is actually updated. Maybe cherokee reads the
> > version that openssl returns rather than the actual version it is
> > and disables SNI. It would be nice to get SNI working as that is
> > a major reason to switch to cherokee on top of the other great
> > reasons! Maybe someone has figured this openssl base/port thing
> > already?
>
> By default, the OpenSSL port doesn't overwrite the base OpenSSL. You need to
turn a few knobs for that.
> First, you need to have WITH_OPENSSL_BASE=yes in your /etc/make.conf and also
place
> WITHOUT_OPENSSL=true in /etc/src.conf if you regularly update your FreeBSD
system from the source.
> This is correct for FreeBSD 7.x, so if you're using <7.x, check the src
READMEs for specifics.
>
> After that, you'll need to recompile Cherokee to catch the new version.
Cherokee just checks for
> SSL_CTRL_SET_TLSEXT_HOSTNAME, so if that's set in the include files, it should
work fine. If it isn't,
> you may have two versions of ssl.h on your system, one from the base and one
from the port. The system will
> catch the base version first.
>
> On that note, 0.9.8k was just importing into HEAD, so you can always tried
finding out if it'll be backported
> to RELENG_7. Unlikely, but it's always possible!
>
> Jaime
>

Thanks for the info. I did find info on those knobs in my research, and I did
set them. However the first time I just installed the port without those
settings as it was before I found that. So the next time I uninstalled the port
then reinstalled with those set. Maybe that affected it a bit.

How can I manually check the output of that SSL_CTRL_SET_TLSEXT_HOSTNAME?
Looking around I did find 2 ssl.h one in /usr/include/openssl/ssl.h and another
in /usr/local/include/openssl/ssl.h. I'll see what I can do to rectify this.

Oh, and I just checked with freebsd-update and nothing new yet with regard to
openssl. (I used to go with updating from source, but I wanted to keep things
simpler for this production system this time around.)

Thanks for your help, looking forward to the up-to-date port!

Jason

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

jbozza at mindsites

Jun 18, 2009, 11:42 AM

Post #11 of 20 (1429 views)
Permalink

Re: FreeBSD Port [In reply to]

> How can I manually check the output of that SSL_CTRL_SET_TLSEXT_HOSTNAME?
> Looking around I did find 2 ssl.h one in /usr/include/openssl/ssl.h and
> another in /usr/local/include/openssl/ssl.h. I'll see what I can do to
> rectify this.

There's no output - it's either defined or not. If you have two ssl.h files, (one in /usr/local), then the port installed outside of the base system. You'll need to uninstall the port (double-check that it removed everything from /usr/local) and reinstall.

Also, freebsd-update may clobber your base openssl again if there's a security patch to the openssl files after you use the port to overwrite the base. I'm not completely familiar with freebsd-update so you may want to check for settings there as well.

Jaime

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

superman.jason at gmail

Jun 18, 2009, 11:47 AM

Post #12 of 20 (1428 views)
Permalink

Re: FreeBSD Port [In reply to]

Jaime Bozza <jbozza <at> mindsites.com> writes:

>
> > How can I manually check the output of that SSL_CTRL_SET_TLSEXT_HOSTNAME?
> > Looking around I did find 2 ssl.h one in /usr/include/openssl/ssl.h and
> > another in /usr/local/include/openssl/ssl.h. I'll see what I can do to
> > rectify this.
>
> There's no output - it's either defined or not. If you have two ssl.h files,
(one in /usr/local), then the
> port installed outside of the base system. You'll need to uninstall the port
(double-check that it
> removed everything from /usr/local) and reinstall.
>
> Also, freebsd-update may clobber your base openssl again if there's a security
patch to the openssl files
> after you use the port to overwrite the base. I'm not completely familiar
with freebsd-update so you may
> want to check for settings there as well.
>
> Jaime
>

I just tried deinstalling. It did remove the /usr/local/include/openssl folder
completely, but even with the make.conf knob when I reinstalled from the port it
recreated the /usr/local/include/openssl. I guess I'll have to track that down.

Thanks again,
Jason

PS: If you want to send me your updated port I'd be glad to try it out!

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

jbozza at mindsites

Jun 18, 2009, 1:27 PM

Post #13 of 20 (1432 views)
Permalink

Re: FreeBSD Port [In reply to]

> I just tried deinstalling. It did remove the /usr/local/include/openssl
> folder completely, but even with the make.conf knob when I reinstalled
> from the port it recreated the /usr/local/include/openssl. I guess I'll
> have to track that down.

Jason,

I looked further into it and it seems that the openssl port no longer has the option to overwrite the base openssl. That leaves you with forcing Cherokee to somehow follow the port version. I'll see if that's something I can work into the port. Right now I'm going to leave it alone though.

I'm about done testing my changes. I should have something to test by tomorrow, minus the openssl issue.

If you could, try removing WITH_OPENSSL_BASE from your make.conf and replace it with WITH_OPENSSL_PORT=yes. Then reinstall both the openssl port and the Cherokee port. Let me know if that changes anything.

Jaime

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

superman.jason at gmail

Jun 18, 2009, 1:52 PM

Post #14 of 20 (1431 views)
Permalink

Re: FreeBSD Port [In reply to]

Jaime Bozza <jbozza <at> mindsites.com> writes:

> If you could, try removing WITH_OPENSSL_BASE from your make.conf and replace
it with
> WITH_OPENSSL_PORT=yes. Then reinstall both the openssl port and the Cherokee
port. Let me know if that
> changes anything.
>
> Jaime
>

Okay, tried it. I get this error when I try to start it.

plugin_loader.c:194:
ERROR: dlopen(/usr/local/lib/cherokee/libplugin_libssl.so):
/usr/local/lib/cherokee/libplugin_libssl.so:
Undefined symbol "SSL_get_servername"
plugin_loader.c:363:
ERROR: Can't open "libssl" module
Couldn't read the config file:
/usr/local/etc/cherokee/cherokee.conf

I'm using my modified port folder,
but all that is modified presently is the version number of the program, so that
it's using 0.99.17.

I don't think it's reading the openssl knob from make.conf.

In the meantime do you know what flag I can use with configure to make it use
the openssl from ports?

Thanks,
Jason

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

superman.jason at gmail

Jun 18, 2009, 2:30 PM

Post #15 of 20 (1434 views)
Permalink

Re: FreeBSD Port [In reply to]

Jason <superman.jason <at> gmail.com> writes:

Jaime,

Okay, I deinstalled the openssl port but left the make.conf
WITH_OPENSSL_PORT=yes knob and proved myself wrong. It definitely is reading the
knob, because this time when I tried to reinstall cherokee it wanted to install
openssl from ports first.

I removed the knob and reinstalled cherokee with just the base openssl and it
worked fine. Must be something it doesn't like with the ports version. Too bad,
SSL w/SNI is a feature that I would really like to have working.

Thanks again,
Jason

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

jbozza at mindsites

Jun 18, 2009, 7:40 PM

Post #16 of 20 (1437 views)
Permalink

Re: FreeBSD Port [In reply to]

> Okay, tried it. I get this error when I try to start it.
>
> plugin_loader.c:194:
> ERROR: dlopen(/usr/local/lib/cherokee/libplugin_libssl.so):
> /usr/local/lib/cherokee/libplugin_libssl.so:
> Undefined symbol "SSL_get_servername"
> plugin_loader.c:363:
> ERROR: Can't open "libssl" module
> Couldn't read the config file:
> /usr/local/etc/cherokee/cherokee.conf

I was able to duplicate the error. I was also able to fix it. You need two items in /etc/make.conf:

USE_OPENSSL_RPATH=yes
USE_OPENSSL_PORT=yes

Recompile Cherokee after having both of these and Cherokee should compile and link against the OpenSSL port. Without the RPATH, it'll use the new include file, but link against the base port, causing a mismatch.

This was only tested with my updated port file, so you may want to try with that.

Jaime

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

superman.jason at gmail

Jun 19, 2009, 2:59 PM

Post #17 of 20 (1426 views)
Permalink

Re: FreeBSD Port [In reply to]

Jaime Bozza <jbozza <at> mindsites.com> writes:

> I was able to duplicate the error. I was also able to fix it.
> You need two items in /etc/make.conf:
>
> USE_OPENSSL_RPATH=yes
> USE_OPENSSL_PORT=yes
>
> Recompile Cherokee after having both of these and Cherokee should compile
> and link against the OpenSSL port.
> Without the RPATH, it'll use the new include file, but link against the
>base port, causing a mismatch.
>
> This was only tested with my updated port file, so you may want to try with
>that.
>
> Jaime
>

Dude, you're awesome!! That totally solved it! Thanks a million! Nice to see
someone with some knowledge finally taking an interest in cherokee on FreeBSD!

Thanks again,
Jason

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

jbozza at mindsites

Jun 19, 2009, 3:25 PM

Post #18 of 20 (1447 views)
Permalink

Re: FreeBSD Port [In reply to]

> Dude, you're awesome!! That totally solved it! Thanks a million! Nice
> to see someone with some knowledge finally taking an interest in
> cherokee on FreeBSD!

Not a problem! The OpenSSL thing has always been a bit tricky. I actually learned something new myself, so everyone wins!

Jaime

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

superman.jason at gmail

Jul 11, 2009, 9:18 AM

Post #19 of 20 (1316 views)
Permalink

Re: FreeBSD Port [In reply to]

Jaime Bozza <jbozza <at> mindsites.com> writes:

> To all FreeBSD users,
>
> Â
>
> As of this morning, the FreeBSD port has finally been updated
> to 0.99.20.Â Â I want to thank everyone for their help in getting this
> done!Â Â You should now be able to sync your ports tree instead of
> manually building.
>
> Jaime

Hi Jaime,

Thanks for all your hard work on this. I just updated all my ports and cherokee
built & ran perfectly!

Thanks again,
Jason

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

alvaro at gnu

Jul 11, 2009, 9:31 AM

Post #20 of 20 (1318 views)
Permalink

Re: FreeBSD Port [In reply to]

On 11-jul-09, at 18:18, Jason wrote:

>> As of this morning, the FreeBSD port has finally been updated
>> to 0.99.20. I want to thank everyone for their help in getting this
>> done! You should now be able to sync your ports tree instead of
>> manually building.
>>
>
> Thanks for all your hard work on this. I just updated all my ports
> and cherokee
> built & ran perfectly!

Sweet!
Thanks for a great job :-)

--
Greetings, alo
http://www.alobbs.com/

_______________________________________________
Cherokee mailing list
Cherokee [at] lists
http://lists.octality.com/listinfo/cherokee

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads