[Bf-committers] RenderD Info

Stefan Gartner bf-committers@blender.org
Fri, 11 Apr 2003 22:47:04 +0200


On Friday 11 April 2003 17:11, Douglas Bischoff wrote:
> Hello:
>
> I have successfully compiled RenderD on OS X. I don't have (nor do I
> particularly want for fear of making a mess *grin*) commit rights, but
> I think this might be useful to someone more knowledgable.
>
> Here is my edit to the Makefile in renderd:
> In "platform dependent parts:
> ----
> ifeq ($(OS),darwin)
>      NAN_DEPEND = true
>      # Static libraries:
>      LIBS = $(NSPR)/lib/libplc4.a $(NSPR)/lib/libnspr4.a
>      # If you used PTH instead of EMU NSPR you also need:
>      LIBS += -lpthread
> endif
> ----
> Mind you, I had to use a bash script to define $OS because the existing
> one was mis-identifying my system.

if you replace renderd's config.guess with the one from 
/usr/share/autoconf-1.6, it should get recognized correctly

>
> Everything runs fine... but when I fire up renderd in the same
> directory as the blender executable, I get:
> ----
> Exception:  EXC_BAD_ACCESS (0x0001)
> Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
>
> Thread 0:
>   #0   0x900257ac in select
>   #1   0x0001d8cc in poll (unix.c:3667)
>   #2   0x000085f4 in pt_poll_now (ptio.c:592)
>   #3   0x00008b1c in pt_Continue (ptio.c:716)
>   #4   0x0000acac in pt_Accept (ptio.c:1665)
>   #5   0x0000499c in PR_Accept (priometh.c:194)
>   #6   0x00001fa8 in main (renderd.c:108)
>   #7   0x00001a10 in _start (crt.c:267)
>   #8   0x00001890 in start
>
> Thread 1 Crashed:
>   #0   0x00019db0 in PR_EnumerateHostEnt (prnetdb.c:1236)
>   #1   0x00003ac4 in renderd_scan_thread (scan.c:34)
>   #2   0x00005a30 in _pt_root (ptthread.c:217)
>   #3   0x90020d48 in _pthread_body
> ----
> My only thought here is that launching ./blender from the command line
> generates a window that takes no input whatsoever. This window never
> appears when running ./renderd, so I have to assume that blender never
> fires up properly. My thought is that without a flag to tell it to run
> in the background, blender fails to startup like this.
>
> If this sounds reasonable, can someone add a flag to blender that will
> tell it not to create the GUI? To essentially do the same thing as the
> "-b" option except don't expect a file right away.

make sure renderd runs the binary inside the application bundle (eg. set the 
BLENDER environment variable to /path/to/blender.app/Contents/MacOS/blender

>
> Thanks,
>
> -Doug

sgefant