Bug#544356: neverball: fails to start on kFreeBSD

Jordà Polo jorda at ettin.org
Sat Sep 5 17:26:21 UTC 2009


On Mon, Aug 31, 2009 at 12:23:08AM +0200, Gonéri Le Bouder wrote:
> On Sun, Aug 30, 2009 at 11:39:08PM +0200, Gonéri Le Bouder wrote:
> > The problem is related to libphysfs since it appends in fs_init.
>
> debian:/usr/games$ neverball
> Failure to initialize virtual file system
>  --> Game doesn't start
> debian:/usr/games$ ./neverball
> shm_open() failed: Permission denied
>  --> Game starts ok
> No available audio device
> debian:/usr/games$ /usr/games/neverball
> shm_open() failed: Permission denied
> No available audio device
>  --> Game starts ok

Right, it looks like a libphysfs-related problem, which has just been
added as a dependency for this release.

I can't reproduce the problem (no kFreeBSD box around yet), but it is
failing at PHYSFS_init(), which looking at libphysfs's code, does some
really weird stuff trying to guess the base directory. But other than
that, there is nothing special about that function: it is either called
with argv[0] or NULL as the only parameter. Other libphysfs-based games
such as Warzone2100 call it exactly like Neverball does. Do you have
similar problems with Warzone2100?

A few days ago I committed a patch to the pkg-games SVN repository
(already applied upstream) that might also be helpful to find out where
exactly in the initialization it is failing.

(This seems to be related to #544835, so fixing this bug will probably
help to fix the FTBFS problems, which seem a bit random at the moment.
Neverball 1.5.2 has only been succesfully (auto) built on armel, i386,
ia64, and mips, yet it builds just fine on my amd64 and powerpc
cowbuilders.)





More information about the Pkg-games-devel mailing list