Will pkg(8) *ever* play nice?

2016-01-18 Thread Chris H
Greetings,
I was in the process of updating one of my development boxes
that runs -CURRENT. It's lagging a bit behind. So it required
a fresh, new "world". World built as expected. But the kernel
failed due to pkg(8). This box has an Nvidia video card. So
src.conf(5) has [among other ports entries]

PORTS_MODULES=x11/nvidia-driver-304

the [kernel] build failed due to pkg(8)

===> Ports module x11/nvidia-driver-304 (all)
cd ${PORTSDIR:-/usr/ports}/x11/nvidia-driver-304;
PATH=/usr/obj/usr/src/tmp/lega
cy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/bin:
/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/sbin:/bin:/usr/sbin:
/usr/bin:/usr/local/bin:/usr/local/sbin  SRC_BASE=/usr/src  OSVERSION=1100062 
W
RKDIRPREFIX=/usr/obj/usr/src/sys/DEVBOX make -B clean all
===>  Cleaning for nvidia-driver-304-304.128
===>  nvidia-driver-304-304.128 pkg(8) must be version 1.6.0 or greater, but
you have 1.4.12. You must upgrade the ports-mgmt/pkg port first.
*** Error code 1

Stop.
make[3]: stopped in /usr/ports/x11/nvidia-driver-304
*** Error code 1

Stop.
make[2]: stopped in /usr/obj/usr/src/sys/DEVBOX
*** Error code 1

Stop.
make[1]: stopped in /usr/src
*** Error code 1

..

Do I need to have FreeBSD-12 && ports/head from 12 installed *prior*
to building (upgrading)?!?
This feels like a chicken-v-egg thing. Is it possible to *remove*
pkg(8) && any dependency on it. Is this a bug in pkg(8) or just
a bug in my head?

Please help. As most of you already know; building/installing
world/kernel is a fairly time consuming process.

Thanks!

--Chris

--


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


FreeBSD ports you maintain which are out of date

2016-01-18 Thread portscout
Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
net-mgmt/weathermap | 1.1.1   | 4.0.0
+-+
science/libquantum  | 1.1.1   | 9.0.0
+-+
www/tikiwiki| 14.1| 14.2
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

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


Re: Will pkg(8) *ever* play nice?

2016-01-18 Thread Chris H
On Mon, 18 Jan 2016 00:26:39 -0800 "Chris H"  wrote

> Greetings,
> I was in the process of updating one of my development boxes
> that runs -CURRENT. It's lagging a bit behind. So it required
> a fresh, new "world". World built as expected. But the kernel
> failed due to pkg(8). This box has an Nvidia video card. So
> src.conf(5) has [among other ports entries]
> 
> PORTS_MODULES=x11/nvidia-driver-304
> 
> the [kernel] build failed due to pkg(8)
> 
> ===> Ports module x11/nvidia-driver-304 (all)
> cd ${PORTSDIR:-/usr/ports}/x11/nvidia-driver-304;
> PATH=/usr/obj/usr/src/tmp/lega
> cy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/b
> in:
> /usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/sbin:/bin:/usr/sb
> in: /usr/bin:/usr/local/bin:/usr/local/sbin  SRC_BASE=/usr/src 
> OSVERSION=1100062  W
> RKDIRPREFIX=/usr/obj/usr/src/sys/DEVBOX make -B clean all
> ===>  Cleaning for nvidia-driver-304-304.128
> ===>  nvidia-driver-304-304.128 pkg(8) must be version 1.6.0 or greater, but
> you have 1.4.12. You must upgrade the ports-mgmt/pkg port first.
> *** Error code 1
> 
> Stop.
> make[3]: stopped in /usr/ports/x11/nvidia-driver-304
> *** Error code 1
> 
> Stop.
> make[2]: stopped in /usr/obj/usr/src/sys/DEVBOX
> *** Error code 1
> 
> Stop.
> make[1]: stopped in /usr/src
> *** Error code 1
> 
> ..
> 
> Do I need to have FreeBSD-12 && ports/head from 12 installed *prior*
> to building (upgrading)?!?
> This feels like a chicken-v-egg thing. Is it possible to *remove*
> pkg(8) && any dependency on it. Is this a bug in pkg(8) or just
> a bug in my head?
> 
> Please help. As most of you already know; building/installing
> world/kernel is a fairly time consuming process.
> 
> Thanks!
> 
OK. It's late, and I'm ready to call it a day.
It's probably a bug in my head. I *probably* should have
upgraded pkg(8) after svn up'ing src && ports, and *prior*
to making worls &&  kernel.
So I'm going to take a chance, and:

