Re: [AD] Allegro on OpenBSD

[Evert Glebbeek <eglebbk@xxxxxxxxxx>]

> * Everything compiled fine except for src/unix/uossmidi.c. I
> reconfigured with --disable-ossmidi and this compiliation error went
> away.
[...]
> * When linking allegro programs with the default allegro-config I got
> errors about _oss_ioctl not being found. I added -lossaudio to
> allegro-config which fixed this.

I think there were some problems with OSS in Solaris too, but I don't
remember if they were solved? As far as I can remember, it mostly had to do
with the ability to detect the precense of OSS.

> * When starting *any* Allegro program I get the following output from
> ps:
> ~/archives/scratch/c++/star kazzmir $ ./star
> ps: unknown option -- f
> usage: ps [-][aCcehjklmrSTuvwx] [-M core] [-N system] [-O fmt] [-o fmt]
> [-p pid]
>           [-t tty] [-U username] [-W swap]
>        ps [-L]
> ps: unknown option -- f
> usage: ps [-][aCcehjklmrSTuvwx] [-M core] [-N system] [-O fmt] [-o fmt]
> [-p pid]
>           [-t tty] [-U username] [-W swap]
>        ps [-L]
> ps: unknown option -- f
> usage: ps [-][aCcehjklmrSTuvwx] [-M core] [-N system] [-O fmt] [-o fmt]
> [-p pid]
>           [-t tty] [-U username] [-W swap]
>        ps [-L]
> ~/archives/scratch/c++/star kazzmir $

Hmm... this is a problem in get_executable_name (_unix_get_executable_name
in src/unix/). One of the things it tries is using ps to find the name of
the current process - which obviously fails (which, by the way, implies
that get_executable_name() doesn't work). A quick test suggests that the -f
option is not nescessary, so can you try to remove the -f option and
recompile and check if it still works?
Alternatively, do you know a better way to get the name of the executable
under OpenBSD? You may also want to check out current CVS, which has some
fixes for Solaris issues with the same function. I don't think that'll help
on a BSD system, but you never know.
I'm definitely interested in resolving this.

Evert