Re: kde5/qt5 problem

2020-04-16 Thread The Doctor via freebsd-ports
On Thu, Apr 16, 2020 at 05:08:59PM +0200, Adriaan de Groot wrote:
> On Thursday, 16 April 2020 00:05:02 CEST The Doctor wrote:
> > On Wed, Apr 15, 2020 at 09:20:17PM +0200, Adriaan de Groot wrote:
> > > Qt ports are annoying like that; it's an incompatibility between pre-5.14
> > > and (current) 5.14 where it picks up the wrong CMake support bits.
> > > Uninstall Qt < 5.14, then build Qt 5.14. Or use poudriere, which builds
> > > in a clean environment.
> > 
> > All right, just that I use portmaster.  How can I use poudriere for this?
> 
> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing-poudriere.html
> 
> That's from the perspective of someone working on the ports themselves, not 
> so 
> much for the consumer of ports, but it'll do to get you started.
> 
> [ade]


Will do.

-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
https://www.empire.kred/ROOTNK?t=94a1f39b  Look at Psalms 14 and 53 on Atheism
All appears to change when we change.  -Henri-Fr=C3=A9d=C3=A9ric Amiel
___
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: editors/atom: build error on 13.0-CURRENT

2020-04-16 Thread Vidar Karlsen

On 4/16/20 6:49 AM, Dimitry Andric wrote:

On 15 Apr 2020, at 22:14, Vidar Karlsen  wrote:

BUILDING.md says it needs llvm 3.3 or higher, and I have clang 10.0.0. Is this 
simply a version check gone wrong in node?


Very likely. When FreeBSD went to version 10, lots of sloppy configure
scripts then started to assume they were dealing with FreeBSD 1.x, and
did *strange* things. I would look for an expression "1*" in the
script. :)


You are right, Dimitri. I found that there is already an issue for this 
upstream: https://github.com/nodejs/node/issues/29536



--
Vidar Karlsen
___
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"


New feature suggestion: print-gh-tuple: Print GH_TUPLE corresponding to submodules of a GitHub repository ${GH_ACCOUNT}/${GH_PROJECT}

2020-04-16 Thread Yuri

Hi,


I am suggesting a new feature: make print-gh-tuple


https://reviews.freebsd.org/D24231


It works when USE_GITHUB=yes is set.

When a GitHub repository has git submodules, that themselves can also 
have embedded submodules, it can traverse all of them and output the 
value of GH_TUPLE that would include all of them.


This is quite tedious and difficult to do manually.

It checks out the GitHub repository with submodules, traverses the list 
using a combination of shell and awk scripting, and prints GH_TUPLE that 
can be pasted into a ports's Makefile.



Yuri

___
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: kde5/qt5 problem

2020-04-16 Thread Pau Amma

On 2020-04-16 17:08, Adriaan de Groot wrote:

On Thursday, 16 April 2020 00:05:02 CEST The Doctor wrote:


All right, just that I use portmaster.  How can I use poudriere for 
this?


https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing-poudriere.html

That's from the perspective of someone working on the ports themselves, 
not so

much for the consumer of ports, but it'll do to get you started.


For port consumers, there's also 
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-poudriere.html 
.

___
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: kde5/qt5 problem

2020-04-16 Thread Adriaan de Groot
On Thursday, 16 April 2020 00:05:02 CEST The Doctor wrote:
> On Wed, Apr 15, 2020 at 09:20:17PM +0200, Adriaan de Groot wrote:
> > Qt ports are annoying like that; it's an incompatibility between pre-5.14
> > and (current) 5.14 where it picks up the wrong CMake support bits.
> > Uninstall Qt < 5.14, then build Qt 5.14. Or use poudriere, which builds
> > in a clean environment.
> 
> All right, just that I use portmaster.  How can I use poudriere for this?

https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing-poudriere.html

That's from the perspective of someone working on the ports themselves, not so 
much for the consumer of ports, but it'll do to get you started.

[ade]

signature.asc
Description: This is a digitally signed message part.


Re: creating a new port from github: "_GH0" suffix in the filename

2020-04-16 Thread Marco Beishuizen