cd /usr/obj
chflags -R noschg *
cd /
rm -r /usr/obj

cd /usr/ports/ports-mgmt/pkg
make; make deinstall && make resinstall clean
cd /usr/src
and make world, and kernel, and see how it goes.

--Chris


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


Re: error upgrading graphics/dri port "/usr/local/llvm36/bin/clang: not found"

2016-01-18 Thread Brooks Davis
On Sun, Jan 17, 2016 at 07:08:14PM +1100, Graham Menhennitt wrote:
> Does anybody have any clues, please?
> 
> Thanks,
> Graham
> 
> root@starker# uname -a
> FreeBSD starker 11.0-CURRENT FreeBSD 11.0-CURRENT #17 r294103: Sun Jan
> 17 13:26:05 AEDT 2016
> gfm@starker:/usr/obj/usr/data/FreeBSD/src_11-Current/sys/starker  amd64
> root@starker# ll /usr/local/llvm36/bin
> total 22384
> -rwxr-xr-x  1 root  wheel277720 Jan  6 19:54 bugpoint
> -rwxr-xr-x  1 root  wheel  18292472 Sep 25 07:49 clang-cpp
> -rwxr-xr-x  1 root  wheel  7288 Jan  6 19:53 count
> -r-xr-xr-x  2 root  wheel220280 Jan  6 19:54 FileCheck
> -r-xr-xr-x  4 root  wheel82 Jan  6 19:54 lit
> -rwxr-xr-x  1 root  wheel117368 Jan  6 19:54 llc
> -rwxr-xr-x  1 root  wheel 96128 Jan  6 19:54 lli
> -rwxr-xr-x  1 root  wheel 14648 Jan  6 19:54 lli-child-target
> -rwxr-xr-x  1 root  wheel 58200 Jan  6 19:54 llvm-ar
> -rwxr-xr-x  1 root  wheel 16960 Jan  6 19:54 llvm-as
> -rwxr-xr-x  1 root  wheel 46088 Jan  6 19:54 llvm-bcanalyzer
> -rwxr-xr-x  1 root  wheel 91416 Jan  6 19:54 llvm-config
> -rwxr-xr-x  1 root  wheel 92552 Jan  6 19:54 llvm-cov
> -rwxr-xr-x  1 root  wheel 49200 Jan  6 19:54 llvm-diff
> -rwxr-xr-x  1 root  wheel 20432 Jan  6 19:54 llvm-dis
> -rwxr-xr-x  1 root  wheel 32992 Jan  6 19:54 llvm-dsymutil
> -rwxr-xr-x  1 root  wheel 24888 Jan  6 19:54 llvm-dwarfdump
> -rwxr-xr-x  1 root  wheel 33008 Jan  6 19:54 llvm-extract
> -rwxr-xr-x  1 root  wheel 24904 Jan  6 19:54 llvm-link
> -r-xr-xr-x  4 root  wheel82 Jan  6 19:54 llvm-lit
> -rwxr-xr-x  1 root  wheel 74560 Jan  6 19:54 llvm-mc
> -rwxr-xr-x  1 root  wheel 18072 Jan  6 19:54 llvm-mcmarkup
> -rwxr-xr-x  1 root  wheel 79432 Jan  6 19:54 llvm-nm
> -rwxr-xr-x  1 root  wheel244848 Jan  6 19:54 llvm-objdump
> -rwxr-xr-x  1 root  wheel 46400 Jan  6 19:54 llvm-profdata
> lrwxr-xr-x  1 root  wheel 7 Jan  6 19:54 llvm-ranlib -> llvm-ar
> -rwxr-xr-x  1 root  wheel314824 Jan  6 19:54 llvm-readobj
> -rwxr-xr-x  1 root  wheel 52520 Jan  6 19:54 llvm-rtdyld
> -rwxr-xr-x  1 root  wheel 64744 Jan  6 19:54 llvm-size
> -rwxr-xr-x  1 root  wheel 64640 Jan  6 19:54 llvm-stress
> -rwxr-xr-x  1 root  wheel 64736 Jan  6 19:54 llvm-symbolizer
> -rwxr-xr-x  1 root  wheel   1622424 Jan  6 19:53 llvm-tblgen
> -rwxr-xr-x  1 root  wheel 39064 Jan  6 19:54 llvm-vtabledump
> -rwxr-xr-x  1 root  wheel 36944 Jan  6 19:54 macho-dump
> -rwxr-xr-x  1 root  wheel 41112 Jan  6 19:53 not
> -rwxr-xr-x  1 root  wheel 47168 Jan  6 19:54 obj2yaml
> -rwxr-xr-x  1 root  wheel302320 Jan  6 19:54 opt
> -rwxr-xr-x  1 root  wheel 34264 Jan  6 19:54 verify-uselistorder
> -rwxr-xr-x  1 root  wheel 66032 Jan  6 19:54 yaml2obj
> root@starker# pkg info|grep llvm
> llvm36-3.6.2_2 Low Level Virtual Machine
> root@starker# portupgrade -aWw
> [Reading data from pkg(8) ... - 854 packages found - done]
> --->  Upgrading 'dri-11.0.7_1,2' to 'dri-11.0.8,2' (graphics/dri)
> --->  Building '/usr/ports/graphics/dri'
> ===>   dri-11.0.8,2 depends on executable: makedepend - found
> ===>   dri-11.0.8,2 depends on package: libclc>=0.0.r222830 - not found
> ===>  Building for libclc-0.1.0.20150710
> [8/979] LLVM-CC r600--/lib/math/mad.cl.cedar.bc
> FAILED: /usr/local/llvm36/bin/clang -MMD -MF
> r600--/lib/math/mad.cl.cedar.bc.d -target r600-- -I`dirname
> generic/lib/math/mad.cl` -Igeneric/include -fno-builtin
> -Dcl_clang_storage_class_specifiers -Dcl_khr_fp64 -Dcles_khr_int64
> -D__CLC_INTERNAL -emit-llvm -mcpu=cedar -c -o
> r600--/lib/math/mad.cl.cedar.bc generic/lib/math/mad.cl
> /bin/sh: /usr/local/llvm36/bin/clang: not found
> [8/979] LLVM-CC r600--/lib/math/tables.cl.cedar.bc
> FAILED: /usr/local/llvm36/bin/clang -MMD -MF
> r600--/lib/math/tables.cl.cedar.bc.d -target r600-- -I`dirname
> generic/lib/math/tables.cl` -Igeneric/include -fno-builtin
> -Dcl_clang_storage_class_specifiers -Dcl_khr_fp64 -Dcles_khr_int64
> -D__CLC_INTERNAL -emit-llvm -mcpu=cedar -c -o
> r600--/lib/math/tables.cl.cedar.bc generic/lib/math/tables.cl
> /bin/sh: /usr/local/llvm36/bin/clang: not found
> ...

