Bug 253074 - security/sudo: failed to build 1.9.5p2 on FreeBSD 12.2-RELEASE-p1 amd64
Summary: security/sudo: failed to build 1.9.5p2 on FreeBSD 12.2-RELEASE-p1 amd64
Status: Closed Unable to Reproduce
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Renato Botelho
Depends on:
Reported: 2021-01-29 07:38 UTC by Kirill A Sarksyan
Modified: 2021-06-14 11:30 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (garga)


Note You need to log in before you can comment on or make changes to this bug.
Description Kirill A Sarksyan 2021-01-29 07:38:57 UTC
Hello. Failed to build this port on FreeBSD 12.2-p1.
pkg system does not contain 1.9.5-p2 and port build fails.

[root@xxx /usr/ports/security/sudo]# portupgrade sudo
[Reading data from pkg(8) ... - 484 packages found - done]
--->  Upgrading 'sudo-1.9.5p1' to 'sudo-1.9.5p2' (security/sudo)
--->  Building '/usr/ports/security/sudo'
===>  Cleaning for sudo-1.9.5p2
===>  License sudo accepted by the user
===>   sudo-1.9.5p2 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by sudo-1.9.5p2 for building
===>  Extracting for sudo-1.9.5p2
=> SHA256 Checksum OK for sudo-1.9.5p2.tar.gz.
===>  Patching for sudo-1.9.5p2
===>  Applying FreeBSD patches for sudo-1.9.5p2 from /usr/ports/security/sudo/files
===>   sudo-1.9.5p2 depends on executable: msgfmt - found
===>   sudo-1.9.5p2 depends on shared library: libintl.so - found (/usr/local/lib/libintl.so)
===>  Configuring for sudo-1.9.5p2
configure: loading site script /usr/ports/Templates/config.site
configure: Configuring Sudo version 1.9.5p2
checking for gcc... cc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... unsupported
checking how to run the C preprocessor... cpp
checking for grep that handles long lines and -e... (cached) /usr/bin/grep
checking for egrep... (cached) /usr/bin/egrep
checking for ANSI C header files... (cached) yes
checking for sys/types.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for memory.h... (cached) yes
checking for strings.h... (cached) yes
checking for inttypes.h... (cached) yes
checking for stdint.h... (cached) yes
checking for unistd.h... (cached) yes
checking for minix/config.h... (cached) no
checking whether it is safe to define __EXTENSIONS__... no
checking whether to use a two line prompt for OTP authentication... yes
checking whether to lecture users the first time they run sudo... yes
checking whether sudo should log via syslog or to a file by default... syslog
checking at which syslog priority to log commands... notice
checking at which syslog priority to log failures... alert
checking how long a line in the log file should be... 80
checking whether sudo should ignore '.' or '' in $PATH... yes
checking whether to send mail when a user is not in sudoers... yes
checking whether to send mail when user listed but not for this host... no
checking whether to send mail when a user tries a disallowed command... no
checking who should get the mail that sudo sends... root
checking for bad password prompt... Password: 
checking for bad password message... Sorry, try again.
checking whether to expect fully qualified hosts in sudoers... no
checking for umask programs should be run with... 0022
checking for default user to run commands as... root
checking for editor that visudo should use... vi
checking whether to obey EDITOR and VISUAL environment variables... yes
checking number of tries a user gets to enter their password... 3
checking time in minutes after which sudo will ask for a password again... 5
checking time in minutes after the password prompt will time out... 5
checking whether to include insults... no
checking whether to override the user's path... no
checking whether to get ip addresses from the network interfaces... yes
checking whether to use an askpass helper... no
checking whether to do user authentication by default... yes
checking whether to disable running the mailer as root... no
checking whether to disable shadow password support... no
checking whether root should be allowed to use sudo... yes
checking whether to log the hostname in the log file... no
checking whether to invoke a shell if sudo is given no arguments... no
checking whether to set $HOME to target user in shell mode... no
checking whether to disable 'command not found' messages... no
checking whether to enable environment debugging... no
checking whether to enable environment resetting by default... yes
checking how to run the C preprocessor... cpp
checking for ar... ar
checking for ranlib... ranlib
configure: error: Sudo version 1.9.5p2 requires an ANSI C compiler to build.
===>  Script "configure" failed unexpectedly.
Please report the problem to garga@FreeBSD.org [maintainer] and attach the
"/usr/ports/security/sudo/work/sudo-1.9.5p2/config.log" including the output
of the failure of your make command. Also, it might be a good idea to provide
an overview of all packages installed on your system (e.g. a
/usr/local/sbin/pkg-static info -g -Ea).
*** Error code 1

make[1]: stopped in /usr/ports/security/sudo
*** Error code 1

make: stopped in /usr/ports/security/sudo
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20210129-78151-2pkgoj env UPGRADE_TOOL=portupgrade UPGRADE_PORT=sudo-1.9.5p1 UPGRADE_PORT_VER=1.9.5p1 make
** Fix the problem and try again.
** Listing the failed packages (-:ignored / *:skipped / !:failed)
	! security/sudo (sudo-1.9.5p1)	(configure error)
Comment 1 Renato Botelho freebsd_committer 2021-03-30 12:40:22 UTC
Hello Kirill,

Does this problem persist on current sudo version?  If yes, please attach config.log here so I can take a look.
Comment 2 Renato Botelho freebsd_committer 2021-06-14 11:30:54 UTC
I could not reproduce it and got no answer from submitter confirming it's still broken on current version.  We can re-open it if needed.