Notices

please test

no SSL:
https://www.dropbox.com/s/jjhvekzmb7...es-n900.tar.gz

with SSL:
https://www.dropbox.com/s/08vzk7hfic...emo5-armel.deb

install:
untar, and install the three deb files inside
dpkg -i apr_1.5.0_maemo5-armel.deb
dpkg -i apr-util_1.5.3_maemo5-armel.deb
dpkg -i apache_2.4.7_maemo5-armel.deb

all files will be installed in /usr/local/....

edit:

# nano /usr/local/apache2/conf/httpd.conf

start:

# /usr/local/apache2/bin/apachectl start

Enjoy!

Does this happen to be built with OpenSSL? If so, I don't need one of my Debian chroots anymore

Cheers,
Justin

no, its not compiled with ssl, sorry
since I did this as a favour. I may do one more

The last time I tried to build Apache with SSL for N900, it was sad times... got crap about 64-bit integers not existing, and the Debian chroot was the easier solution.

You know what though? stunnel will probably work for me with this package. I'll give that a shot -- though if SSL was built with Apache I'd certainly use that instead

Cheers,
Justin

https://www.dropbox.com/s/08vzk7hfic...emo5-armel.deb

Finally got around to trying these packages

This appears to have been built against libssl1.0.0, and none of my thumb/community repos had a good package for this. The waemo/wheezy on maemo package had a GLIBC2.7 symbol issue and didn't work either.

For my webdav server I also need authz_default, mod_dav_lock, and mod_security would be a nice-to-have.

I actually have a scratchbox now to build some of this stuff, but if you have any hints on how you built this software it might help me.

EDIT: Will try your openrepo.net Harmattan packages on Maemo as well and update this thread

Cheers,
Justin

well, download all needed sources.
You will need apr libraries, apr utilities, and, httpd sources.

Surely you might use available apr debs, install those, and just compile httpd sources.

next, start with finding out which modules you want to compile in, and, if its cool to compile those as loadable modules (look at the httpd instructions that already exist at Apache)

Then, run ./configure --help and look at the options you need (example is, you will probably need --with-apr={some path} --with-aprutils={some path} and so on)

Try to find out if you will end up with more dependencies that is needed. Install -devel versions of those (or, maybe needed, complle those)

then do ./configure --prefix=/usr (if thats what you want) --{all options you noted as needed}

You most likely will get configure errors, and you will need to find out what causes those - like additional packages needed for options you want, possibly you need to - again - download sources for those, and all dependencies they need)

Once configure finishes without errors, you need to run make.
Again, you might run into compiling errors. You may even need to make some patching of sources.
Continue to correct/compile (make) until male finsihes.

then as root (fakeroot) run "make install" to install binaries, libraries, modules etc.
Or, run "make install DESTDIR=/some-path

wirh make install DESTDIR=/some-path you can create a deb package with dpkg-deb -b ./some-path some-deb_some-version_armel.deb

to create a deb package, beforehand you will need to create and modify some-path/DEBIAN/control and some-path/DEBIAN/changelog files with appropriate contenr.

Job done, that easy. Compile time is biggest issue ;-)

That doesn't sound too bad actually. The only thing I've tried to build in my scratchbox so far is Pulseaudio and it needed updated autoconf/automake, and it wasn't immediately clear or obvious on how to update those packages within the scratchbox.

Will let you know how things go. Thanks again man!

well, updating those is a bit tricky, not impossible - try googling around for help. They are ARM binaries, but resides in the toolchain and is located outside the scratchbox environment. From inside scratchbox, wrappers are used to reach the actual binaries - cant remember the exact path, but a bit of local searching in the /scratchbox path, outside scratchbox, should easily locate them (find /scratchbox -name autoconf).
You will then need to compile new binaries , and replace the included ones.

Fortunately autotools/automake bastardry was unnecessary for building Apache. Was just a matter of building apr, apr-util, and apache in that order in FREMANTLE_ARMEL scratchbox, putting modules and binaries on the device, and then updating my old 2.2.15 configs (which was the longest, most tedious part).

I'd totally make a .deb but I don't want to have the self-expectation of managing it or determining a canonical configuration structure on-disk for Maemo apache. Plus all the modules would ideally be their own .debs too...

tl:dr; building Apache on scratchbox is way easier than Pulseaudio. And building anything with the FREMANTLE_ARMEL_GCC472 scratchbox profile is a pain in the ***.