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

2016-07-05 Thread Larry Baird
>> 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.
>>
> 
> Nope the opposite :)
> 
> dialog4ports uses bsd.prog.mk, somehow his make ends up using the one from
> the
> source tree rather than the one from /usr/share/mk. The one from the
> sourcetree
> is having src.libnames.mk which is not supposed to be used
> 
> Larry do you have any variable ENV or /etc/make.conf that defines MAKESYSPATH
> to
> /usr/src/share/mk?

Thanks. That was it. I need to do some digging. For some reason I added 
following to my .shrc file.
MAKESYSPATH=.../usr/src/share/mk

Removing it fixes the issue.  I can't remember what this fixed for me. Back
to the drawing board to do some experimenting to see.

Larry
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


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

2016-07-01 Thread Allan Jude
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 
> r...@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



signature.asc
Description: OpenPGP digital signature


Unable to 'make config' ports under FreeBSD current

2016-07-01 Thread Larry Baird
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 r...@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


-- 

Larry Baird
Global Technology Associates, Inc. 1992-2012| http://www.gta.com
Celebrating Twenty Years of Software Innovation | Orlando, FL
Email: l...@gta.com | TEL 407-380-0220
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"