Re: Unable to 'make config' ports under FreeBSD current

On 2016-07-01 10:56, Larry Baird wrote:
> I recently installed FreebSD current using a snapshot ISO. I then used svnlite
> to bring FreeBSD source up to date. I then used portsnap fetch extract to
> bring my ports tree up todate. I was surprised I got errors doing 'make config'
> for a port. I assumed it was a transitory problem. I have brought my system
> and ports up to date several times over the last few weeks, but the issue
> remains. The fix to the Makefile for the port to fix the issue is pretty
> simple. I figured I would soon see other people complainging about the issue.
> Since nobody has, I wonder if it is something in my environment.  Is anybody
> else having this issue?
> 
> uname -a shows I am running 
> 
> FreeBSD snake32.gta.com 11.0-ALPHA6 FreeBSD 11.0-ALPHA6 #0 r302305: Fri Jul  1 03:45:06 EDT 2016     root_at_snake32.gta.com:/usr/obj/usr/src/sys/GENERIC-NODEBUG  i386
> 
> 
> make config
> ===> Building/installing dialog4ports as it is required for the config dialog
> ===>  Cleaning for dialog4ports-0.1.5_2
> ===>  License BSD2CLAUSE accepted by the user
> ===>   dialog4ports-0.1.5_2 depends on file: /usr/local/sbin/pkg - found
> ===> Fetching all distfiles required by dialog4ports-0.1.5_2 for building
> ===>  Extracting for dialog4ports-0.1.5_2
> => SHA256 Checksum OK for dialog4ports-0.1.5.tar.gz.
> ===>  Patching for dialog4ports-0.1.5_2
> ===>  Configuring for dialog4ports-0.1.5_2
> ===>  Building for dialog4ports-0.1.5_2
> make[3]: "/usr/src/share/mk/src.libnames.mk" line 390: /usr/ports/ports-mgmt/dialog4ports/work/dialog4ports-0.1.5: These libraries should be LIBADD+=foo rather than DPADD/LDADD+=-lfoo:  ncursesw m dialog
> ===> Compilation failed unexpectedly.
> Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
> the maintainer.
> *** Error code 1
> 
> Stop.
> make[2]: stopped in /usr/ports/ports-mgmt/dialog4ports
> *** Error code 1
> 
> Stop.
> make[1]: stopped in /usr/ports/ports-mgmt/dialog4ports
> ===> Options unchanged
> 
> 

Are you sure the portsnap process finished successfully? It appears to
be trying to use the FreeBSD 9.x/10.x syntax for adding the dependencies
of dialog4ports, rather than the 11.x method.

-- 
Allan Jude