You appear not to have lang/clang36 installed.  I don't know why
portupgrade isn't installing it since it is a BUILD_DEPEND of
graphics/dri, but installing it by hand should work around the problem.

-- Brooks


signature.asc
Description: PGP signature


Re: error upgrading graphics/dri port "/usr/local/llvm36/bin/clang: not found"

2016-01-18 Thread Graham Menhennitt

On 19/01/2016 6:31 AM, Brooks Davis wrote:

On Sun, Jan 17, 2016 at 07:08:14PM +1100, Graham Menhennitt wrote:

Does anybody have any clues, please?

Thanks,
 Graham

root@starker# portupgrade -aWw
[Reading data from pkg(8) ... - 854 packages found - done]
--->  Upgrading 'dri-11.0.7_1,2' to 'dri-11.0.8,2' (graphics/dri)
--->  Building '/usr/ports/graphics/dri'
===>   dri-11.0.8,2 depends on executable: makedepend - found
===>   dri-11.0.8,2 depends on package: libclc>=0.0.r222830 - not found
===>  Building for libclc-0.1.0.20150710
[8/979] LLVM-CC r600--/lib/math/mad.cl.cedar.bc
FAILED: /usr/local/llvm36/bin/clang -MMD -MF
r600--/lib/math/mad.cl.cedar.bc.d -target r600-- -I`dirname
generic/lib/math/mad.cl` -Igeneric/include -fno-builtin
-Dcl_clang_storage_class_specifiers -Dcl_khr_fp64 -Dcles_khr_int64
-D__CLC_INTERNAL -emit-llvm -mcpu=cedar -c -o
r600--/lib/math/mad.cl.cedar.bc generic/lib/math/mad.cl
/bin/sh: /usr/local/llvm36/bin/clang: not found
...

