|
#9
February 10th, 2007, 01:43 PM
| ||||
| ||||
| Are you using GD to link against PHP? Or for another project? I've had tests fail when everything else works - its usually because they update the source, change something, but forget to update the test to reflect the new change. Bus error is a Mac error that bugs me a lot. Every other Unix variant I've used puts a more descriptive error... ie: "lp0: printer on fire?"  In any case - you shouldn't have to sudo to get that to work. You are simply compiling a program and linking it against a library. Its possible that the kernel has reserved certain calls for system instead of user - but I doubt it. If its really bugging you, you can recompile the test with the -g flag added to the GCC_FLAGS variable in the Makefile (or whatever its called) .. that'll compile debug symbols into the executable - then you can run the debugger (gdb) to find out what is causing it to crash. See http://www.gnu.org/software/gdb/gdb.html for more info  |
