=> Bootstrap dependency digest>=20010302: found digest-20190127 WARNING: [license.mk] Every package should define a LICENSE. => Checksum SHA1 OK for elm2.5.8.tar.gz => Checksum RMD160 OK for elm2.5.8.tar.gz => Checksum SHA512 OK for elm2.5.8.tar.gz ===> Installing dependencies for elm-2.5.8nb5 => Tool dependency nbpatch-[0-9]*: found nbpatch-20151107 => Tool dependency checkperms>=1.1: found checkperms-1.12 => Build dependency cwrappers>=20150314: found cwrappers-20180325 => Full dependency metamail>=2.7: found metamail-2.7nb12 => Full dependency gettext-lib>=0.18: found gettext-lib-0.21 ===> Skipping vulnerability checks. WARNING: No /opt/pkg/pkgdb/pkg-vulnerabilities file found. WARNING: To fix run: `/opt/pkg/sbin/pkg_admin -K /opt/pkg/pkgdb fetch-pkg-vulnerabilities'. ===> Overriding tools for elm-2.5.8nb5 ===> Extracting for elm-2.5.8nb5 ===> Patching for elm-2.5.8nb5 => Applying pkgsrc patches for elm-2.5.8nb5 => Verifying /opt/pkgsrc/mail/elm/patches/patch-aa => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-aa Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-aa,v 1.5 2006/06/20 15:39:06 joerg Exp $ | |--- Configure.orig 2005-08-18 12:49:24.000000000 +0000 |+++ Configure -------------------------- Patching file Configure using Plan A... Hunk #1 succeeded at 18. Hunk #2 succeeded at 485. Hunk #3 succeeded at 1992. Hunk #4 succeeded at 5496. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-ab => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-ab Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ab,v 1.5 2001/07/18 20:04:13 martin Exp $ |--- nls/LANGS.orig Thu Apr 20 05:38:33 1995 |+++ nls/LANGS Wed Jul 18 06:58:32 2001 -------------------------- Patching file nls/LANGS using Plan A... Hunk #1 succeeded at 1. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-ac => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-ac Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ac,v 1.6 2010/04/15 06:50:46 dholland Exp $ | |--- nls/Makefile.orig 2005-08-18 12:49:24.000000000 +0000 |+++ nls/Makefile -------------------------- Patching file nls/Makefile using Plan A... Hunk #1 succeeded at 1. Hunk #2 succeeded at 35. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-ad => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-ad Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ad,v 1.7 2010/04/15 06:50:46 dholland Exp $ | |destdir support. | |--- Make.defs.SH.orig 2005-08-18 12:49:24.000000000 +0000 |+++ Make.defs.SH -------------------------- Patching file Make.defs.SH using Plan A... Hunk #1 succeeded at 113. Hunk #2 succeeded at 144. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-ae => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-ae Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ae,v 1.4 2003/04/23 14:36:37 jschauma Exp $ | |--- doc/Makefile.SH.orig Wed Mar 24 09:13:56 1999 |+++ doc/Makefile.SH -------------------------- Patching file doc/Makefile.SH using Plan A... Hunk #1 succeeded at 101. Hunk #2 succeeded at 119. Hunk #3 succeeded at 133. Hunk #4 succeeded at 147. Hunk #5 succeeded at 162. Hunk #6 succeeded at 274. Hunk #7 succeeded at 288. Hunk #8 succeeded at 322. Hunk #9 succeeded at 365. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-af => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-af Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-af,v 1.1 2001/07/18 20:04:14 martin Exp $ |--- Makefile.SH.orig Fri Mar 15 02:27:09 1996 |+++ Makefile.SH Mon Jul 16 02:25:23 2001 -------------------------- Patching file Makefile.SH using Plan A... Hunk #1 succeeded at 87. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-ag => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-ag Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ag,v 1.1 2003/04/23 14:36:37 jschauma Exp $ | |--- utils/Makefile.SH.orig Fri Apr 4 14:20:02 2003 |+++ utils/Makefile.SH -------------------------- Patching file utils/Makefile.SH using Plan A... Hunk #1 succeeded at 86. Hunk #2 succeeded at 119. Hunk #3 succeeded at 128. Hunk #4 succeeded at 151. Hunk #5 succeeded at 171. Hunk #6 succeeded at 206. Hunk #7 succeeded at 231. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-ah => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-ah Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ah,v 1.1 2006/01/24 22:47:13 joerg Exp $ | |--- hdrs/elm_defs.h.orig 2006-01-24 19:52:27.000000000 +0000 |+++ hdrs/elm_defs.h -------------------------- Patching file hdrs/elm_defs.h using Plan A... Hunk #1 succeeded at 103. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-ai => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-ai Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ai,v 1.1 2006/01/24 22:47:13 joerg Exp $ | |--- hdrs/elm_lib.h.orig 2006-01-24 19:53:20.000000000 +0000 |+++ hdrs/elm_lib.h -------------------------- Patching file hdrs/elm_lib.h using Plan A... Hunk #1 succeeded at 67. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-aj => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-aj Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-aj,v 1.1 2006/01/24 22:47:13 joerg Exp $ | |--- config.h.SH.orig 2005-08-18 12:49:24.000000000 +0000 |+++ config.h.SH -------------------------- Patching file config.h.SH using Plan A... Hunk #1 succeeded at 40. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-ak => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-ak Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ak,v 1.2 2006/07/17 17:41:00 wiz Exp $ | |--- hdrs/mcprtlib.h.orig 2005-08-18 12:49:24.000000000 +0000 |+++ hdrs/mcprtlib.h -------------------------- Patching file hdrs/mcprtlib.h using Plan A... Hunk #1 succeeded at 46. Hunk #2 succeeded at 137. Hunk #3 succeeded at 151. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-al => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-al Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-al,v 1.1 2006/01/24 22:47:13 joerg Exp $ | |--- utils/newmail.c.orig 2006-01-24 22:37:59.000000000 +0000 |+++ utils/newmail.c -------------------------- Patching file utils/newmail.c using Plan A... Hunk #1 succeeded at 88. Hunk #2 succeeded at 161. Hunk #3 succeeded at 699. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-am => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-am Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-am,v 1.1 2006/07/17 17:41:00 wiz Exp $ | |--- src/curses.c.orig 2005-08-18 13:20:14.000000000 +0000 |+++ src/curses.c -------------------------- Patching file src/curses.c using Plan A... Hunk #1 succeeded at 47. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-an => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-an Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-an,v 1.2 2010/04/15 06:50:46 dholland Exp $ | |Add necessary includes; fix POSIX getline lossage. | |--- nls/gencat/genlib.c.orig 2005-08-18 12:49:24.000000000 +0000 |+++ nls/gencat/genlib.c -------------------------- Patching file nls/gencat/genlib.c using Plan A... Hunk #1 succeeded at 42. Hunk #2 succeeded at 88. Hunk #3 succeeded at 203. Hunk #4 succeeded at 335. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-ao => Applying pkgsrc patch /opt/pkgsrc/mail/elm/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/07/21 05:35:37 dholland Exp $ | |--- lib/msgcat.c.orig 2005-08-18 08:49:24.000000000 -0400 |+++ lib/msgcat.c 2008-07-21 01:22:41.000000000 -0400 -------------------------- Patching file lib/msgcat.c using Plan A... Hunk #1 succeeded at 60. Hunk #2 succeeded at 88. Hunk #3 succeeded at 283. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-ap => Applying pkgsrc patch /opt/pkgsrc/mail/elm/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/07/21 05:35:37 dholland Exp $ | |--- src/savecopy.c~ 2005-08-18 08:49:24.000000000 -0400 |+++ src/savecopy.c 2008-07-21 01:27:53.000000000 -0400 -------------------------- Patching file src/savecopy.c using Plan A... Hunk #1 succeeded at 51. Hunk #2 succeeded at 82. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-aq => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-aq Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-aq,v 1.1 2010/04/15 06:50:46 dholland Exp $ | |destdir support. | |--- nls/Install~ 2005-08-18 12:49:24.000000000 +0000 |+++ nls/Install -------------------------- Patching file nls/Install using Plan A... Hunk #1 succeeded at 40. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-src_a__sort.c => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-src_a__sort.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-src_a__sort.c,v 1.1 2013/02/26 11:08:17 joerg Exp $ | |--- src/a_sort.c.orig 2013-02-25 16:39:10.000000000 +0000 |+++ src/a_sort.c -------------------------- Patching file src/a_sort.c using Plan A... Hunk #1 succeeded at 34. Hunk #2 succeeded at 181. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-src_alias.c => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-src_alias.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-src_alias.c,v 1.1 2013/02/26 11:08:17 joerg Exp $ | |--- src/alias.c.orig 2013-02-25 16:38:02.000000000 +0000 |+++ src/alias.c -------------------------- Patching file src/alias.c using Plan A... Hunk #1 succeeded at 705. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-src_calendar.c => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-src_calendar.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-src_calendar.c,v 1.1 2013/02/26 11:08:17 joerg Exp $ | |--- src/calendar.c.orig 2013-02-25 16:39:42.000000000 +0000 |+++ src/calendar.c -------------------------- Patching file src/calendar.c using Plan A... Hunk #1 succeeded at 45. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-src_elm.c => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-src_elm.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-src_elm.c,v 1.1 2013/02/26 11:08:17 joerg Exp $ | |--- src/elm.c.orig 2013-02-25 16:40:15.000000000 +0000 |+++ src/elm.c -------------------------- Patching file src/elm.c using Plan A... Hunk #1 succeeded at 63. Hunk #2 succeeded at 596. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-src_fileio.c => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-src_fileio.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-src_fileio.c,v 1.1 2013/02/26 11:08:17 joerg Exp $ | |--- src/fileio.c.orig 2013-02-25 16:40:58.000000000 +0000 |+++ src/fileio.c -------------------------- Patching file src/fileio.c using Plan A... Hunk #1 succeeded at 66. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-src_read__rc.c => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-src_read__rc.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-src_read__rc.c,v 1.1 2013/02/26 11:08:17 joerg Exp $ | |--- src/read_rc.c.orig 2013-02-25 16:41:35.000000000 +0000 |+++ src/read_rc.c -------------------------- Patching file src/read_rc.c using Plan A... Hunk #1 succeeded at 82. Hunk #2 succeeded at 324. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-src_screen.c => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-src_screen.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-src_screen.c,v 1.1 2013/02/26 11:08:17 joerg Exp $ | |--- src/screen.c.orig 2013-02-25 16:42:10.000000000 +0000 |+++ src/screen.c -------------------------- Patching file src/screen.c using Plan A... Hunk #1 succeeded at 252. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-src_strings.c => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-src_strings.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-src_strings.c,v 1.1 2013/02/26 11:08:17 joerg Exp $ | |--- src/strings.c.orig 2013-02-25 16:42:37.000000000 +0000 |+++ src/strings.c -------------------------- Patching file src/strings.c using Plan A... Hunk #1 succeeded at 165. done => Verifying /opt/pkgsrc/mail/elm/patches/patch-utils_answer.c => Applying pkgsrc patch /opt/pkgsrc/mail/elm/patches/patch-utils_answer.c Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-utils_answer.c,v 1.1 2013/02/26 11:08:17 joerg Exp $ | |--- utils/answer.c.orig 2013-02-25 16:43:08.000000000 +0000 |+++ utils/answer.c -------------------------- Patching file utils/answer.c using Plan A... Hunk #1 succeeded at 53. Hunk #2 succeeded at 273. done ===> Creating toolchain wrappers for elm-2.5.8nb5 ===> Configuring for elm-2.5.8nb5 /opt/pkg/bin/nbsed -e 's:@PREFIX@:/opt/pkg:g' -e 's:@DESTDIR@:/opt/work/mail/elm/work/.destdir:g' -e 's:@LOCALBASE@:/opt/pkg:g' -e 's:@PKGMANDIR@:man:g' -e 's:@LIBC@:/usr/lib/libSystem.dylib:g' /opt/pkgsrc/mail/elm/files/config.sh > /opt/work/mail/elm/work/elm2.5.8/config.sh /bin/mv /opt/work/mail/elm/work/elm2.5.8/nls/LANGS /opt/work/mail/elm/work/elm2.5.8/nls/LANGS.tmpl /opt/pkg/bin/nbsed -e 's:__PREFIX:'/opt/pkg':g' < /opt/work/mail/elm/work/elm2.5.8/nls/LANGS.tmpl > /opt/work/mail/elm/work/elm2.5.8/nls/LANGS => 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 elm2.5 kit. First let's make sure your kit is complete. Checking... Looks good... Making bin directory 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 \c This installation shell script will examine your system and ask you questions to determine how the elm2.5 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 the Elm Development Group (elm@dsi.com) know how they 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, and 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] I see a config.sh file. Did Configure make it on THIS system? [y] Fetching default answers from your old config.sh file... Locating common programs... cat is in /bin/cat. chgrp is in /usr/bin/chgrp. chmod is in /bin/chmod. cp is in /bin/cp. echo is in /bin/echo. expr is in /bin/expr. grep is in /usr/bin/grep. ln is in /bin/ln. ls is in /bin/ls. mv is in /bin/mv. rm is in /bin/rm. sed is in /usr/bin/sed. sleep is in /bin/sleep. touch is in /usr/bin/touch. tr is in /usr/bin/tr. Don't worry if any of the following aren't found... I don't see Mcc out there, offhand. compress is in /usr/bin/compress. cpp is in /usr/bin/cpp. date is in /bin/date. I don't see emacs out there, either. I don't see execmail out there, either. I don't see ispell out there, either. I don't see line out there, either. I don't see lint out there, either. lp is in /usr/bin/lp. lpr is in /usr/bin/lpr. I don't see mips out there, either. more is in /usr/bin/more. nroff is in /usr/bin/nroff. I don't see pack out there, either. I don't see pg out there, either. pr is in /usr/bin/pr. I don't see rmail out there, either. sendmail is in /usr/sbin/sendmail. shar is in /usr/bin/shar. I don't see smail out there, either. I don't see submit out there, either. tar is in /usr/bin/tar. tbl is in /usr/bin/tbl. test is in /bin/test. troff is in /usr/bin/troff. uname is in /usr/bin/uname. uuname is in /usr/bin/uuname. vi is in /usr/bin/vi. Using the test built into your sh. Checking compatibility between /bin/echo and builtin echo (if any)... They are compatible. In fact, they may be identical. There is a neat feature that enables scanning of the message body for entries to add to the users ".calendar" (or whatever) file. These entries are then processed by the system program calendar. To use this feature it needs to be enabled. The name of the per user calendar file used by your system's calendar program is also required. Enable calendar feature [y] Default calendar file: [calendar] Not all environments are restricted to the ASCII 7-bit character set. For example, the ISO 8859/1 (Latin alphabet no. 1) character set, consisting of 8 bits and 191 printable characters, is becoming more and more common, especially in non-English speaking countries. Unfortunately, not all isprint() functions or macros, which ELM uses to determine whether a character is printable or not, will handle non-ASCII (8-bit) characters properly. It is suggested that you start with this value configured to handle 8-bit characters correctly and if there are problems with Elm aborting while displaying messages that use extended character sets to reconfigure Elm to only display 7-bit characters. Should Elm assume that isprint() won't break on non-ASCII characters? [y] Hmm... ./Configure[880]: cat: /usr/include/signal.h: No such file or directory ./Configure[880]: cat: /usr/include/sys/signal.h: No such file or directory 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... Does your /etc/passwd file keep full names in Berkeley/V7 format (name first thing after ':' in GCOS field)? [y] The Elm documentation (Reference Guide, Configuration Guide, etc.) is set up for troff. If you only have nroff, it can be used, but the documentation will not be as readable. If you use an alternate processor for troff/nroff documents it can be specified here. Elm expects the text processor to write to standard out. You will be given a chance to provide command line options to this command in the next question. Give the name of the program used to format the Elm documentation on your system: [/usr/bin/troff] If this text processor requires any options for proper formatting, specify them here. To specify no options, enter the word "none". Some versions of troff require the -t option to write to standard out. This is the proper place to specify that option. What options should Elm use with /usr/bin/troff: [] elm2.5 has manual pages that can be installed in unformatted or formatted form. Either or both (or neither) of these may be installed. Please give the location in which to store each type of man page. To specify that a particular type is not to be installed, answer "none" to the question. Where do the unformatted manual pages go? [/opt/work/mail/elm/work/.destdir/opt/pkg/man/man1] Directory /opt/work/mail/elm/work/.destdir/opt/pkg/man/man1 doesn't exist. Use that name anyway? [y] The installed unformatted manual pages can have various extensions to suit the conventions of the host operating system, for example "page.1". Note that the period '.' must be included as part of the extension. To specify no extension, enter the word "none". What extension should be used on installed unformatted man pages: [.1] Where do the formatted manual pages go? [none] 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. Xenix and 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] Use which C compiler? [cc -MD] Some C compilers have problems with their optimizers, by default, elm2.5 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? [-O2] 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. If you want elm to honor its debug flag, add -DDEBUG. To use no flags, specify the word "none". Any additional cc flags? [-I/opt/pkg/include] (C preprocessor flags: -I/opt/pkg/include) Your linker/loader may want other flags. For example, you might want to enable support for the symbolic debugger (-g on traditional UNIX systems). For this question you should specify those flags. Do NOT specify libraries (-lwhatever) here. Most systems will not need any special flags, in which case specify "none". Any additional ld flags (NOT including libraries)? [-Wl,-R/opt/pkg/lib -L/opt/pkg/lib] Checking for optional libraries... No -lintl. No -lnls. 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 elm2.5 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? [-lintl] I can't seem to find your C library. I've looked in the following places: /usr/lib /usr/ccs/lib /usr/local/lib /usr/lib/large /lib /usr/lib/386 /lib/386 /lib /lib/large /usr/lib/small /lib/small None of these seems to contain your C library. What is the full name of your C library? Extracting names from None for later perusal... nm didn't seem to work right. Trying ar instead... ar: None: No such file or directory ar didn't seem to work right. Maybe this is a Cray...trying bld instead... ./Configure[2174]: t: inaccessible or not found bld didn't seem to work right either. Desperation time. We'll use strings and hope this returns something useful. error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/strings: can't open file: None (No such file or directory) That didn't work either. Giving up. *** Error code 1 Stop. bmake[1]: stopped in /opt/pkgsrc/mail/elm *** Error code 1 Stop. bmake: stopped in /opt/pkgsrc/mail/elm