lighttpd modules

[andrew_gatt]

I've downloaded and started to use the OpenWRT binaries and all is
well. However i'm after a few of the modules for lighttpd (namely mod-
status and mod-cgi). They don't seem to be in the tar ball and if i
try to use any other packages (rdc and i386 from the lastest snapshot
downloads of the same version) they complain about differing
architecture - which makes sense.

Does anyone have these packages or an easy way for me to build them?

Thanks for your help.

Andrew

[Jason]

you could try to download Lighty source fom www.lighttpd.org. It
compiles well for the BBoard, well at least on Gentoo.

Note use mod_fastcgi rather than mod_cgi as its faster and uses less
resources - youll need to compile the spawn_fcgi deamon as well.

> Andrewtyuou

[andrew_gatt]

I think i'd need the specific OpenWRT toolchain and build environment
for that to work wouldn't i? Making sure all the right libraries are
built against?

That is another option though, if i could get my hands on the Open WRT
build environment, i could build up the package myself.

I have tired to compile from SVN, but i can't seem to get the kernel
to boot. I'm sure i missing something, but it doesn't find the flash.
I changed the command line to 115200, and i changed the rdc3210.c file
for the code in the patch file (all in the wiki), but it still didn't
work. Hence the use of the binaries - at least i can get the kernel to
boot! The tar ball is exactly what i'm after and has every package,
expect the lighttpd modules.


On Dec 12, 11:09 pm, Jason <g...@solo-c.demon.co.uk> wrote:
> you could try to download  Lighty source fomwww.lighttpd.org.  It

[biff...@yahoo.co.uk]

On Dec 13, 7:50 am, andrew_gatt <a.g...@btinternet.com> wrote:
> I think i'd need the specific OpenWRT toolchain and build environment
> for that to work wouldn't i? Making sure all the right libraries are
> built against?

No, I don't think the libraries have changed much.
Try to build using these instructions:
http://sites.google.com/site/bifferboard/openwrt-svn

Stick with the kernel you've got, select the package you need. I
suspect these instructions result in a damaged opkg setup, however if
you mark the packages you need in the tarball with a star [*] instead
of M [m] then opkg will be run from your host system (not on the
Bifferboard) so it should work.

Biff.

[andrew_gatt]

I may have misunderstood what you meant, but here's what i tried.

I kept the kernel and rootfs from the tar ball (the other option is
that you meant to replace the tar ball rootfs with the just built
rootfs, but wouldn't that mean that i can't use any of the kernel
modules?).

I configured the openwrt svn as per the wiki and compiled everything,
selecting lighttpd as [*] not [m].

I then copied across these packages onto the bifferboard and ran the
install command. Results are as follows.

root@OpenWrt:~# opkg install /home/packages/Built/
lighttpd_1.4.25-1_rdc.ipk
Collected errors:
* Packages were found, but none compatible with the architectures
configured

Should i be replacing the rootfs with the one i just built and use the
kernel modules from the tar ball - to match the kernel on the flash?
Does that work or am i really showing my ignorance!?

On Dec 13, 11:11 am, "biffe...@yahoo.co.uk" <biffe...@yahoo.co.uk>
wrote:

[Andrew Scheller]

> I then copied across these packages onto the bifferboard and ran the
> install command. Results are as follows.
>
> root@OpenWrt:~# opkg install /home/packages/Built/
> lighttpd_1.4.25-1_rdc.ipk
> Collected errors:
>  * Packages were found, but none compatible with the architectures
> configured

I think this error has popped up on the mailing list before - one part
of openwrt is expecting "386" architecture, and another part of
openwrt is expecting "rdc" architecture. I'm afraid I can't remember
what the solution was, but maybe this will help point you in the right
direction?

Lurch

[andrew_gatt]

OK here's what i ended up doing. I extracted the individual packages
i'd built (using openwrt svn and the wiki) and pasted them over the
installed files. Everything seems to be working well and i have cgi
and status mods included.

I extracted the packages with

tar zxOf <package_name>.ipk ./data.tar.gz | tar zxv

then just copied the files over ssh. Seems to be working so far, only
downside is the modules aren't included in the package system of the
bifferboard, but they only install single file modules so its easy
enough to track / clear up.

[biff...@yahoo.co.uk]

On Dec 13, 11:54 am, andrew_gatt <a.g...@btinternet.com> wrote:
> I configured the openwrt svn as per the wiki and compiled everything,
> selecting lighttpd as [*] not [m].

... in which case it should be in the generated tarball, so no need to
copy it anywhere. My idea was that you avoid running opkg on the
Bifferboard, but run it (implicitly) as part of the OpenWrt build,
which as never failed in the past for me. This should happen when you
select target image --> tgz. If that's not working, you could always
post the error messages you get from make V=99.

I'm interested to know why you have to 'install' anything when
selecting something as [*]. It should already be 'installed' into the
tarball, then just extract the tarball onto your USB stick as
documented on the wiki. The package also appears in the packages
directory as well, but you can just ignore it.

Biff.

[andrew_gatt]

Selecting lighttpd as [*] only installs the daemon into the rootfs,
not the modules. These still have to be installed with opkg. I
couldn't find a setting to include them.

Aside from this, i didn't want to use a new rootfs as i had set up and
installed everything else into the rootfs that comes with the open wrt
binary tarball. Extracting and copying over the compiled new lighttpd
binaries has worked in this case.

On Dec 13, 4:09 pm, "biffe...@yahoo.co.uk" <biffe...@yahoo.co.uk>
wrote:

[biff...@yahoo.co.uk]

On Dec 13, 4:27 pm, andrew_gatt <a.g...@btinternet.com> wrote:
> Selecting lighttpd as [*] only installs the daemon into the rootfs,
> not the modules. These still have to be installed with opkg. I
> couldn't find a setting to include them.

Agh sorry- didn't realise this was a kernel-based http server.

> Aside from this, i didn't want to use a new rootfs as i had set up and
> installed everything else into the rootfs that comes with the open wrt
> binary tarball. Extracting and copying over the compiled new lighttpd
> binaries has worked in this case.

Understood,

Biff.