From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <140e7ec30802272323n2ddc13bbu59050c05ba390be8@mail.gmail.com>
Date: Thu, 28 Feb 2008 16:23:23 +0900
From: sqweek <sqweek@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] plan9 httpd/pegasus on unix?
In-Reply-To: <20080227155247.GA23909@nibiru.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20080223212240.GB4284@gluon> <47C29FC1.6020202@proweb.co.uk>
	<13426df10802250725w5e777a14n188dadeab28da480@mail.gmail.com>
	<4f34febc0802250826j34a1a5eucce219fe85970dad@mail.gmail.com>
	<20080227155247.GA23909@nibiru.local>
Topicbox-Message-UUID: 66f768da-ead3-11e9-9d60-3106f5b1d025

On Thu, Feb 28, 2008 at 12:52 AM, Enrico Weigelt <weigelt@metux.de> wrote:
> * John Barham <jbarham@gmail.com> wrote:
>
>  > If you just want to serve static content on Unix/FreeBSD, Dan
>  > Bernstein's HTTP server in his publicfile package
>  > (http://cr.yp.to/publicfile.html) is one option.  Considering his
>  > reputation for writing secure software it's probably as good a choice
>  > as any.
>
>  Beware: this reputation is limited to "secure" - installing and
>  maintenance of DJB-packages is really ugly ! (actally, I wouldn't
>  cause this stuff "packages", but collections of code fragments).
>
>  Did you ever try to building qmail ?

 Yes. On linux and netbsd. With and without various patches. Works perfectly.
 The only time in 2 years it has ever required "ugly maintenance" was
no fault of qmail's - about 2 weeks ago my ip-range got blacklisted by
some spam databases for consisting of dynamic ip assignments, so I had
to route outgoing mail through my ISP's mail server.

>  For some customer, I had to get it built in our automated image
>  builder (which does evrything from scratch wit an sysroot'ed
>  cross-toolchain).

$ uname -p
x86_64
$ echo cc -m32 -O2 -include /usr/include/errno.h >conf-cc
$ echo cc -m32 >conf-ld
$ make
...
$ objdump -f auto-gid
auto-gid:     file format elf32-i386
architecture: i386, flags 0x00000112:
...

 Granted, the -include is a bitch and took me awhile to work out. Some
TLS[1] related error which I don't have a good understanding of. Marks
my first qmail build failure - I blame centOS :P
 The sysroot requirement is a little harder to meet, but really just
requires a mount --bind /tmp/sysroot/var/qmail /var/qmail. Or, if
you're running qmail on the host and really can't afford to stop it
for a minute or two, a custom setup rule based on hier.c (or use a
chroot - oh if only lunix had private namespaces...).

[1] /usr/bin/ld: errno: TLS definition in /lib/libc.so.6 section .tbss
mismatches non-TLS reference in substdio.a(substdo.o)

> Required me to completely rewrite all makefiles.

 Just like you had to fork libixp and rewrite all its makefiles?
 Look, if you have a penchant for reimplementing build systems, go for
it. You can rewrite makefiles in every spare second of your time and I
don't care. However, your apparent inability to grasp any build system
not written by yourself is no excuse to spread FUD about other
packages.
-sqweek