You appear not to have lang/clang36 installed.  I don't know why
portupgrade isn't installing it since it is a BUILD_DEPEND of
graphics/dri, but installing it by hand should work around the problem.

-- Brooks

Indeed, it does fix it. Thanks for your help.

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


Fw: Unexpected dependencies of graphics/libGL

2016-01-18 Thread Luís Fernando Schultz Xavier da Silveira


Begin forwarded message:

Date: Sun, 17 Jan 2016 03:19:23 +
From: Luís Fernando Schultz Xavier da Silveira 
To: freebsd-questi...@freebsd.org
Subject: Unexpected dependencies of graphics/libGL


Hello,

Since the beginning of this year, graphics/libGL and friends started
depending on a significant amount of software, including git and bzr.
Could anyone explain why that is and whether it is possible to avoid
such dependencies?

Also, there is a dependency on clang and llvm from ports because of
advanced features that I (and I guess many of us) do not require.
I believe it has to do with the Gallium driver and OpenCL.

Just a suggestion: it would be pretty nice if there were some port
knobs to avoid pulling in another toolchain from ports to build
software that is never run.

Thank you,
Luís Fernando

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


Re: Unexpected dependencies of graphics/libGL

2016-01-18 Thread Manfred Antar

> On Jan 18, 2016, at 8:49 PM, Luís Fernando Schultz Xavier da Silveira 
>  wrote:
> 
> 
> 
> Begin forwarded message:
> 
> Date: Sun, 17 Jan 2016 03:19:23 +
> From: Luís Fernando Schultz Xavier da Silveira 
> To: freebsd-questi...@freebsd.org
> Subject: Unexpected dependencies of graphics/libGL
> 
> 
> Hello,
> 
> Since the beginning of this year, graphics/libGL and friends started
> depending on a significant amount of software, including git and bzr.
> Could anyone explain why that is and whether it is possible to avoid
> such dependencies?
> 
> Also, there is a dependency on clang and llvm from ports because of
> advanced features that I (and I guess many of us) do not require.
> I believe it has to do with the Gallium driver and OpenCL.
> 
> Just a suggestion: it would be pretty nice if there were some port
> knobs to avoid pulling in another toolchain from ports to build
> software that is never run.
> 
> Thank you,
> Luís Fernando

As an added note
the new dependencies also break the build on Sparc64
clang will not build on Sparc64 although llvm will.
So i’m stuck with the earlier version of dri libGl etc.
If there was a way to turn off the depend on clang llvm it would be nice.
Manfred

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