On Thu, 16 Apr 2020, the wise Mathieu Arnold wrote:


On Thu, Apr 16, 2020 at 01:20:20PM +0200, Marco Beishuizen wrote:

GH_TAGNAME= g0de4b1c


   ^
There is an extra g here, commit hash only use hexadecimals.


The name of the file is correct, except for the added "_GH0".
How can I download the file without the "_GH0" suffix?


The _GH0 suffix is fine :)


After some fiddling around, downloading worked after removing 
the "GH_TAGNAME" line, and adding "DISTVERSIONSUFFIX= -g0de4b1c".


The _GH0 suffix is indeed not a problem anymore.

Remain some plist issues, but that's another subject...

Thanks!
Marco
___
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: creating a new port from github: "_GH0" suffix in the filename

2020-04-16 Thread Mathieu Arnold
On Thu, Apr 16, 2020 at 01:20:20PM +0200, Marco Beishuizen wrote:
> GH_TAGNAME=   g0de4b1c

^
There is an extra g here, commit hash only use hexadecimals.

> The name of the file is correct, except for the added "_GH0".
> How can I download the file without the "_GH0" suffix?

The _GH0 suffix is fine :)

-- 
Mathieu Arnold


signature.asc
Description: PGP signature


creating a new port from github: "_GH0" suffix in the filename

2020-04-16 Thread Marco Beishuizen

Hi,

I'm trying to create a new port which is hosted on github (the luakit 
development version).


The Makefile is just a modified version of the one from www/luakit.
The Makefile I got so far is:

[...]
# Created by: Stefan Hagen 
# $FreeBSD: head/www/luakit/Makefile 531700 2020-04-14 15:49:36Z mat $

PORTNAME=   luakit-devel
DISTVERSION=2.1-33
PORTEPOCH=  1
CATEGORIES= www

MAINTAINER= mb...@xs4all.nl
COMMENT=Fast, small, webkit2 based browser framework extensible with Lua

LICENSE=GPLv3
LICENSE_FILE=   ${WRKSRC}/COPYING.GPLv3

NOT_FOR_ARCHS=  sparc64
NOT_FOR_ARCHS_REASON_sparc64=   Does not install on sparc64

BUILD_DEPENDS=  help2man:misc/help2man \
${LUA_MODLIBDIR}/lfs.so:devel/luafilesystem@${LUA_FLAVOR}
LIB_DEPENDS=libdbus-glib-1.so:devel/dbus-glib \
libsoup-2.4.so:devel/libsoup \
libfreetype.so:print/freetype2 \
libwebkit2gtk-4.0.so:www/webkit2-gtk3 \
libfontconfig.so:x11-fonts/fontconfig
RUN_DEPENDS=
${LUA_PKGNAMEPREFIX}luafilesystem>=0:devel/luafilesystem@${LUA_FLAVOR}

USES=   compiler:c++11-lang desktop-file-utils gettext-runtime gmake \
gnome lua:51 pkgconfig sqlite
USE_GITHUB= yes
GH_ACCOUNT= luakit
GH_PROJECT= luakit
GH_TAGNAME= g0de4b1c
USE_GNOME=  cairo gdkpixbuf2 glib20 gtk30

OPTIONS_DEFINE= DOCS LUAJIT
LUAJIT_DESC=Use the Just-In-Time compiler for lua
LUAJIT_LIB_DEPENDS= libluajit-5.1.so:lang/luajit
LUAJIT_MAKE_ARGS=   USE_LUAJIT=1
LUAJIT_MAKE_ARGS_OFF=   USE_LUAJIT=0

CONFLICTS_INSTALL=  luakit

post-extract:
@${REINPLACE_CMD} -e \
's|share/man|man| ; s|luakit/doc|doc/luakit| ; \
s|/etc/xdg|${PREFIX}/etc/xdg| ; /MANPREFIX */s|?=|=| ; \
s|gnu99|gnu11| ; s|-ggdb||' \
${WRKSRC}/config.mk
@${REINPLACE_CMD} -e 's|bin/env lua|&${LUA_VER_STR}|' \
${WRKSRC}/build-utils/gentokens.lua

post-install:
${STRIP_CMD} ${STAGEDIR}${PREFIX}/bin/luakit

