You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rivet-dev@tcl.apache.org by János Holányi <cs...@lme.linux.hu> on 2005/07/12 15:41:54 UTC
Debian - apache-ssl - Rivet
Hello,
I'd like to know how I can build an apache-ssl-enabled Debian package of Rivet
using standard Debian building environment (Sarge) and tools.
Any ideas?
Thanks *a lot*.
Best regards,
Csani
--
Debian Project (http://www.debian.org/)
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Debian - apache-ssl - Rivet
Posted by János Holányi <cs...@lme.linux.hu>.
On Mon, 18 Jul 2005 23:18:15 +0200, David N. Welton wrote
> János Holányi wrote:
>
> > What do you think the best way to enable apache-ssl support in the rivet
> > package is?
>
> mod_ssl :-)
>
> Requires no recompiling and fiddling...
Yes, you are right, but that's not apache-ssl support (it's mod_ssl support ;))
Regard,
Csani
--
Debian Project (http://www.debian.org/)
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Debian - apache-ssl - Rivet
Posted by "David N. Welton" <da...@dedasys.com>.
János Holányi wrote:
> What do you think the best way to enable apache-ssl support in the rivet
> package is?
mod_ssl :-)
Requires no recompiling and fiddling...
> Well - if I may ;) - logging to Apache's own error.log is also good.
> There could also be a Rivet global and per virtual host directive to set the
> error log file name to, which would default to empty (which in turn would log
> to the Apache error.log).
Sure, that's doable too... Seems more complex, though, and I'm a big
fan of "as simple as possible".
> By the way, are you planning to support apache2 in the near future?
Realistically, probably not. I have some ideas on how to make it work
with the threaded nasties that lurk for the unwary programmer, but it's
bound to be complicated work with some surprises along the way. And all
things considered...2.0 is nice, but 1.3 works fine too.
--
David N. Welton
- http://www.dedasys.com/davidw/
Apache, Linux, Tcl Consulting
- http://www.dedasys.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Debian - apache-ssl - Rivet
Posted by János Holányi <cs...@lme.linux.hu>.
On Sun, 17 Jul 2005 10:05:13 +0200, David N. Welton wrote
> János Holányi wrote:
> > On Fri, 15 Jul 2005 22:56:48 +0200, David N. Welton wrote
> >
> >>János Holányi wrote:
> Err... I'm not clear on what you would copy where...?
Ah, forget that. Sorry, that was an earlier stage when I was investigating why
rivet didn't work on apache-ssl and I created /usr/lib/apache-ssl/1.3 and
moved the rivet mod files over there ;)
What do you think the best way to enable apache-ssl support in the rivet
package is? Shipping modules within and detect&configure both servers
accordingly (the available ones) or creating a different package (rivet-ssl)?
Let's discuss this over and I'll try to send you a patch for the final solution.
> > Let me grab the opportunity to suggest an important change to rivet/init.tcl
> > I'd be curious what you think about it:
> >
> > --- rivet-0.5.0/rivet/init.tcl 2004-02-24 11:24:32.000000000 +0100
> > +++ /usr/lib/rivet0.5.0/init.tcl 2005-07-17 09:14:39.363021232 +0200
> > @@ -44,11 +44,11 @@
> > global errorInfo
> > global errorOutbuf
> >
> > - puts <PRE>
> > - puts "<HR>$errorInfo<HR>"
> > - puts "<P><B>OUTPUT BUFFER:</B></P>"
> > - puts $errorOutbuf
> > - puts </PRE>
> > + set logfile /var/log/apache-ssl/rivet-error.log
> > + puts "<pre>Error. Check log file.</pre>"
> > + set fd [open $logfile w]
> > + puts $fd "ERROR:\n\n$errorInfo\n---\nOUTPUT BUFFER:\n\n$errorOutbuf"
> > + close $fd
> > }
>
> Could be potentially very useful... not a bad idea at all. I don't
> think setting the log file location from in there is correct, and
> perhaps it would be best to simply take advantage of the fact that
> stderr goes to Apache's own error.log?
>
> Other opinions?
Well - if I may ;) - logging to Apache's own error.log is also good.
There could also be a Rivet global and per virtual host directive to set the
error log file name to, which would default to empty (which in turn would log
to the Apache error.log).
By the way, are you planning to support apache2 in the near future?
Best,
Csani
--
Debian Project (http://www.debian.org/)
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Debian - apache-ssl - Rivet
Posted by "David N. Welton" <da...@dedasys.com>.
János Holányi wrote:
> On Fri, 15 Jul 2005 22:56:48 +0200, David N. Welton wrote
>
>>János Holányi wrote:
>>
>>>Could it be gcc-4.0.12 (gonna try with gcc-3.4 ASAIC - any versions you'd
>>>suggest trying out?)?
>>
>>Did 3.4 work out any better?
>
>
> Yes, it did!
> It compiled (a few warnings here and there), it installed and apparently it
> worked.
Good. Strange that 4.0 has problems... I will have to investigate:-/
> Although some file re-organization could be done I feel...
> /usr/lib/apache/1.3 is out of apache-ssl focus.
> I copied all three to /usr/lib/apache-ssl/1.3 and configured httpd.conf and
> modules.conf accordingly.
Err... I'm not clear on what you would copy where...?
> Let me grab the opportunity to suggest an important change to rivet/init.tcl
> I'd be curious what you think about it:
>
> --- rivet-0.5.0/rivet/init.tcl 2004-02-24 11:24:32.000000000 +0100
> +++ /usr/lib/rivet0.5.0/init.tcl 2005-07-17 09:14:39.363021232 +0200
> @@ -44,11 +44,11 @@
> global errorInfo
> global errorOutbuf
>
> - puts <PRE>
> - puts "<HR>$errorInfo<HR>"
> - puts "<P><B>OUTPUT BUFFER:</B></P>"
> - puts $errorOutbuf
> - puts </PRE>
> + set logfile /var/log/apache-ssl/rivet-error.log
> + puts "<pre>Error. Check log file.</pre>"
> + set fd [open $logfile w]
> + puts $fd "ERROR:\n\n$errorInfo\n---\nOUTPUT BUFFER:\n\n$errorOutbuf"
> + close $fd
> }
Could be potentially very useful... not a bad idea at all. I don't
think setting the log file location from in there is correct, and
perhaps it would be best to simply take advantage of the fact that
stderr goes to Apache's own error.log?
Other opinions?
--
David N. Welton
- http://www.dedasys.com/davidw/
Apache, Linux, Tcl Consulting
- http://www.dedasys.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Debian - apache-ssl - Rivet
Posted by János Holányi <cs...@lme.linux.hu>.
On Fri, 15 Jul 2005 22:56:48 +0200, David N. Welton wrote
> János Holányi wrote:
> > Could it be gcc-4.0.12 (gonna try with gcc-3.4 ASAIC - any versions you'd
> > suggest trying out?)?
>
> Did 3.4 work out any better?
Yes, it did!
It compiled (a few warnings here and there), it installed and apparently it
worked.
Although some file re-organization could be done I feel...
/usr/lib/apache/1.3 is out of apache-ssl focus.
I copied all three to /usr/lib/apache-ssl/1.3 and configured httpd.conf and
modules.conf accordingly.
Let me grab the opportunity to suggest an important change to rivet/init.tcl
I'd be curious what you think about it:
--- rivet-0.5.0/rivet/init.tcl 2004-02-24 11:24:32.000000000 +0100
+++ /usr/lib/rivet0.5.0/init.tcl 2005-07-17 09:14:39.363021232 +0200
@@ -44,11 +44,11 @@
global errorInfo
global errorOutbuf
- puts <PRE>
- puts "<HR>$errorInfo<HR>"
- puts "<P><B>OUTPUT BUFFER:</B></P>"
- puts $errorOutbuf
- puts </PRE>
+ set logfile /var/log/apache-ssl/rivet-error.log
+ puts "<pre>Error. Check log file.</pre>"
+ set fd [open $logfile w]
+ puts $fd "ERROR:\n\n$errorInfo\n---\nOUTPUT BUFFER:\n\n$errorOutbuf"
+ close $fd
}
###
Best regards,
János
--
Debian Project (http://www.debian.org/)
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Debian - apache-ssl - Rivet
Posted by "David N. Welton" <da...@dedasys.com>.
János Holányi wrote:
> Could it be gcc-4.0.12 (gonna try with gcc-3.4 ASAIC - any versions you'd
> suggest trying out?)?
Did 3.4 work out any better?
--
David N. Welton
- http://www.dedasys.com/davidw/
Apache, Linux, Tcl Consulting
- http://www.dedasys.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Debian - apache-ssl - Rivet
Posted by János Holányi <cs...@lme.linux.hu>.
On Thu, 14 Jul 2005 15:03:48 +0200, David N. Welton wrote
> János Holányi wrote:
>
> > rivetCore.c: In function 'Rivet_Upload':
> > rivetCore.c:643: error: invalid lvalue in assignment
> > make[2]: *** [mod_rivet_la-rivetCore.lo] Error 1
> > make[2]: Leaving directory `/home/root/rivet-0.5.0/src'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/home/root/rivet-0.5.0'
> > make: *** [build-stamp] Error 2
>
> That's weird... I have that line as being:
>
> (CONST84 char *)channelname = Tcl_GetChannelName(chan);
>
> So I'm not really seeing how that line could go wrong... Is that the
> same line you have, just to double check?
Yes, it is literally the same as mine over here:
(CONST84 char *)channelname = Tcl_GetChannelName(chan);
Could it be gcc-4.0.12 (gonna try with gcc-3.4 ASAIC - any versions you'd
suggest trying out?)?
configure:2411: checking for gcc
configure:2427: found /usr/bin/gcc
configure:2437: result: gcc
configure:2681: checking for C compiler version
configure:2684: gcc --version </dev/null >&5
gcc (GCC) 4.0.1 20050701 (prerelease) (Debian 4.0.0-12)
Copyright (C) 2005 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:2687: $? = 0
configure:2689: gcc -v </dev/null >&5
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v
--enable-languages=c,c++,java,f95,objc,ada,treelang --prefix=/usr
--enable-shared --with-system-zlib --libexecdir=/usr/lib
Thread model: posix
gcc version 4.0.1 20050701 (prerelease) (Debian 4.0.0-12)
configure:2692: $? = 0
configure:2694: gcc -V </dev/null >&5
gcc: '-V' option must have argument
--
Debian Project (http://www.debian.org/)
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Debian - apache-ssl - Rivet
Posted by "David N. Welton" <da...@dedasys.com>.
János Holányi wrote:
> rivetCore.c: In function 'Rivet_Upload':
> rivetCore.c:643: error: invalid lvalue in assignment
> make[2]: *** [mod_rivet_la-rivetCore.lo] Error 1
> make[2]: Leaving directory `/home/root/rivet-0.5.0/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/root/rivet-0.5.0'
> make: *** [build-stamp] Error 2
That's weird... I have that line as being:
(CONST84 char *)channelname = Tcl_GetChannelName(chan);
So I'm not really seeing how that line could go wrong... Is that the
same line you have, just to double check?
--
David N. Welton
- http://www.dedasys.com/davidw/
Apache, Linux, Tcl Consulting
- http://www.dedasys.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Debian - apache-ssl - Rivet
Posted by János Holányi <cs...@lme.linux.hu>.
Hello all,
I was able to get his far:
holanyij:~# dpkg -S `which apxs`
apache-dev: /usr/bin/apxs
holanyij:~# dpkg -S `which apxs-ssl`
apache-dev: /usr/bin/apxs-ssl
holanyij:~# apt-get build-dep rivet
Reading package lists... Done
Building dependency tree... Done
0 upgraded, 0 newly installed, 0 to remove and 120 not upgraded.
holanyij:~# apt-get source rivet
Reading package lists... Done
Building dependency tree... Done
Need to get 882kB of source archives.
Get:1 http://ftp.debian.org sid/main rivet 0.5.0-3 (dsc) [523B]
Get:2 http://ftp.debian.org sid/main rivet 0.5.0-3 (tar) [882kB]
Fetched 2B in 0s (2B/s)
Skipping unpack of already unpacked source in rivet-0.5.0
holanyij:~# cd rivet-0.5.0/
holanyij:~/rivet-0.5.0# diff debian/rules~ debian/rules
12c12
< ./configure --with-tcl=/usr/lib/tcl$(TCL_VERSION)/
--with-apxs=/usr/bin/apxs --enable-threads
--with-tclsh=/usr/bin/tclsh$(TCL_VERSION)
---
> ./configure --with-tcl=/usr/lib/tcl$(TCL_VERSION)/
--with-apxs=/usr/bin/apxs-ssl --enable-threads
--with-tclsh=/usr/bin/tclsh$(TCL_VERSION)
36c36
< debian/tmp/`apxs -q LIBEXECDIR`/500mod_rivet.info
---
> debian/tmp/`apxs-ssl -q LIBEXECDIR`/500mod_rivet.info
holanyij:~/rivet-0.5.0# ./debian/rules binary
dh_testdir
/usr/bin/make
make[1]: Entering directory `/home/root/rivet-0.5.0'
Making all in src
make[2]: Entering directory `/home/root/rivet-0.5.0/src'
if /bin/sh ../libtool --mode=compile gcc -pipe -DPACKAGE_NAME=\"Rivet\"
-DPACKAGE_TARNAME=\"rivet\" -DPACKAGE_VERSION=\"0.5.0\"
-DPACKAGE_STRING=\"Rivet\ 0.5.0\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"rivet\"
-DVERSION=\"0.5.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1
-DHAVE_SYS_PARAM_H=1 -DHAVE_DLFCN_H=1 -DUSE_THREAD_ALLOC=1 -D_REENTRANT=1
-D_THREAD_SAFE=1 -DHAVE_PTHREAD_ATTR_SETSTACKSIZE=1 -DHAVE_READDIR_R=1
-DTCL_THREADS=1 -D_ISOC99_SOURCE= -D_LARGEFILE64_SOURCE=
-DTCL_WIDE_INT_TYPE=long\ long -DHAVE_STRUCT_STAT64=1 -DHAVE_TYPE_OFF64_T=1
-DNAMEOFEXECUTABLE=\"/usr/bin/tclsh8.4\" -I. -I.
-I"/usr/include/tcl8.4/tcl-private/generic" -DLINUX=22 -DEAPI
-DTARGET="apache" -DHAVE_SET_DUMPABLE -DDB_DBM_HSEARCH=1
-DDEV_RANDOM=/dev/random -DUSE_HSREGEX -DAPACHE_SSL -O1 -g -Wall
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/apache-1.3
-DSTART_TAG='"<?"' -DEND_TAG='"?>"' -O2 -Wall -Wno-implicit-int -fPIC -MT
mod_rivet_la-rivetCore.lo -MD -MP -MF ".deps/mod_rivet_la-rivetCore.Tpo" -c -o
mod_rivet_la-rivetCore.lo `test -f 'rivetCore.c' || echo './'`rivetCore.c; \
then mv -f ".deps/mod_rivet_la-rivetCore.Tpo"
".deps/mod_rivet_la-rivetCore.Plo"; else rm -f
".deps/mod_rivet_la-rivetCore.Tpo"; exit 1; fi
gcc -pipe -DPACKAGE_NAME=\"Rivet\" -DPACKAGE_TARNAME=\"rivet\"
-DPACKAGE_VERSION=\"0.5.0\" "-DPACKAGE_STRING=\"Rivet 0.5.0\""
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"rivet\" -DVERSION=\"0.5.0\"
-DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1
-DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1
-DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_PARAM_H=1
-DHAVE_DLFCN_H=1 -DUSE_THREAD_ALLOC=1 -D_REENTRANT=1 -D_THREAD_SAFE=1
-DHAVE_PTHREAD_ATTR_SETSTACKSIZE=1 -DHAVE_READDIR_R=1 -DTCL_THREADS=1
-D_ISOC99_SOURCE= -D_LARGEFILE64_SOURCE= "-DTCL_WIDE_INT_TYPE=long long"
-DHAVE_STRUCT_STAT64=1 -DHAVE_TYPE_OFF64_T=1
-DNAMEOFEXECUTABLE=\"/usr/bin/tclsh8.4\" -I. -I.
-I/usr/include/tcl8.4/tcl-private/generic -DLINUX=22 -DEAPI -DTARGET=apache
-DHAVE_SET_DUMPABLE -DDB_DBM_HSEARCH=1 -DDEV_RANDOM=/dev/random -DUSE_HSREGEX
-DAPACHE_SSL -O1 -g -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I/usr/include/apache-1.3 "-DSTART_TAG=\"<?\"" "-DEND_TAG=\"?>\"" -O2 -Wall
-Wno-implicit-int -fPIC -MT mod_rivet_la-rivetCore.lo -MD -MP -MF
.deps/mod_rivet_la-rivetCore.Tpo -c rivetCore.c -fPIC -DPIC -o
.libs/mod_rivet_la-rivetCore.o
In file included from /usr/include/sys/sem.h:28,
from /usr/include/apache-1.3/ap_config.h:463,
from /usr/include/apache-1.3/httpd.h:29,
from rivetCore.c:27:
/usr/include/sys/ipc.h:25:3: warning: #warning "Files using this header must
be compiled with _SVID_SOURCE or _XOPEN_SOURCE"
rivetCore.c: In function 'Rivet_Upload':
rivetCore.c:643: error: invalid lvalue in assignment
make[2]: *** [mod_rivet_la-rivetCore.lo] Error 1
make[2]: Leaving directory `/home/root/rivet-0.5.0/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/root/rivet-0.5.0'
make: *** [build-stamp] Error 2
What next?
Regs,
Csani
On Wed, 13 Jul 2005 13:35:02 +0200, David N. Welton wrote
> János Holányi wrote:
> > Hello,
> >
> > I'd like to know how I can build an apache-ssl-enabled Debian package of Rivet
> > using standard Debian building environment (Sarge) and tools.
> >
> > Any ideas?
>
> Well, I think the configuration information for Apache SSL should be
> captured by the apxs that it ships with. So what you want to do is find
> where its apxs script resides, and then, when you configure Rivet, do
> something like:
>
> --with-apxs=/usr/bin/apxs-ssl
>
> That line is, for Debian, in debian/rules.
>
> See if that works and let us know, ok?
>
> --
> David N. Welton
> - http://www.dedasys.com/davidw/
>
> Apache, Linux, Tcl Consulting
> - http://www.dedasys.com/
--
Debian Project (http://www.debian.org/)
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: Debian - apache-ssl - Rivet
Posted by "David N. Welton" <da...@dedasys.com>.
János Holányi wrote:
> Hello,
>
> I'd like to know how I can build an apache-ssl-enabled Debian package of Rivet
> using standard Debian building environment (Sarge) and tools.
>
> Any ideas?
Well, I think the configuration information for Apache SSL should be
captured by the apxs that it ships with. So what you want to do is find
where its apxs script resides, and then, when you configure Rivet, do
something like:
--with-apxs=/usr/bin/apxs-ssl
That line is, for Debian, in debian/rules.
See if that works and let us know, ok?
--
David N. Welton
- http://www.dedasys.com/davidw/
Apache, Linux, Tcl Consulting
- http://www.dedasys.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org