On 12 February 2010 15:01, Roman Neuhauser <[email protected]> wrote: > # [email protected] / 2010-02-10 23:03:26 +0100: >> On 1 February 2010 11:52, Roman Neuhauser <[email protected]> wrote: >> > >> > I'm having trouble with nekoml on FreeBSD 9.0-CURRENT. >> > >> > nekoml runs fine from my usual interactive shell (zsh), but fails >> > with "Uncaught exception - load.c(176): Module not found : ..." when >> > run from /bin/sh. >> >> Hmm, this resembles the unexplained build failures I get on Debian >> GNU/kFreeBSD: > > What shell is the build running under? Does it set $_ to the path of > a program before exec()ing it?
I don't know (it might be dash), but I now use the following patches for kFreeBSD: http://hg.debian.org/hg/collab-maint/neko/file/tip/debian/patches/kfreebsd-compile-fix.diff http://hg.debian.org/hg/collab-maint/neko/file/tip/debian/patches/kfreebsd-executable-path.diff and in addition I have the following in the Makefile: ## Both AMD64 and all kFreeBSDs seem to have problems with the type ## punning used in the Neko source. ifeq (amd64,$(DEB_HOST_ARCH)) cflags += -fno-strict-aliasing endif ifeq (kfreebsd,$(DEB_HOST_ARCH_OS)) cflags += -fno-strict-aliasing endif which seem to fix the problems. Nicolas, here are the GCC warnings which apparently have to be taken seriously: vvm/others.c:465: warning: dereferencing type-punned pointer will break strict-aliasing rules vm/others.c:474: warning: dereferencing type-punned pointer will break strict-aliasing rules m/interp.c:1085: warning: dereferencing type-punned pointer will break strict-aliasing rules libs/std/misc.c:76: warning: dereferencing type-punned pointer will break strict-aliasing rules libs/std/misc.c:96: warning: dereferencing type-punned pointer will break strict-aliasing rules Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- Neko : One VM to run them all (http://nekovm.org)
