On Thursday 24 July 2003 15:48, Juergen Boemmels wrote: > Daniel Grunblatt <[EMAIL PROTECTED]> writes: > > I have checked in a first attempt to make parrot generate an executable. > > This is very cool. Thanks.
> > > It works fine on x86 - OpenBSD/linux/FreeBSD and should also work on > > NetBSD > > Not at the moment. My Linux-system (an SUSE 7.3 or 8.0) has a > /usr/include/elf.h but it does not define ELFOSABI_LINUX. This file > only contains > #define EI_OSABI 7 /* OS ABI identification */ > #define ELFOSABI_SYSV 0 /* UNIX System V ABI */ > #define ELFOSABI_HPUX 1 /* HP-UX */ > #define ELFOSABI_ARM 97 /* ARM */ > #define ELFOSABI_STANDALONE 255 /* Standalone (embedded) > application */ > > > For PPC (Darwin) it generates code correctly just for programs that use > > *only* fully jitted opcodes. > > > > It should work with or without JIT_CGP. About to solve this. > > Nope > with Configure.pl --cgoto=0 this fails. Attached patch is what I > needed to get it to compile, and make it pass make test. Applied, thanks! > > > After building parrot you should "make exec_start.o" that is used to > > start running the compiled code. > > Then you can use it like this: > > > > # ./test_main -o t.pbc > > > > This will generate exec_output.o (I know that -o must require an argument > > I just don't know which is the correct way to actually make the argument > > "visible" from insede the core, should I just add a pointer in the > > interpreter and a subroutine to embed.c? or what?) > > Put the name of the outputfile in the interpreter structure. > > [...] > > bye > boe Daniel.
