+ 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/trn-4.77nb7/work.log + su pbulk -c '"$@"' make /opt/pkg/bin/bmake configure BATCH=1 DEPENDS_TARGET=/nonexistent WRKLOG=/tmp/bulklog/trn-4.77nb7/work.log => Checksum BLAKE2s OK for trn-4.0-test77.tar.gz => Checksum SHA512 OK for trn-4.0-test77.tar.gz ===> Installing dependencies for trn-4.77nb7 ========================================================================== The supported build options for trn are: trn-inn trn-nntpclnt The currently selected options are: trn-nntpclnt You can select which build options to use by setting PKG_DEFAULT_OPTIONS or the following variable. Its current value is shown: PKG_OPTIONS.trn (not defined) ========================================================================== ========================================================================== The following variables will affect the build process of this package, trn-4.77nb7. Their current value is shown below: * CURSES_DEFAULT = ncurses Based on these variables, the following variables have been set: * CURSES_TYPE = ncurses * TERMCAP_TYPE = curses 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 bison>=1.0: found bison-3.8.2nb1 => Tool dependency cwrappers>=20150314: found cwrappers-20220403 => Tool dependency checkperms>=1.1: found checkperms-1.12 => Full dependency nntpclnt>=1.6.1: found nntpclnt-1.6.1nb7 => Full dependency perl>=5.0: found perl-5.42.0 => Full dependency ncurses>=6.5: found ncurses-6.5nb1 ===> Overriding tools for trn-4.77nb7 ===> Extracting for trn-4.77nb7 ===> Patching for trn-4.77nb7 => Applying pkgsrc patches for trn-4.77nb7 => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/news/trn/patches/patch-ac => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/news/trn/patches/patch-ac Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ac,v 1.9 2014/06/29 19:03:30 dholland Exp $ | |- Don't belch on single quotes in uname output. |- Dragonfly support. |- Always use pkgsrc termcap. |- Use assorted pkgsrc tools. |- Don't embed the tools path of sleep into installed scripts. | |--- Configure.orig 2001-02-22 19:17:39.000000000 +0000 |+++ Configure -------------------------- Patching file Configure using Plan A... Hunk #1 succeeded at 1260. Hunk #2 succeeded at 1365. Hunk #3 succeeded at 1507. Hunk #4 succeeded at 2540. Hunk #5 succeeded at 4412. Hunk #6 succeeded at 4858. Hunk #7 succeeded at 4929. Hunk #8 succeeded at 4948. Hunk #9 succeeded at 4975. Hunk #10 succeeded at 5006. Hunk #11 succeeded at 5029. Hunk #12 succeeded at 6253. Hunk #13 succeeded at 6270. Hunk #14 succeeded at 6335. Hunk #15 succeeded at 6406. Hunk #16 succeeded at 6447. Hunk #17 succeeded at 6472. Hunk #18 succeeded at 6480. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/news/trn/patches/patch-ad => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/news/trn/patches/patch-ad Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ad,v 1.2 2013/02/09 18:30:14 christos Exp $ | |--- Pnews.SH.orig 2000-10-31 22:43:16.000000000 +0000 |+++ Pnews.SH -------------------------- Patching file Pnews.SH using Plan A... Hunk #1 succeeded at 911. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/news/trn/patches/patch-ae => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/news/trn/patches/patch-ae Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-ae,v 1.2 2013/02/09 18:30:14 christos Exp $ | |--- hints/darwin.sh.orig 2013-01-23 19:09:43.000000000 +0000 |+++ hints/darwin.sh -------------------------- (Creating file hints/darwin.sh...) Patching file hints/darwin.sh using Plan A... Empty context always matches. Hunk #1 succeeded at 1. done => Verifying /data/jenkins/workspace/pkgsrc-upstream-trunk/news/trn/patches/patch-parsedate.y => Applying pkgsrc patch /data/jenkins/workspace/pkgsrc-upstream-trunk/news/trn/patches/patch-parsedate.y Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |$NetBSD: patch-parsedate.y,v 1.1 2020/07/05 13:35:31 rhialto Exp $ | |Add date grammar rules for old articles from olduse.net. | |--- parsedate.y.orig 2000-05-27 00:31:17.000000000 +0000 |+++ parsedate.y -------------------------- Patching file parsedate.y using Plan A... Hunk #1 succeeded at 134. Hunk #2 succeeded at 263. Hunk #3 succeeded at 305. Hunk #4 succeeded at 729. Hunk #5 succeeded at 743. Hunk #6 succeeded at 756. Hunk #7 succeeded at 848. done ===> Creating toolchain wrappers for trn-4.77nb7 ===> Configuring for trn-4.77nb7 => Substituting "pipe2" in filter.c => Checking for portability problems in extracted files Beginning of configuration questions for trn. Checking echo to see how to suppress newlines... ...using -n. The star should be here-->* First let's make sure your kit is complete. Checking... Looks good... This installation shell script will examine your system and ask you questions to determine how the trn 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] The prompter used in this script allows you to use shell variables and backticks in your answers. You may use $1, $2, etc... to refer to the words in the default answer, as if the default line was a set of arguments given to a script shell. This means you may also use $* to repeat the whole default line, so you do not have to re-type everything to add something to the default. Everytime there is a substitution, you will have to confirm. If there is an error (e.g. an unmatched backtick), the default answer will remain unchanged and you will be prompted again. If you are in a hurry, you may run 'Configure -d'. This will bypass nearly all the questions and use the computed defaults (or the previous answers if there was already a config.sh file). Type 'Configure -h' for a list of options. You may also start interactively and then answer '& -d' at any prompt to turn on the non-interactive behaviour for the remainder of the execution. [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 yours, your best bet is to edit Configure and run it again. If you can't run Configure for some reason, you'll have to generate a config.sh file by hand. Whatever problems you have, let me (trn-workers@lists.sourceforge.net) know how I blew it. 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... awk is in /home/pbulk/build/news/trn/work/.tools/bin/awk. cat is in /home/pbulk/build/news/trn/work/.tools/bin/cat. comm is in /usr/bin/comm. cp is in /home/pbulk/build/news/trn/work/.tools/bin/cp. echo is in /home/pbulk/build/news/trn/work/.tools/bin/echo. expr is in /home/pbulk/build/news/trn/work/.tools/bin/expr. grep is in /home/pbulk/build/news/trn/work/.tools/bin/grep. mkdir is in /home/pbulk/build/news/trn/work/.tools/bin/mkdir. mv is in /home/pbulk/build/news/trn/work/.tools/bin/mv. rm is in /home/pbulk/build/news/trn/work/.tools/bin/rm. sed is in /home/pbulk/build/news/trn/work/.tools/bin/sed. sort is in /home/pbulk/build/news/trn/work/.tools/bin/sort. tail is in /home/pbulk/build/news/trn/work/.tools/bin/tail. touch is in /home/pbulk/build/news/trn/work/.tools/bin/touch. tr is in /home/pbulk/build/news/trn/work/.tools/bin/tr. uniq is in /usr/bin/uniq. Don't worry if any of the following aren't found... I don't see Mcc out there, offhand. ar is in /usr/bin/ar. basename is in /home/pbulk/build/news/trn/work/.tools/bin/basename. bash is in /usr/bin/bash. bison is in /opt/pkg/bin/bison. I don't see byacc out there, either. cpp is in /home/pbulk/build/news/trn/work/.cwrapper/bin/cpp. csh is in /usr/bin/csh. date is in /home/pbulk/build/news/trn/work/.tools/bin/date. diff is in /home/pbulk/build/news/trn/work/.tools/bin/diff. ed is in /usr/bin/ed. egrep is in /home/pbulk/build/news/trn/work/.tools/bin/egrep. inews is in /opt/pkg/bin/inews. I don't see ispell out there, either. ksh is in /usr/bin/ksh. less is in /usr/bin/less. ln is in /home/pbulk/build/news/trn/work/.tools/bin/ln. mail is in /usr/bin/mail. more is in /usr/bin/more. nm is in /usr/bin/nm. nroff is in /usr/bin/nroff. perl is in /opt/pkg/bin/perl. pg is in /usr/bin/pg. I don't see pgp out there, either. rmail is in /usr/bin/rmail. sendmail is in /usr/sbin/sendmail. I don't see smail out there, either. spell is in /usr/bin/spell. test is in /home/pbulk/build/news/trn/work/.tools/bin/test. uname is in /sbin/uname. I don't see uuname out there, either. vi is in /usr/bin/vi. who is in /usr/bin/who. Using the test built into your sh. Checking compatibility between /home/pbulk/build/news/trn/work/.tools/bin/echo and builtin echo (if any)... They are compatible. In fact, they may be identical. Symbolic links are supported. Good, your tr supports [:lower:] and [:upper:] to convert case. Using [:upper:] and [:lower:] to convert case. First time through, eh? I have some defaults handy for some systems that need some extra help getting the Configure answers right: aix_rs domainos irix mips solaris_2 altos486 dynix isc_2_2_1 next sunos convexos freebsd isc_3_2_2 sco_3 svr4 darwin hp9000_800 isc_3_2_3 sco_3_2_4 dec_osf1 hpux linux sco_xenix dgux i386 mc6000 sgi You may give one or more space-separated answers, or "none" if appropriate. A well-behaved OS will have no hints, so answering "none" or just "Policy" is a good thing. DO NOT give a wrong version. Which of these apply, if any? [solaris_2] Configure uses the operating system name and version to set some defaults. The default value is probably right if the name rings a bell. Otherwise, since spelling matters for me, either accept the default or answer "none" to leave it blank. Operating system name? [solaris] Trn is capable of accessing both local and remote news sources at the same time, including multiple servers and private local directories. NOTE: if your system doesn't have a local news spool, choose "nntp" to make the Configuration easier -- it won't affect the access of private local directories. Select the news spool support ("local", "nntp", or "both"): [nntp] Trn supports the new generic user-authentication extension to NNTP that is available in INN 1.5 and NNTP 1.5.12. Do you want to use generic user-authentication? [n] Trn needs a default news source to access when it is started without a custom list. This can either be the name of a server or a filename from which to read the server's name. Enter your news server name or a file name (~name ok): [/etc/opt/pkg/nntp/server] (You'll need to create /etc/opt/pkg/nntp/server before trn will work.) I can set things up so that your shell scripts and binaries are more portable, at what may be a noticable cost in performance. In particular, if you ask to be portable, the following happens: 1) Shell scripts will rely on the PATH variable rather than using the paths derived above. 2) ~username interpretations will be done at run time rather than by Configure. 3) The system name will be determined at run time, if at all possible. Do you expect to run these scripts and binaries on multiple machines? [n] By default, trn will be installed in /opt/pkg/bin, manual pages under /opt/pkg/man, etc..., i.e. with /opt/pkg as prefix for all installation directories. Typically set to /usr/local, but you may choose /usr if you wish to install trn among your system binaries. If you wish to have binaries under /bin but manual pages under /usr/local/man, that's ok: you will be prompted separately for each of the installation directories, the prefix being only used to set the defaults. Installation prefix to use? (~name ok) [/opt/pkg] If the default server doesn't support XGTITLE (to send newsgroup descriptions) you may want to install a copy of the newsgroups file on your local machine and periodically update it (by whatever means you choose). If so, select where you want to put it. If not, enter "none". Where is the newsgroups file? ("none" ok) (~name ok) [none] Trn comes with an inews that can post via the same NNTP connection that the newsreader is using, provided the newsreader (such as trn) supports this. If you don't want to install this inews, enter "none". Pathname where trn's inews will reside? ("none" ok) (~name ok) [none] Which inews should be used for posting articles? (~name ok) [/opt/pkg/bin/inews] If there are any database files (either overview or thread files) available on your local system for accessing the *default* news server (/etc/opt/pkg/nntp/server), enter the appropriate path here for each hierarchy. If you want to use a remote database, enter "remote". If you want to disable a database, enter "none". Enter a local directory for overview files, "remote", or "none": (~name ok) [remote] Enter a local directory for thread files, "remote", or "none": (~name ok) [remote] Trn has two distinct operating modes (selected by the -x option): traditional rn and threaded rn. If you like, trn will check the first letter of the command name and default to threaded mode (-x) if it is a 't', or run as traditional rn (+x) if it isn't (this lets you install as both trn and rn, linked together). Otherwise, you can install trn to default to threaded rn (-x) no matter what its name is. Do you want trn to default to -x, regardless of name? [n] When the -X option is specified, trn will set the default command for starting a newsgroup to be the selector. Should the -X option be on by default for trn (not rn)? [y] Pathname where the public executables will reside? (~name ok) [/opt/pkg/bin] To install the files in this directory, a few strange systems need to use a different directory name to get the files there. What directory name should be used for the install? (~name ok) [/home/pbulk/build/news/trn/work/.destdir/opt/pkg/bin] Directory /home/pbulk/build/news/trn/work/.destdir/opt/pkg/bin doesn't exist. Use that name anyway? [y] Distribution groups are the things you use on the Distribution line to limit where an article will go to. You are likely to be a member of several distribution groups, such as organization, city, state, province, country, continent, etc. For example, Los Angeles has the distribution code "la", New Jersey has the code "nj", and Europe has the code "eunet". The categories you will be asked are: local organization (Could be just one machine or a cluster or an office) organization att, dec, kgb, ... city la, ny, mosc, ... state/province ca, nj, bc, ... multi-state region pnw, ne, ... country usa, can, rok, whatever continent na (North America), asia, etc. Use 'none' for any distributions you don't have. What is the distribution code for your local organization? [none] What is the distribution code for your organization? [none] What is the distribution code for your city? [none] What is the distribution code for your state/province? [none] What is the distribution code for your multi-state region? [none] What is the distribution code for your country? [none] What is the distribution code for your continent? [none] If you have any other distribution groups you will need to edit Pnews to add them. 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... System manual is in /usr/man/man1. Use which C compiler? [cc] Checking for GNU cc in disguise and/or its version number... *** WHOA THERE!!! *** Your C compiler "cc" doesn't seem to be working! You'd better start hunting for one and let me know about it. *** Error code 1 Stop. bmake[1]: stopped making "configure" in /data/jenkins/workspace/pkgsrc-upstream-trunk/news/trn *** Error code 1 Stop. bmake: stopped making "configure" in /data/jenkins/workspace/pkgsrc-upstream-trunk/news/trn