+ case "${usergroup_phase}" in
+ local run_cmd
+ run_cmd=run_su
+ shift
+ run_su /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/rayshade-4.0.6nb6/work.log
+ su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/rayshade-4.0.6nb6/work.log
=> Bootstrap dependency digest>=20211023: found digest-20220214
WARNING: [license.mk] Every package should define a LICENSE.
=> Checksum BLAKE2s OK for rayshade.4.0.6.tar.Z
=> Checksum SHA512 OK for rayshade.4.0.6.tar.Z
===> Installing dependencies for rayshade-4.0.6nb6
==========================================================================
The following variables will affect the build process of this package,
rayshade-4.0.6nb6.  Their current value is shown below:

        * JPEG_DEFAULT = jpeg

Based on these variables, the following variables have been set:

        * JPEGBASE (defined, but empty)
        * JPEG_TYPE = jpeg

You may want to abort the process now with CTRL-C and change the value
of variables in the first group before continuing.  Be sure to run
`/opt/pkg/bin/bmake clean' after the changes.
==========================================================================
=> Tool dependency mktools-[0-9]*: found mktools-20220614
=> Tool dependency flex>=2.5.4a: found flex-2.6.4
=> Tool dependency bison>=1.0: found bison-3.8.2nb1
=> Tool dependency cwrappers>=20150314: found cwrappers-20220403
=> Tool dependency checkperms>=1.1: found checkperms-1.12
=> Build dependency flex>=2.5.4a: found flex-2.6.4
=> Full dependency urt>=3.1b1nb18: found urt-3.1b1nb18
===> Overriding tools for rayshade-4.0.6nb6
===> Extracting for rayshade-4.0.6nb6
===> Patching for rayshade-4.0.6nb6
=> Applying pkgsrc patches for rayshade-4.0.6nb6
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-aa
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-aa
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-aa,v 1.4 2016/03/11 08:18:12 tnn Exp $
|
|--- Configure.orig	1992-02-10 03:04:23.000000000 +0000
|+++ Configure
--------------------------
Patching file Configure using Plan A...
Hunk #1 succeeded at 28.
Hunk #2 succeeded at 321.
Hunk #3 succeeded at 366.
Hunk #4 succeeded at 388.
Hunk #5 succeeded at 618.
Hunk #6 succeeded at 723.
Hunk #7 succeeded at 833.
Hunk #8 succeeded at 883.
Hunk #9 succeeded at 1018.
Hunk #10 succeeded at 1159.
Hunk #11 succeeded at 1184.
Hunk #12 succeeded at 1234.
Hunk #13 succeeded at 1273.
Hunk #14 succeeded at 1437.
Hunk #15 succeeded at 1584.
Hunk #16 succeeded at 1609.
Hunk #17 succeeded at 1648.
Hunk #18 succeeded at 1822.
Hunk #19 succeeded at 1845.
Hunk #20 succeeded at 1855.
Hunk #21 succeeded at 1991.
Hunk #22 succeeded at 2012.
Hunk #23 succeeded at 2033.
Hunk #24 succeeded at 2048.
Hunk #25 succeeded at 2178.
Hunk #26 succeeded at 2231.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ab
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ab
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ab,v 1.2 2012/12/25 21:08:40 joerg Exp $
|
|--- etc/rsconvert/lex.l.orig	1992-02-10 03:03:54.000000000 +0000
|+++ etc/rsconvert/lex.l
--------------------------
Patching file etc/rsconvert/lex.l using Plan A...
Hunk #1 succeeded at 21.
Hunk #2 succeeded at 103.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ac
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ac
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ac,v 1.2 2008/09/01 06:57:58 dholland Exp $
|
|This fixes an error that will only occur on machines fast enough to
|compile through two directories in the "libray" directorie in 1 
|second: the upto-date check of libray.a will fail because it was already
|touched in this very second. Slowing things down here will help.
| 
|(I seem to remember some hacking about this before, maybe in make(1),
|but I don't remember, and I won't start hacking make(1) now ;-)
|
|(Note from 2008: still pertinent, because the build misuses ar to add
|objects into the same .a file repeatedly. I could hack it to not do
|that, but for now I'm choosing not to. However, I am fixing the
|makefile to stop on error.)
|
|--- libray/Makefile.orig	1992-02-09 22:03:05.000000000 -0500
|+++ libray/Makefile	2008-09-01 02:06:03.000000000 -0400
--------------------------
Patching file libray/Makefile using Plan A...
Hunk #1 succeeded at 10.
Hunk #2 succeeded at 20.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ad
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ad
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ad,v 1.1 2008/09/01 06:57:58 dholland Exp $
|
|--- Makefile~	1992-02-09 22:03:04.000000000 -0500
|+++ Makefile	2008-09-01 02:03:03.000000000 -0400
--------------------------
Patching file Makefile using Plan A...
Hunk #1 succeeded at 11.
Hunk #2 succeeded at 21.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ae
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ae
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ae,v 1.1 2008/09/01 06:57:58 dholland Exp $
|
|--- libray/libcommon/memory.c~	1992-02-09 22:03:29.000000000 -0500
|+++ libray/libcommon/memory.c	2008-09-01 02:07:19.000000000 -0400
--------------------------
Patching file libray/libcommon/memory.c using Plan A...
Hunk #1 succeeded at 20.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-af
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-af
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-af,v 1.1 2008/09/01 06:57:58 dholland Exp $
|
|--- libray/libobj/hf.c~	1992-02-09 22:04:18.000000000 -0500
|+++ libray/libobj/hf.c	2008-09-01 02:08:11.000000000 -0400
--------------------------
Patching file libray/libobj/hf.c using Plan A...
Hunk #1 succeeded at 42.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ag
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ag
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ag,v 1.1 2008/09/01 06:57:58 dholland Exp $
|
|--- libray/liblight/extended.h~	1992-02-09 22:03:11.000000000 -0500
|+++ libray/liblight/extended.h	2008-09-01 02:09:05.000000000 -0400
--------------------------
Patching file libray/liblight/extended.h using Plan A...
Hunk #1 succeeded at 33.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ah
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ah
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ah,v 1.1 2008/09/01 06:57:58 dholland Exp $
|
|--- libray/libsurf/fog.c~	1992-02-09 22:03:33.000000000 -0500
|+++ libray/libsurf/fog.c	2008-09-01 02:09:44.000000000 -0400
--------------------------
Patching file libray/libsurf/fog.c using Plan A...
Hunk #1 succeeded at 28.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ai
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ai
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ai,v 1.1 2008/09/01 06:57:58 dholland Exp $
|
|--- libray/libtext/texture.h~	1992-02-09 22:03:41.000000000 -0500
|+++ libray/libtext/texture.h	2008-09-01 02:10:15.000000000 -0400
--------------------------
Patching file libray/libtext/texture.h using Plan A...
Hunk #1 succeeded at 76.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-aj
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-aj
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-aj,v 1.1 2008/09/01 06:57:58 dholland Exp $
|
|--- libray/libtext/noise.c~	1992-02-09 22:04:06.000000000 -0500
|+++ libray/libtext/noise.c	2008-09-01 02:11:06.000000000 -0400
--------------------------
Patching file libray/libtext/noise.c using Plan A...
Hunk #1 succeeded at 121.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ak
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ak
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ak,v 1.1 2008/09/01 06:57:58 dholland Exp $
|
|--- libshade/misc.c~	1992-02-09 22:03:59.000000000 -0500
|+++ libshade/misc.c	2008-09-01 02:12:18.000000000 -0400
--------------------------
Patching file libshade/misc.c using Plan A...
Hunk #1 succeeded at 23.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-al
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-al
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-al,v 1.1 2008/09/01 06:57:58 dholland Exp $
|
|--- etc/rsconvert/main.c~	1992-02-09 22:03:28.000000000 -0500
|+++ etc/rsconvert/main.c	2008-09-01 02:15:11.000000000 -0400
--------------------------
Patching file etc/rsconvert/main.c using Plan A...
Hunk #1 succeeded at 24.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-am
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-am
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-am,v 1.2 2015/01/09 14:29:52 joerg Exp $
|
|--- etc/rsconvert/yacc.y~	1992-02-09 22:04:17.000000000 -0500
|+++ etc/rsconvert/yacc.y	2008-09-01 02:15:45.000000000 -0400
--------------------------
Patching file etc/rsconvert/yacc.y using Plan A...
Hunk #1 succeeded at 15.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-an
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-an
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-an,v 1.1 2008/09/01 06:57:58 dholland Exp $
|
|--- libray/liblight/extended.c~	1992-02-09 22:03:43.000000000 -0500
|+++ libray/liblight/extended.c	2008-09-01 02:17:28.000000000 -0400
--------------------------
Patching file libray/liblight/extended.c using Plan A...
Hunk #1 succeeded at 24.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ao
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ao
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ao,v 1.1 2008/09/01 06:57:58 dholland Exp $
|
|--- libray/libsurf/fogdeck.c~	1992-02-09 22:03:45.000000000 -0500
|+++ libray/libsurf/fogdeck.c	2008-09-01 02:18:42.000000000 -0400
--------------------------
Patching file libray/libsurf/fogdeck.c using Plan A...
Hunk #1 succeeded at 31.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ap
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ap
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ap,v 1.1 2008/09/01 06:57:58 dholland Exp $
|
|--- libshade/options.c~	1992-02-09 22:04:09.000000000 -0500
|+++ libshade/options.c	2008-09-01 02:28:43.000000000 -0400
--------------------------
Patching file libshade/options.c using Plan A...
Hunk #1 succeeded at 30.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ba
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-ba
Hmm...  Looks like a new-style context diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-ba,v 1.1 1998/08/24 18:11:44 agc Exp $
|
|*** raypaint/Makefile.SH.orig	Sat Mar 28 20:31:28 1998
|--- raypaint/Makefile.SH	Sat Mar 28 20:31:55 1998
--------------------------
Patching file raypaint/Makefile.SH using Plan A...
Hunk #1 succeeded at 55.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-libray_libtext_mapping.h
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-libray_libtext_mapping.h
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-libray_libtext_mapping.h,v 1.1 2012/12/25 21:08:40 joerg Exp $
|
|--- libray/libtext/mapping.h.orig	2012-12-25 18:59:13.000000000 +0000
|+++ libray/libtext/mapping.h
--------------------------
Patching file libray/libtext/mapping.h using Plan A...
Hunk #1 succeeded at 36.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-libray_libtext_texture.c
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-libray_libtext_texture.c
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-libray_libtext_texture.c,v 1.1 2012/12/25 21:08:40 joerg Exp $
|
|--- libray/libtext/texture.c.orig	2012-12-25 18:58:09.000000000 +0000
|+++ libray/libtext/texture.c
--------------------------
Patching file libray/libtext/texture.c using Plan A...
Hunk #1 succeeded at 121.
done
=> Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-libshade_lex.l
=> Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade/patches/patch-libshade_lex.l
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|$NetBSD: patch-libshade_lex.l,v 1.1 2012/12/25 21:08:40 joerg Exp $
|
|--- libshade/lex.l.orig	1992-02-10 03:04:02.000000000 +0000
|+++ libshade/lex.l
--------------------------
Patching file libshade/lex.l using Plan A...
Hunk #1 succeeded at 28.
Hunk #2 succeeded at 166.
done
===> Creating toolchain wrappers for rayshade-4.0.6nb6
===> Configuring for rayshade-4.0.6nb6
=> Checking for portability problems in extracted files
(I see you are using the Korn shell.  Some ksh's blow up on Configure,
especially on exotic machines.  If yours does, try the Bourne shell instead.)
 
Beginning of configuration questions for rayshade kit.
 
First let's make sure your kit is complete.  Checking...
Looks good...
 
Checking your sh to see if it knows about # comments...
Your sh handles # comments correctly.
 
Okay, let's see if #! works on this system...
It does.
 
Checking out how to guarantee sh startup...
Let's see if '#!/bin/sh' works...
Yup, it does.
 
Checking echo to see how to suppress newlines...
...using -n.
The star should be here-->*
 
This installation shell script will examine your system and ask you questions
to determine how the rayshade package should be installed.  If you get stuck
on a question, you may use a ! shell escape to start a subshell or execute
a command.  Many of the questions will have default answers in square
brackets--typing carriage return will give you the default.

On some of the questions which ask for file or directory names you are
allowed to use the ~name construct to specify the login directory belonging
to "name", even if you don't have a shell which knows about that.  Questions
where this is allowed will be marked "(~name ok)".

[Type carriage return to continue] 
Much effort has been expended to ensure that this shell script will run on
any Unix system. If despite that it blows up on you, your best bet is to edit
Configure and run it again. Also, let me (rayshade-request@cs.princeton.edu)
know how I blew it. If you can't run Configure for some reason, you'll have
to generate a config.sh file by hand.

This installation script affects things in two ways:
1) it may do direct variable substitutions on some of the files included
   in this kit.
2) it builds a config.h file for inclusion in C programs.  You may edit
   any of these files as the need arises after running this script.

If you make a mistake on a question, there is no easy way to back up to it
currently.  The easiest thing to do is to edit config.sh and rerun all the
SH files.  Configure will offer to let you do this before it runs the SH files.

[Type carriage return to continue]  
Locating common programs...
cat is in /bin/cat.
echo is in /bin/echo.
expr is in /bin/expr.
grep is in /bin/grep.
rm is in /bin/rm.
sed is in /bin/sed.
sort is in /bin/sort.
uniq is in /bin/uniq.
 
Don't worry if any of the following aren't found...
bison is in /opt/pkg/bin/bison.
cpp is in /usr/lib/cpp.
test is in /bin/test.
Using the test built into your sh.
 
Checking compatibility between /bin/echo and builtin echo (if any)...
They are not compatible!  You are probably running ksh on a non-USG system.
I'll have to use /bin/echo instead of the builtin, since Bourne shell doesn't
have echo built in and we may have to run some Bourne shell scripts.  That
means I'll have to use \c to suppress newlines now.  Life is ridiculous.

The star should be here-->*
 
Checking for optional libraries...
No -lm.
No -lmalloc.
No -lc_s.
 
Some versions of Unix support shared libraries, which make
executables smaller but make load time slightly longer.

On some systems, mostly newer Unix System V's, the shared library
is included by putting the option "-lc_s" as the last thing on the
cc command line when linking.  Other systems use shared libraries
by default.  There may be other libraries needed to compile rayshade
on your machine as well.  If your system needs the "-lc_s" option,
include it here.  Include any other special libraries here as well.
Say "none" for none.
 
Any additional libraries? [none]  
Your shared C library is in /usr/lib/libc.so.
 
Extracting names from /usr/lib/libc.so for later perusal...done
 
<sys/types.h> found.
 
times() found.
 
What type is returned by times() on this sytem? [clock_t]  
System manual is in /usr/man/man1.
 
Hmm...  Looks kind of like a Version 7 system, but we'll see...
 
Congratulations.  You aren't running Eunice.
 
It's not Xenix...
 
Nor is it Venix...
 
Some systems have different model sizes.  On most systems they are called
small, medium, large, and huge.  On the PDP11 they are called unsplit and
split.  If your system doesn't support different memory models, say "none".
If you wish to force everything to one memory model, say "none" here and
put the appropriate flags later when it asks you for other cc and ld flags.
Venix systems may wish to put "none" and let the compiler figure things out.
(In the following question multiple model names should be space separated.)

Which models are supported? [none] Unrecognized memory models--you may have to edit Makefile.SH
 
Use which C compiler? [cc] 
Some C compilers have problems with their optimizers, by default, rayshade
compiles with the -O flag to use the optimizer.  Alternately, you might
want to use the symbolic debugger, which uses the -g flag (on traditional
Unix systems).  Either flag can be specified here.  To use neither flag,
specify the word "none".
  
What optimizer/debugger flag should be used? [-O] 
Your C compiler may want other flags.  For this question you should
include -I/whatever and -DWHATEVER flags and any other flags used by
the C compiler, but you should NOT include libraries or ld flags like
-lwhatever.  To use no flags, specify the word "none".
  
Any additional cc flags? [none] (C preprocessor flags:  -I/opt/pkg/include)
 
Any additional ld flags (NOT including libraries)? [none]  
Now, how can we feed standard input to your C preprocessor...
Maybe "cc -E" will work...
Nope, maybe "/usr/lib/cpp" will work...
Yup, it does.
 
memset() found.
 
bzero() found.
 
cbrt() not found.
 
Using <string.h> instead of <strings.h>.
 
strchr() found.
 
popen() found.
 
<sys/resource.h> found.
  
Testing to see if we should include <time.h>, <sys/time.h> or both.
I'm now running the test program...
Trying -DI_SYSTIME -DS_TIMEVAL
Trying -DS_TIMEVAL
Trying -DI_TIME -DI_SYSTIME -DS_TIMEVAL
Trying -DI_TIME -DS_TIMEVAL
Trying -DI_SYSTIME -DSYSTIMEKERNEL -DS_TIMEVAL
Trying -DSYSTIMEKERNEL -DS_TIMEVAL
Trying -DI_TIME -DI_SYSTIME -DSYSTIMEKERNEL -DS_TIMEVAL
Trying -DI_TIME -DSYSTIMEKERNEL -DS_TIMEVAL
Trying -DI_SYSTIME
Trying
Trying -DI_TIME -DI_SYSTIME
Trying -DI_TIME
Trying -DI_SYSTIME -DSYSTIMEKERNEL
Trying -DSYSTIMEKERNEL
Trying -DI_TIME -DI_SYSTIME -DSYSTIMEKERNEL
Trying -DI_TIME -DSYSTIMEKERNEL
 
getrusage() found.
 
rayshade works best when linked with the Utah Raster Toolkit.
If you don't have the URT, rayshade will compile, but with many
useful features disabled.

In addition to providing a library for reading and writing compact
image files, the URT offers a host of useful image-maniuplation tools.
You are strongly encouraged to get a copy.

If you do not have a copy of the URT, answer 'none' below.

What directory holds the Utah Raster Toolkit include files? [none]  
Where is the Utah Raster Toolkit library? [/opt/pkg/lib/librle.a]  
<stdlib.h> found.
 
Good, found drand48().
 
Use which function to generate random numbers? [drand48]  
Checking to see how well your C compiler groks the void type...

  Support flag bits are:
    1: basic void declarations.
    2: arrays of pointers to functions returning void.
    4: operations between pointers to and addresses of void functions.
    8: generic void pointers.

Hmm, your compiler has some difficulty with void.  Checking further...
There is no support at all for void.
Your void support flags add up to what? [0]  
Where do you want to put the public executables? (~name ok) [/usr/local/bin]  
Checking how to generate makefile dependencies on your machine...
A shell script using /usr/lib/cpp does the trick.
 
Name of program to make makefile dependencies? [/home/pbulk/build/graphics/rayshade/work/rayshade.4.0/mkdep] /usr/bin/mkdep doesn't exist.  Use that name anyway? [n] ERROR: Configure script tried to use interactive prompt
*** Error code 1

Stop.
bmake[1]: stopped in /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade
*** Error code 1

Stop.
bmake: stopped in /data/jenkins/workspace/pkgsrc-upstream-trunk/graphics/rayshade