.include 
[...]

The tarball isn't downloaded because "_GH0" is being added to the name of 
the file to be downloaded. So I get an error message:


[...]
=> luakit-luakit-2.1-33-gOde4b1c_GH0.tar.gz doesn't seem to exist in 
/usr/ports/distfiles/.
=> Attempting to fetch 
https://codeload.github.com/luakit/luakit/tar.gz/gOde4b1c?dummy=/luakit-luakit-2.1-33-gOde4b1c_GH0.tar.gz
fetch: 
https://codeload.github.com/luakit/luakit/tar.gz/gOde4b1c?dummy=/luakit-luakit-2.1-33-gOde4b1c_GH0.tar.gz: 
Not Found
=> Attempting to fetch 
http://distcache.FreeBSD.org/ports-distfiles/luakit-luakit-2.1-33-gOde4b1c_GH0.tar.gz
fetch: 
http://distcache.FreeBSD.org/ports-distfiles/luakit-luakit-2.1-33-gOde4b1c_GH0.tar.gz: 
Not Found

=> Couldn't fetch it - please try to retrieve this
=> port manually into /usr/ports/distfiles/ and try again.
*** Error code 1
[...]

The name of the file is correct, except for the added "_GH0".
How can I download the file without the "_GH0" suffix?

Thanks,
Marco

--
My own dear love, he is strong and bold
And he cares not what comes after.
His words ring sweet as a chime of gold,
And his eyes are lit with laughter.
He is jubilant as a flag unfurled --
Oh, a girl, she'd not forget him.
My own dear love, he is all my world --
And I wish I'd never met him.
-- Dorothy Parker, part 1
___
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: editors/atom: build error on 13.0-CURRENT

2020-04-16 Thread Dimitry Andric
On 15 Apr 2020, at 22:14, Vidar Karlsen  wrote:
> 
> I'm getting an error building editors/atom on 13.0-CURRENT:
>> ===>  Building for atom-ide-1.45.0
>> cd /usr/ports/editors/atom/work/node-v10.2.1 [...]
>> WARNING: C++ compiler too old, need g++ 4.9.4 or clang++ 3.4.2 (CXX=c++)
>> ERROR: Did not find a new enough assembler, install one or build with
>>   --openssl-no-asm.
>>   Please refer to BUILDING.md
> 
> Adding --openssl-no-asm to the ./configure line (Makefile line 115) seems to 
> bypass the problem, and it builds, runs and works fine as far as I can see, 
> but I don't know if this can affect some of the functionality.
> 
> BUILDING.md says it needs llvm 3.3 or higher, and I have clang 10.0.0. Is 
> this simply a version check gone wrong in node?

Very likely. When FreeBSD went to version 10, lots of sloppy configure
scripts then started to assume they were dealing with FreeBSD 1.x, and
did *strange* things. I would look for an expression "1*" in the
script. :)

-Dimitry



signature.asc
Description: Message signed with OpenPGP


Re: BIND 9.16.2 failing on RPI3 running 12.1-STABLE

