Large files support on FreeBSD

[Russ Allbery]

Julien ÉLIE <julien at trigofacile.com> writes:

> It case it could be of help, the following tests fail *without* large files
> support:
>
> overview/api............MISSED 49-75 (killed by signal 10, core dumped)
> overview/buffindexed....MISSED 1-21 (exit status 1)
> util/inndf..............MISSED 5-6 (exit status 1)
>
> All of them because of an error similar to this one:
>
>    cant create shared memory segment: Function not implemented
>    buffindexed: ovinitdisks: cant create shmem for ov-tmp/buffer len 16384: Function not implemented
>    Opening the overview database failed, cannot continue
>    Bus error: 10 (core dumped)

Shared memory isn't available on that system.  It looks like (from those
tests) that buffindexed requires SysV shared memory to work properly.

> I also see that:
>
> lib/strerror............FAILED 2
>
> -bash-2.05b$ ./strerror.t
> 5
> ok 1
> not ok 2
>  wanted: Unknown error: 0
>    seen: Undefined error: 0
> ok 3
> ok 4
> ok 5
>
> I do not know whether it is important to fix.  (And how?)

It's a silly test; the wording of the reply to strerror(0) is not
standardized.  My fault.

More fundamentally, it's a silly bit of portability these days.  The last
time I saw a system without strerror() was ULTRIX, and I certainly hope no
one is trying to run a modern INN on ULTRIX on a museum piece in their
basement.  (I'm fairly sure that it didn't have mmap anyway.)

The right solution is probably to just delete lib/strerror.c, the Autoconf
probe for strerror, and the corresponding test case.  I don't bother
shipping a replacement for strerror in any of my packages any more.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.