2020-04-16 Thread Mathieu Arnold
On Thu, Apr 16, 2020 at 05:57:07PM +1200, Jonathan Chen wrote:
> Hi,
> 
> I'm currently running BIND on an RPI3, and the latest update to
> bind-9.16.2 currently fails to with:
> 
> Apr 16 17:39:26 topaz named[64497]: starting BIND 9.16.2 (Stable
> Release) 
> Apr 16 17:39:26 topaz named[64497]: running on FreeBSD arm64
> 12.1-STABLE FreeBSD 12.1-STABLE #0 r358927: Sun Mar 15 22:24:30 NZDT
> 2020 jo
> n...@onyx.inside.chen.org.nz:/xbuilds/rpi3/obj/usr/src/arm64.aarch64/sys/GENERIC
> Apr 16 17:39:26 topaz named[64497]: built with '--disable-linux-caps'
> '--localstatedir=/var' '--sysconfdir=/usr/local/etc/namedb'
> '--with-dlo
> pen=yes' '--with-libxml2' '--with-openssl=/usr'
> '--with-readline=-L/usr/local/lib -ledit' '--with-dlz-filesystem=yes'
> '--disable-dnstap' '--d
> isable-fixed-rrset' '--disable-geoip' '--without-maxminddb'
> '--without-gssapi' '--with-libidn2=/usr/local' '--with-json-c'
> '--disable-largefi
> le' '--with-lmdb=/usr/local' '--disable-native-pkcs11'
> '--without-python' '--disable-querytrace'
> 'STD_CDEFINES=-DDIG_SIGCHASE=1' '--enable-tc
> p-fastopen' '--with-tuning=default' '--disable-symtable'
> '--prefix=/usr/local' '--mandir=/usr/local/man'
> '--infodir=/usr/local/share/info/' '
> --build=aarch64-portbld-freebsd12.1'
> 'build_alias=aarch64-portbld-freebsd12.1' 'CC=cc' 'CFLAGS=-O2 -pipe
> -DLIBICONV_PLUG -fstack-protector-st
> rong -isystem /usr/local/include -fno-strict-aliasing ' 'LDFLAGS=
> -L/usr/local/lib -ljson-c -fstack-protector-strong '
> 'LIBS=-L/usr/local/lib
> ' 'CPPFLAGS=-DLIBICONV_PLUG -isystem /usr/local/include' 'CPP=cpp'
> 'PKG_CONFIG=pkgconf'
> Apr 16 17:39:26 topaz named[64497]: running as: named -4 -t /var/named
> -u bind -c /usr/local/etc/namedb/named.conf
> Apr 16 17:39:26 topaz named[64497]: compiled by CLANG FreeBSD Clang
> 9.0.1 (g...@github.com:llvm/llvm-project.git
> c1a0a213378a458fbea1a5c77b315
> c7dce08fd05)
> Apr 16 17:39:26 topaz named[64497]: compiled with OpenSSL version:
> OpenSSL 1.1.1d-freebsd  10 Sep 2019
> Apr 16 17:39:26 topaz named[64497]: linked to OpenSSL version: OpenSSL
> 1.1.1d-freebsd  10 Sep 2019
> Apr 16 17:39:26 topaz named[64497]: compiled with libxml2 version: 2.9.10
> Apr 16 17:39:26 topaz named[64497]: linked to libxml2 version: 20910
> Apr 16 17:39:26 topaz named[64497]: compiled with json-c version: 0.13.1
> Apr 16 17:39:26 topaz named[64497]: linked to json-c version: 0.13.1
> Apr 16 17:39:26 topaz named[64497]: compiled with zlib version: 1.2.11
> Apr 16 17:39:26 topaz named[64497]: linked to zlib version: 1.2.11
> Apr 16 17:39:26 topaz named[64497]:
> 
> Apr 16 17:39:26 topaz named[64497]: BIND 9 is maintained by Internet
> Systems Consortium,
> Apr 16 17:39:26 topaz named[64497]: Inc. (ISC), a non-profit 501(c)(3)
> public-benefit
> Apr 16 17:39:26 topaz named[64497]: corporation.  Support and training
> for BIND 9 are
> Apr 16 17:39:26 topaz named[64497]: available at https://www.isc.org/support
> Apr 16 17:39:26 topaz named[64497]:
> 
> Apr 16 17:39:26 topaz named[64497]: command channel listening on 127.0.0.1#953
> Apr 16 17:39:26 topaz named[64497]: netmgr.c:995:
> REQUIRE(worker->recvbuf_inuse) failed
> Apr 16 17:39:26 topaz named[64497]: exiting (due to assertion failure)
> Apr 16 17:39:26 topaz kernel: pid 64497 (named), jid 0, uid 53: exited
> on signal 6
> 
> The last version of bind916 that works is bind916-9.16.0_2.txz. 9.16.1
> also fails with an assertion error on netmgr.c.

https://gitlab.isc.org/isc-projects/bind9/-/issues/1761

It seems the problem is libuv 1.36.

-- 
Mathieu Arnold


signature.asc
Description: PGP signature


FreeBSD ports you maintain which are out of date

2020-04-16 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
+-+
devel/codequery | 0.21.1  | v0.23.0
+-+


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

Reported by:portscout!
___
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"