Re: qemu-aarch64-static

2017-08-21 Thread Andrea Venturoli 

On 08/17/17 21:22, Jan Beich wrote:


Yep. Link the binary (i.e. "date") statically or run it inside jail/chroot.
Otherwise, /libexec/ld-elf.so.1 references the host system, which on amd64
wouldn't recognize aarch64 shared libraries.


Thanks a lot.
Now it seems so obvious to me, but I really wouldn't have thought about 
this little detail :)





That page is a bit out of date. Nowadays building for aarch64 is as simple as

   $ pkg install poudriere qemu-user-static
   $ service qemu_user_static onestart
   $ poudriere jail -cj 111aarch64 -a arm64.aarch64 -v 11.1-RELEASE
   $ poudriere bulk -j 111aarch64 category/port


I can confirm this is working.




To speed up port builds you may want to consider using native
cross-toolchain by creating a jail with -x flag.


Do you have any more info on this?
Except from poudriere's man page's description I could find no other 
docs. Is there any more elaborate description on what this does and how?


I built the jail with -x, but how do I check it's using "native-xtools"?

I tried building ports-mgmt/pkg and it requires ten times more than 
native build (i.e. 24 minutes for aarch64 vs. less than 3 minutes for 
amd64). Is this normal?




 bye & Thanks
av.
___
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: Synth and circular dependencies

2017-08-21 Thread Don Lewis 
On 21 Aug, To: mueller6...@bellsouth.net wrote:
> On 22 Aug, Thomas Mueller wrote:
>> Again, I am responding from the FreeBSD mailing list web interface
>> because that is faster than reaching my inbox.
>> 
>> from Don Lewis truckman at FreeBSD.org
>> Mon Aug 21 23:16:36 UTC 2017
>> 
>>> > I went to /usr/ports/textproc/xmlto , ran "make all-depends-list",
>>> > and one line that showed up was
>>> > /usr/ports/textproc/xmlto
>>  
>>> > depends on itself.
>> 
>>> I don't see that here with default option settings:
>> 
>>> %cd /usr/ports/textproc/xmlto && make all-depends-list | grep
>>> textproc
>>> /usr/ports/textproc/libxml2
>>> /usr/ports/textproc/libxslt
>>> /usr/ports/textproc/docbook-xsl
>>> /usr/ports/textproc/xmlcatmgr
>>> /usr/ports/textproc/docbook
>>> /usr/ports/textproc/docbook-sgml
>>> /usr/ports/textproc/iso8879
>>> /usr/ports/textproc/docbook-xml
>>> /usr/ports/textproc/xmlcharent
>>> /usr/ports/textproc/sdocbook-xml
>> 
>>> > Otherwise, on newer system, I see circular dependencies running
>>> > "make all-depends-list", finding textproc/xmlto depended on
>>> > graphics/gd and vice versa.
>> 
>>> I don't see the former:
>> 
>>> %cd /usr/ports/textproc/xmlto && make all-depends-list | grep
>>> graphics
>>> [nada]
>> 
>>> or the latter:
>> 
>>> %cd /usr/ports/graphics/gd && make all-depends-list | grep textproc 
>>> /usr/ports/textproc/expat2
>> 
>>> This is with the head branch of the ports tree, revision r448344.
>> 
>>> Problems like this with the default option settings tend to get found
>>> and fixed fairly quickly because this will cause failures on the
>>> package build cluster and will spam the maintainer's mailbox with
>>> build failure messages.
>> 
>> I didn't think I went overboard selecting options, but I did want
>> documentation.  Maybe that screwed up, or the ports tree was not up to
>> it.
>> 
>> I suppose I could move (mv) /var/db/ports to /var/db/ports2
>> temporarily just to see what happens when I "make all-depends-list".
>> 
>> I really need to be able to see the options in a better way than the
>> FreeBSD ports framework allows, like in a file /etc/mk.conf (pkgsrc)
>> or USE= ... as in /etc/make.conf (Gentoo portage).
>>
>> Dialog4ports is better than the previous dialog but not as good as
>> seeing in a file mk.conf or make.conf .
> 
> 
> It is possible to set the options for ports in /etc/make.conf.  That is
> how I handle it would poudriere which looks for make.conf files in

s/would/with/

> /usr/local/etc/poudriere.d and can use make.conf files that are specific
> to each jail, ports tree and ports set (poudriere -z option to specify
> the latter).
> 
> Specifying the options in make.conf also makes it easier to set options
> globally for all all of the ports that you build so they are consistent.
> For instance I specify these options globally:
> 
> OPTIONS_SET=CUPS APPLET OPENBLAS OBLAS SZIP LETTER GUILE2 GSSAPI_NONE KRB_NONE
> OPTIONS_UNSET=GUILE1 NETLIB REFERENCE GSSAPI_BASE KRB_BASE KERBEROS
> 
> Port-specific options can be set like this:
> 
> graphics_gimp-help_SET=EN
> graphics_gimp-help_UNSET=ALL
> 
> Back when I still used portupgrade, I found that dialog4ports got to be
> really frustrating.
> 
> ___
> 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@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Synth and circular dependencies

2017-08-21 Thread Don Lewis 
On 22 Aug, Thomas Mueller wrote:
> Again, I am responding from the FreeBSD mailing list web interface
> because that is faster than reaching my inbox.
> 
> from Don Lewis truckman at FreeBSD.org
> Mon Aug 21 23:16:36 UTC 2017
> 
>> > I went to /usr/ports/textproc/xmlto , ran "make all-depends-list",
>> > and one line that showed up was
>> > /usr/ports/textproc/xmlto
>  
>> > depends on itself.
> 
>> I don't see that here with default option settings:
> 
>> %cd /usr/ports/textproc/xmlto && make all-depends-list | grep
>> textproc
>> /usr/ports/textproc/libxml2
>> /usr/ports/textproc/libxslt
>> /usr/ports/textproc/docbook-xsl
>> /usr/ports/textproc/xmlcatmgr
>> /usr/ports/textproc/docbook
>> /usr/ports/textproc/docbook-sgml
>> /usr/ports/textproc/iso8879
>> /usr/ports/textproc/docbook-xml
>> /usr/ports/textproc/xmlcharent
>> /usr/ports/textproc/sdocbook-xml
> 
>> > Otherwise, on newer system, I see circular dependencies running
>> > "make all-depends-list", finding textproc/xmlto depended on
>> > graphics/gd and vice versa.
> 
>> I don't see the former:
> 
>> %cd /usr/ports/textproc/xmlto && make all-depends-list | grep
>> graphics
>> [nada]
> 
>> or the latter:
> 
>> %cd /usr/ports/graphics/gd && make all-depends-list | grep textproc 
>> /usr/ports/textproc/expat2
> 
>> This is with the head branch of the ports tree, revision r448344.
> 
>> Problems like this with the default option settings tend to get found
>> and fixed fairly quickly because this will cause failures on the
>> package build cluster and will spam the maintainer's mailbox with
>> build failure messages.
> 
> I didn't think I went overboard selecting options, but I did want
> documentation.  Maybe that screwed up, or the ports tree was not up to
> it.
> 
> I suppose I could move (mv) /var/db/ports to /var/db/ports2
> temporarily just to see what happens when I "make all-depends-list".
> 
> I really need to be able to see the options in a better way than the
> FreeBSD ports framework allows, like in a file /etc/mk.conf (pkgsrc)
> or USE= ... as in /etc/make.conf (Gentoo portage).
>
> Dialog4ports is better than the previous dialog but not as good as
> seeing in a file mk.conf or make.conf .


It is possible to set the options for ports in /etc/make.conf.  That is
how I handle it would poudriere which looks for make.conf files in
/usr/local/etc/poudriere.d and can use make.conf files that are specific
to each jail, ports tree and ports set (poudriere -z option to specify
the latter).

Specifying the options in make.conf also makes it easier to set options
globally for all all of the ports that you build so they are consistent.
For instance I specify these options globally:

OPTIONS_SET=CUPS APPLET OPENBLAS OBLAS SZIP LETTER GUILE2 GSSAPI_NONE KRB_NONE
OPTIONS_UNSET=GUILE1 NETLIB REFERENCE GSSAPI_BASE KRB_BASE KERBEROS

Port-specific options can be set like this:

graphics_gimp-help_SET=EN
graphics_gimp-help_UNSET=ALL

Back when I still used portupgrade, I found that dialog4ports got to be
really frustrating.

___
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: Synth and circular dependencies

2017-08-21 Thread Jonathan Chen 
On 22 August 2017 at 15:17, Thomas Mueller  wrote:
[...]
> I really need to be able to see the options in a better way than the FreeBSD 
> ports framework allows, like in a file /etc/mk.conf (pkgsrc) or USE= ... as 
> in /etc/make.conf (Gentoo portage).
>
> Dialog4ports is better than the previous dialog but not as good as seeing in 
> a file mk.conf or make.conf .
>
> Otherwise, I don't really know any elegant way to fix the options mess I got 
> into.

Any reason why don't you can't all your options into /etc/make.conf?
I've never used /var/db/ports options as they're not easy to review in
one go.

Cheers.
-- 
Jonathan Chen 
___
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: zabbix32-server and frontend fails to build on poudriere

2017-08-21 Thread Danilo G. Baio 
On Mon, Aug 21, 2017 at 10:01:20PM +0200, Johan Hendriks wrote:
> 
> 
> Op 21/08/2017 om 04:45 schreef Danilo G. Baio:
> > On Mon, Aug 21, 2017 at 12:12:19AM +0200, Johan Hendriks wrote:
> >> Hello all,
> >>
> >> It seems zabbix32-server and zabbix32-frontend fails to build with
> >> poudriere.
> >>
> >> This is the log from poudriere.
> >>
> >> zabbix32-frontend
> >>
> >> ==
> >> Unknown extension mysql for PHP 70.
> >> *** Error code 1
> > That's because mysql extension does not exist in PHP 7.0+
> > This should fix zabbix32-frontend:
> > https://people.freebsd.org/~dbaio/svn-patch-zabbix3-frontend-mysql.patch
> >
> >> And this I get from zabbix32-server
> >>
> >> configure: error: Not found mysqlclient library
> >> ===>  Script "configure" failed unexpectedly.
> >> Please report the problem to p...@pakhom.spb.ru [maintainer] and attach the
> >> "/wrkdirs/usr/ports/net-mgmt/zabbix32-server/work/zabbix-3.2.7/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
> > I wasn't able to reproduce this, could you send your list of port options 
> > and
> > the full build log?
> >
> > Regards.
> If I apply your patch, it will not build zabbix32_frontend with the
> following message
> Ignored: cannot be installed: doesn't work with lang/php70 port (doesn't
> support PHP 7.0)
> 


[net-mgmt/zabbix32-frontend]

The patch just removes MYSQL as default option.

It won't build with PHP70 if MYSQL is enabled.

It needs to be like this(poudriere log):

---Begin OPTIONS List---
===> The following configuration options are available for 
zabbix32-frontend-3.2.7:
 MYSQL=off: MySQL database support
 MYSQLI=on: MySQLI backend
 ORACLE=off: Oracle database support
 PGSQL=off: PostgreSQL database support
 SQLITE=off: SQLite database support
===> Use 'make config' to modify these settings
---End OPTIONS List---



> checking for mysql_config... /usr/local/bin/mysql_config
> checking for main in -l... no
> configure: error: Not found mysqlclient library
> ===>  Script "configure" failed unexpectedly.
> Please report the problem to p...@pakhom.spb.ru [maintainer] and attach the
> "/wrkdirs/usr/ports/net-mgmt/zabbix32-server/work/zabbix-3.2.7/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
> 
> Stop.
> make: stopped in /usr/ports/net-mgmt/zabbix32-server
> >> Cleaning up wrkdir
> ===>  Cleaning for zabbix32-server-3.2.7
> build of net-mgmt/zabbix32-server ended at Mon Aug 21 04:45:31 CEST 2017
> build time: 00:00:14
> !!! build failure encountered !!!
> 
> 
> My /etc/make.conf
> 
> BATCH_DELETE_OLD_FILES= yes
> WANT_OPENLDAP_SASL=yes
> DEFAULT_VERSIONS+=   pgsql=9.6 php=7.0 mysql=10.2m ssl=openssl apache=2.4
> 

[net-mgmt/zabbix32-server]

And you are using mariadb, I'll make some tests with this.

Regards.
-- 
Danilo G. Baio (dbaio)


signature.asc
Description: PGP signature

Re: Perl broken after upgrade

2017-08-21 Thread Masachika ISHIZUKA 
> After a recent update, it seems things that depend on Perl are
> broken. Any suggestions to fix are greatly appreciated.  Thanks in
> advance.
> 
  [snip]
> 
> Socket.c: loadable library and perl binaries are mismatched (got
> handshake key 0xd200080, needed 0xdf00080)

  Hi.

  I always do the following commands when loadable library and perl
binaries are mismatched.

# pkg info | grep '^p5-' | sed 's/ .*//' | xargs pkg install -fy
-- 
Masachika ISHIZUKA
___
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"

How to force defaulting to heimdal port - a surprise from postgresql96 using base

2017-08-21 Thread Dewayne Geraghty 
Just noticed that the postgresql96-server options
HEIMDAL_KRB5 MIT_KRB5
were removed, 11 days ago.  (They were inherited options defined in
postgresql92)

How do I tell /usr/ports/Mk/Uses/gssapi.mk that only the heimdal port
should be used, in the general sense - for all ports.

Ideally what I would like to do is to tell those ports that I want
kerberos to be used, to only use heimdal port; and preferably with the
bootstrap option to correctly set the build,run dependencies. Something
like:
GSSAPI_HEIMDAL_USES=gssapi:heimdal,bootstrap or
USES=gssapi:heimdal,bootstrap
and in some cases
GSSAPI_HEIMDAL_USES=gssapi:heimdal,bootstrap,flags
depending on how the Makefile is used.

In the absence of a DEFAULT_VERSIONS+=gssapi=heimdal|mit|base (ie
DEFAULT_VERSIONS+=ssl=openssl equivalence).  Would the creation of
/usr/ports/*/*/Makefile.local
that only contains
USES+=gssapi:heimdal,bootstrap
GSSAPI_HEIMDAL_USES=gssapi:heimdal,bootstrap
be the best solution, for all the ports I need to use kerberos?

But two questions arise:
1. How does the ports system process variables in USES?
2. If its a "first found" in the list, is there a way to prepend what is
required to the USES variable?

I would appreciate advise/help as to how I can reliably use the heimdal
port. 
Dewayne

___
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: Synth and circular dependencies

2017-08-21 Thread Don Lewis 
On 21 Aug, Thomas Mueller wrote:
> from RW rwmaillists at googlemail.com
> Mon Aug 21 15:28:49 UTC 2017:
> 
>> On Mon, 21 Aug 2017 13:19:24 +
>> Thomas Mueller wrote:
> 
> 
>> > But on this computer, no such system crashes, but I ran into
>> > circular dependencies
> 
>> Try removing any port options that aren't absolutely essential.
> 
>> > It seems the ports go overboard with an awful lot of dependencies,
>> > of which not all install with the main port.  So I expect some of
>> > these dependencies might be false dependencies.
> 
>> They are probably just build dependencies.
> 
> It is still disappointing to find devel/git or sysutils/coreutils were
> not installed.
> 
> Email from FreeBSD lists is slow coming to my inbox, so I am
> respoonding from the web interface to the emailing lists, and on the
> other computer, now running NetBSD.
> 
> I ran "make show-depends" on NetBSD with pkgsrc, dependencies are
> generally far less/fewer than on FreeBSD with ports.
> 
> But FreeBSD ports seems to go overboard now with dependencies,
> creating circular dependencies along the way.
> 
> I rebooted to an older FreeBSD installation (current/11 amd64 from
> January 2016, no longer supported).
> 
> I went to /usr/ports/textproc/xmlto , ran "make all-depends-list", and
> one line that showed up was
> /usr/ports/textproc/xmlto
> 
> depends on itself.

I don't see that here with default option settings:

%cd /usr/ports/textproc/xmlto && make all-depends-list | grep textproc
/usr/ports/textproc/libxml2
/usr/ports/textproc/libxslt
/usr/ports/textproc/docbook-xsl
/usr/ports/textproc/xmlcatmgr
/usr/ports/textproc/docbook
/usr/ports/textproc/docbook-sgml
/usr/ports/textproc/iso8879
/usr/ports/textproc/docbook-xml
/usr/ports/textproc/xmlcharent
/usr/ports/textproc/sdocbook-xml

> Otherwise, on newer system, I see circular dependencies running "make
> all-depends-list", finding textproc/xmlto depended on graphics/gd and
> vice versa.

I don't see the former:

%cd /usr/ports/textproc/xmlto && make all-depends-list | grep graphics
[nada]

or the latter:

%cd /usr/ports/graphics/gd && make all-depends-list | grep textproc 
/usr/ports/textproc/expat2

This is with the head branch of the ports tree, revision r448344.

Problems like this with the default option settings tend to get found
and fixed fairly quickly because this will cause failures on the package
build cluster and will spam the maintainer's mailbox with build failure
messages.


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

Bump portrevision on port

2017-08-21 Thread Jack L. 
Can someone please change the portrevision so the people who have
broken builds can recompile with the fixes? Thanks.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218104
___
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: Synth and circular dependencies

2017-08-21 Thread Thomas Mueller 
from RW rwmaillists at googlemail.com
Mon Aug 21 15:28:49 UTC 2017:

> On Mon, 21 Aug 2017 13:19:24 +
> Thomas Mueller wrote:


> > But on this computer, no such system crashes, but I ran into circular
> > dependencies 

> Try removing any port options that aren't absolutely essential.

> > It seems the ports go overboard with an awful lot of dependencies, of
> > which not all install with the main port.  So I expect some of these
> > dependencies might be false dependencies.

> They are probably just build dependencies.

It is still disappointing to find devel/git or sysutils/coreutils were not 
installed.

Email from FreeBSD lists is slow coming to my inbox, so I am respoonding from 
the web interface to the emailing lists, and on the other computer, now running 
NetBSD.

I ran "make show-depends" on NetBSD with pkgsrc, dependencies are generally far 
less/fewer than on FreeBSD with ports.

But FreeBSD ports seems to go overboard now with dependencies, creating 
circular dependencies along the way.

I rebooted to an older FreeBSD installation (current/11 amd64 from January 
2016, no longer supported).

I went to /usr/ports/textproc/xmlto , ran "make all-depends-list", and one line 
that showed up was
/usr/ports/textproc/xmlto

depends on itself.

Otherwise, on newer system, I see circular dependencies running "make 
all-depends-list", finding textproc/xmlto depended on graphics/gd and vice 
versa.

It didn't seem broken back in January 2016, and I still use it for Seamonkey 
2.39 and other things.


Tom

___
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: zabbix32-server and frontend fails to build on poudriere

2017-08-21 Thread Johan Hendriks 


Op 21/08/2017 om 04:45 schreef Danilo G. Baio:
> On Mon, Aug 21, 2017 at 12:12:19AM +0200, Johan Hendriks wrote:
>> Hello all,
>>
>> It seems zabbix32-server and zabbix32-frontend fails to build with
>> poudriere.
>>
>> This is the log from poudriere.
>>
>> zabbix32-frontend
>>
>> ==
>> Unknown extension mysql for PHP 70.
>> *** Error code 1
> That's because mysql extension does not exist in PHP 7.0+
> This should fix zabbix32-frontend:
> https://people.freebsd.org/~dbaio/svn-patch-zabbix3-frontend-mysql.patch
>
>> And this I get from zabbix32-server
>>
>> configure: error: Not found mysqlclient library
>> ===>  Script "configure" failed unexpectedly.
>> Please report the problem to p...@pakhom.spb.ru [maintainer] and attach the
>> "/wrkdirs/usr/ports/net-mgmt/zabbix32-server/work/zabbix-3.2.7/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
> I wasn't able to reproduce this, could you send your list of port options and
> the full build log?
>
> Regards.
If I apply your patch, it will not build zabbix32_frontend with the
following message
Ignored: cannot be installed: doesn't work with lang/php70 port (doesn't
support PHP 7.0)



I do not know a easy way to get all the options from the poudriere jail.
If you need more I will get it for you

Here are my ports options for zabbix32-server.

# This file is auto-generated by 'make config'.
# Options for zabbix32-server-3.2.7
_OPTIONS_READ=zabbix32-server-3.2.7
_FILE_COMPLETE_OPTIONS_LIST=CURL FPING IPMI IPV6 JABBER JAVAGW LDAP
LIBXML2 NMAP SSH MYSQL PGSQL SQLITE ORACLE IODBC UNIXODBC OPENSSL GNUTLS
POLARSSL
OPTIONS_FILE_SET+=CURL
OPTIONS_FILE_SET+=FPING
OPTIONS_FILE_UNSET+=IPMI
OPTIONS_FILE_SET+=IPV6
OPTIONS_FILE_UNSET+=JABBER
OPTIONS_FILE_UNSET+=JAVAGW
OPTIONS_FILE_SET+=LDAP
OPTIONS_FILE_SET+=LIBXML2
OPTIONS_FILE_UNSET+=NMAP
OPTIONS_FILE_SET+=SSH
OPTIONS_FILE_SET+=MYSQL
OPTIONS_FILE_UNSET+=PGSQL
OPTIONS_FILE_UNSET+=SQLITE
OPTIONS_FILE_UNSET+=ORACLE
OPTIONS_FILE_UNSET+=IODBC
OPTIONS_FILE_SET+=UNIXODBC
OPTIONS_FILE_SET+=OPENSSL
OPTIONS_FILE_UNSET+=GNUTLS
OPTIONS_FILE_UNSET+=POLARSSL

For php-extensions

# This file is auto-generated by 'make config'.
# Options for php70-extensions-1.1
_OPTIONS_READ=php70-extensions-1.1
_FILE_COMPLETE_OPTIONS_LIST=BCMATH BZ2 CALENDAR CTYPE CURL DBA DOM
ENCHANT EXIF FILEINFO FILTER FTP GD GETTEXT GMP HASH ICONV IMAP
INTERBASE INTL JSON LDAP MBSTRING MCRYPT MYSQLI ODBC OPCACHE OPENSS
L PCNTL PDF PDO PDO_DBLIB PDO_FIREBIRD PDO_MYSQL PDO_ODBC PDO_PGSQL
PDO_SQLITE PGSQL PHAR POSIX PSPELL READLINE RECODE SESSION SHMOP
SIMPLEXML SNMP SOAP SOCKETS SQLITE3 SYBASE_CT SYSVMSG SYSVSEM SYS
VSHM TIDY TOKENIZER WDDX XML XMLREADER XMLRPC XMLWRITER XSL ZIP ZLIB
OPTIONS_FILE_SET+=BCMATH
OPTIONS_FILE_SET+=BZ2
OPTIONS_FILE_UNSET+=CALENDAR
OPTIONS_FILE_SET+=CTYPE
OPTIONS_FILE_SET+=CURL
OPTIONS_FILE_UNSET+=DBA
OPTIONS_FILE_SET+=DOM
OPTIONS_FILE_UNSET+=ENCHANT
OPTIONS_FILE_SET+=EXIF
OPTIONS_FILE_SET+=FILEINFO
OPTIONS_FILE_SET+=FILTER
OPTIONS_FILE_SET+=FTP
OPTIONS_FILE_SET+=GD
OPTIONS_FILE_SET+=GETTEXT
OPTIONS_FILE_UNSET+=GMP
OPTIONS_FILE_SET+=HASH
OPTIONS_FILE_SET+=ICONV
OPTIONS_FILE_SET+=IMAP
OPTIONS_FILE_UNSET+=INTERBASE
OPTIONS_FILE_UNSET+=INTL
OPTIONS_FILE_SET+=JSON
OPTIONS_FILE_SET+=LDAP
OPTIONS_FILE_SET+=MBSTRING
OPTIONS_FILE_SET+=MCRYPT
OPTIONS_FILE_SET+=MYSQLI
OPTIONS_FILE_UNSET+=ODBC
OPTIONS_FILE_SET+=OPCACHE
OPTIONS_FILE_UNSET+=OPENSSL
OPTIONS_FILE_SET+=PCNTL
OPTIONS_FILE_SET+=PDF
OPTIONS_FILE_SET+=PDO
OPTIONS_FILE_UNSET+=PDO_DBLIB
OPTIONS_FILE_UNSET+=PDO_FIREBIRD
OPTIONS_FILE_SET+=PDO_MYSQL
OPTIONS_FILE_UNSET+=PDO_ODBC
OPTIONS_FILE_SET+=PDO_PGSQL
OPTIONS_FILE_SET+=PDO_SQLITE
OPTIONS_FILE_SET+=PGSQL
OPTIONS_FILE_SET+=PHAR
OPTIONS_FILE_SET+=POSIX
OPTIONS_FILE_UNSET+=PSPELL
OPTIONS_FILE_SET+=READLINE
OPTIONS_FILE_UNSET+=RECODE
OPTIONS_FILE_SET+=SESSION
OPTIONS_FILE_UNSET+=SHMOP
OPTIONS_FILE_SET+=SIMPLEXML
OPTIONS_FILE_SET+=SNMP
OPTIONS_FILE_SET+=SOAP
OPTIONS_FILE_UNSET+=SOCKETS
OPTIONS_FILE_SET+=SQLITE3
OPTIONS_FILE_UNSET+=SYBASE_CT
OPTIONS_FILE_UNSET+=SYSVMSG
OPTIONS_FILE_UNSET+=SYSVSEM
OPTIONS_FILE_SET+=SYSVSHM
OPTIONS_FILE_UNSET+=TIDY
OPTIONS_FILE_SET+=TOKENIZER
OPTIONS_FILE_UNSET+=WDDX
OPTIONS_FILE_SET+=XML
OPTIONS_FILE_SET+=XMLREADER
OPTIONS_FILE_UNSET+=XMLRPC
OPTIONS_FILE_SET+=XMLWRITER
OPTIONS_FILE_UNSET+=XSL
OPTIONS_FILE_SET+=ZIP
OPTIONS_FILE_SET+=ZLIB

And the full buildlog from the poudriere webgui.

>> Building net-mgmt/zabbix32-server
build started at Mon Aug 21 04:45:17 CEST 2017
port directory: /usr/ports/net-mgmt/zabbix32-server
building for: FreeBSD pkg.netaffairs.nl 11.1-RELEASE FreeBSD 11.1-RELEASE amd64
maintained by: p...@pakhom.spb.ru
Makefile ident:  $FreeBSD: head/net-mgmt/zabbix32-server/Makefile 448072 
2017-08-16 23:38:57Z dbaio $
Poudriere version: 3.1.19
Host OSVERSION:

Re: security/libressl: Add the possibility to build only libtls

2017-08-21 Thread David Wahlund 

On 2017-08-21 11:59, David Wahlund wrote:

Hi
I'd like to use the libtls library of LibreSSL on FreeBSD. Or the python
bindings to libtls specifically. I do NOT however want to replace
openssl or use the libssl library.

From what I understand it would be possible in practice as I assume it's
only libssl that overwrites files used by openssl.

Would it be possible to create an option in LibreSSL, or preferably make
a separate port, for libtls only? That way future ports can depend on
libtls only. For example a future python-libtls port could depend on that.

-David


I guess it's the libtls-standalone I'm after. It's on GitHub.

https://github.com/libressl-portable/portable/tree/master/libtls-standalone
___
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: security/libressl: Add the possibility to build only libtls

2017-08-21 Thread David Wahlund 



On 2017-08-21 16:55, Mathieu Arnold wrote:

Le 21/08/2017 à 12:03, Franco Fichtner a écrit :

On 21. Aug 2017, at 11:59 AM, David Wahlund  wrote:

I'd like to use the libtls library of LibreSSL on FreeBSD. Or the python 
bindings to libtls specifically. I do NOT however want to replace openssl or 
use the libssl library.

From what I understand it would be possible in practice as I assume it's only 
libssl that overwrites files used by openssl.

Would it be possible to create an option in LibreSSL, or preferably make a 
separate port, for libtls only? That way future ports can depend on libtls 
only. For example a future python-libtls port could depend on that.


Unless you build your own packages with OpenSSL from ports
you can just install LibreSSL and use it in your programs...

# pkg install libressl

OpenSSL lives in the base system, LibreSSL will be an optional
install under /usr/local.



That is not quite true. As soon as you install openssl, openssl-devel,
or libressl or libressl-devel, the ports framework will use it whenever
you build something that needs SSL from the ports tree.


If you truly want to have libressl but do not want to use it for
building ports, you will need to install it in a separate PREFIX.




Well the problem is that libressl is TWO libraries (actually three but 
nm). One that replaces openssl (libssl) and one that doesn't (libtls). 
However the libtls has shared dependencies with libssl. I DO want to use 
libtls for ports that has that dependency, but NOT use it to replace 
openssl. Libtls CAN be a separate dependency in parallel to openssl from 
what I understand. But now the libressl port conflicts with the openssl 
port even though parts of it is not in conflict and I don't think the 
shared parts between libssl and libtls are in conflict with openssl. But 
I might be wrong. So what I'm looking for is a way to use libtls but NOT 
use libssl.

___
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: Synth and circular dependencies

2017-08-21 Thread RW via freebsd-ports 
On Mon, 21 Aug 2017 13:19:24 +
Thomas Mueller wrote:


> But on this computer, no such system crashes, but I ran into circular
> dependencies 

Try removing any port options that aren't absolutely essential.

> It seems the ports go overboard with an awful lot of dependencies, of
> which not all install with the main port.  So I expect some of these
> dependencies might be false dependencies.

They are probably just build dependencies.
___
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: security/libressl: Add the possibility to build only libtls

2017-08-21 Thread Franco Fichtner 

> On 21. Aug 2017, at 4:55 PM, Mathieu Arnold  wrote:
> 
>> Unless you build your own packages with OpenSSL from ports
>> you can just install LibreSSL and use it in your programs...
>> 
>> # pkg install libressl
>> 
>> OpenSSL lives in the base system, LibreSSL will be an optional
>> install under /usr/local.
> 
> 
> That is not quite true. As soon as you install openssl, openssl-devel,
> or libressl or libressl-devel, the ports framework will use it whenever
> you build something that needs SSL from the ports tree.

Maybe that wasn't clear.  I said "unless you build your own packages"
meaning "use prebuilt binary packages only".


Cheers,
Franco
___
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: security/libressl: Add the possibility to build only libtls

2017-08-21 Thread Mathieu Arnold 
Le 21/08/2017 à 12:03, Franco Fichtner a écrit :
>> On 21. Aug 2017, at 11:59 AM, David Wahlund  wrote:
>>
>> I'd like to use the libtls library of LibreSSL on FreeBSD. Or the python 
>> bindings to libtls specifically. I do NOT however want to replace openssl or 
>> use the libssl library.
>>
>> From what I understand it would be possible in practice as I assume it's 
>> only libssl that overwrites files used by openssl.
>>
>> Would it be possible to create an option in LibreSSL, or preferably make a 
>> separate port, for libtls only? That way future ports can depend on libtls 
>> only. For example a future python-libtls port could depend on that.
>
> Unless you build your own packages with OpenSSL from ports
> you can just install LibreSSL and use it in your programs...
>
> # pkg install libressl
>
> OpenSSL lives in the base system, LibreSSL will be an optional
> install under /usr/local.


That is not quite true. As soon as you install openssl, openssl-devel,
or libressl or libressl-devel, the ports framework will use it whenever
you build something that needs SSL from the ports tree.


If you truly want to have libressl but do not want to use it for
building ports, you will need to install it in a separate PREFIX.


-- 
Mathieu Arnold




signature.asc
Description: OpenPGP digital signature

Re: I went to install 11.1 yesterday

2017-08-21 Thread Mathieu Arnold 
Le 20/08/2017 à 18:23, scratch65...@att.net a écrit :
> [Default] On Sun, 20 Aug 2017 16:09:13 +, Manish Jain
>  wrote:
>
>>
>> On 08/20/17 19:57, scratch65...@att.net wrote:
>>> That's quite interesting!  What led me to believe it is that,
>>> after installing windows, which required creating and formatting
>>> an MBR partition, I tried to install 11.1 on the rest of the
>>> disc.  The first choice I was given was whole disc or partition.
>>> I chose partition, of course.  Whereupon it told me that MBR
>>> isn't supported, and that I could either permit it to consume the
>>> whole disc (for GPT, though it didn't actually say that), or back
>>> up and choose differently.  Functionally, the only choices on
>>> offer were whole disc or quit.  I quit.
>>>
>> Are you using UFS or ZFS for the root filesystem ?
> UFS.  Not much point in choosing ZFS without copies=  as a
> precondition.  Or a spare drive for a mirror


No fsck ever, snapshots, clone, send, receive, compression...


-- 
Mathieu Arnold




signature.asc
Description: OpenPGP digital signature

Re: Add gitlab.com into bsd.sites.mk

2017-08-21 Thread Mathieu Arnold 
Le 20/08/2017 à 23:16, Derek Schrock a écrit :
> On Sat, Aug 19, 2017 at 04:28:01PM EDT, L.Bartoletti wrote:
>> Hello,
>>
>> I would suggest to add gitlab.com into bsd.sites.mk
>>
>> Since, I think I am not competent to propose a patch, I ask for help.
>>
>> I have ports to create where the sources are only available on GitLab. 
>> Like some other ports (audio/midi-matrix-lv2, audio/moony-lv2, etc.) I 
>> can fetch source using a direct link. But, it may be nice to have this 
>> possibility.
>>
>> As I can see, it can be similar (and maybe easier) than github.
>>
>> Archive can be dowload by this URL:
>> https://gitlab.com/${GL_ACCOUNT}/${GL_PROJECT}/repository/${GL_TAGNAME}/archive.${EXTRACT_SUFX}
>>
>> ${EXTRACT_SUFX} can be zip, tar.gz, tar.bz2 and tar
>>
>> Is anyone already working on it or do you want to do it with me?
> Assuming gitlab remains API compatible with github.  I'm wondering if
> gitlab.com, github.com, and gitlab hosted site support can be merged
> into a single set of vars.

You can stop here, because they are not compatible.  They do not differ
greatly, but enough. The gitlab API is akin to the previous github API
where the commit hash was required.
A USE_GITLAB is currently being worked on, though.


-- 
Mathieu Arnold




signature.asc
Description: OpenPGP digital signature

Re: Question on Amavis and ramdisk

2017-08-21 Thread RW via freebsd-ports 
On Mon, 21 Aug 2017 14:47:43 +0200
Willem Jan Withagen wrote:

> Hi,
> 
> In the amavis rc.d file is noted:
> ""
> "WARNING: using ramdisk is reported to be unstable and"
> "thus it is highly recommended to be turned off."
> ""
> 
> And this warning seems there since 2012



Actually it came in with revision 228889 in 2009. The script at
that point didn't allow for tmpfs and only checks for an existing md
device before creating a malloc md device (i.e. in unswapable wired
kernel memory).  IIRC there used to be a warning about this kind of md
device being able to cause crashes.

___
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: Question on Amavis and ramdisk

2017-08-21 Thread Willem Jan Withagen 
On 21-8-2017 15:23, Mark Martinec wrote:
> 2017-08-21 14:47 Willem Jan Withagen wrote:
>> In the amavis rc.d file is noted:
>> ""
>> "WARNING: using ramdisk is reported to be unstable and"
>> "thus it is highly recommended to be turned off."
>> ""
>>
>> And this warning seems there since 2012
>>
>> Is this warning still valid?
>> And if YES, could somebody try and enlighten me as to what is unstable
>> on this config?
>>   - Is the ramdisk itself unstable?
>>   - Or is it the fact that upon a crash de ramdisk is lost and email
>> might be lost?
> 
> I don't really know what was the reason for this warning, but I can
> guess that it's because the port creates a mdmfs ram disk of a fixed
> size for the %%AMAVISDIR%%/tmp file system, and any fixed size small
> disk may eventually run out of space, either during some peak mail
> traffic rush-in, of perhaps when soma stale temporary files happen
> to be left undeleted and accumulating, while this goes unnoticed
> for some time.

Oke, so these are the regular sysadmin troubles of a (too) small a disk.
Nothing a good purge can not fix
Full disk might indeed lead to a sort of DOS situation.

> Using tmpfs instead of mdmfs could avoid some of the above concerns
> if you really want to use a ram disk. In my experience with a
> modern host and file systems, especially with SSD, there is no longer
> any substantial speedup by using a ram disk instead, so I don't
> think it is worth sacrificing memory for a ram disk, which could
> better be used by file system caches etc.

' this system runs in VM on KVM in OpenStack.
And one of the bottlenecks is amavis flushing all mail to a disk. And
that pushes the virtual disk to their limit.
Switching some ramdisk on really does help in the load.
>>   - Or is it the fact that upon a crash de ramdisk is lost and email
>> might be lost?
> 
> No, mail should not be lost. Write failures would be noticed and
> a feeding mailer would receive a temporary failure (smtp status 450),
> so mail should stay in the mailer's queue for a later retry.
> But left unattended for days, this would result in mail non-delivery
> notification to the sender.

Right. As far as I know will postfix only note amavis complete if Amavis
has really reported as such, and only then tkae the file from the
waiting queue. So a crash would not result in wrong deliveries.

So perhaps the wording on that message should be less strong and
prohibitive?

--WjW

___
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: Question on Amavis and ramdisk

2017-08-21 Thread Mark Martinec 

2017-08-21 14:47 Willem Jan Withagen wrote:

In the amavis rc.d file is noted:
""
"WARNING: using ramdisk is reported to be unstable and"
"thus it is highly recommended to be turned off."
""

And this warning seems there since 2012

Is this warning still valid?
And if YES, could somebody try and enlighten me as to what is unstable
on this config?
  - Is the ramdisk itself unstable?
  - Or is it the fact that upon a crash de ramdisk is lost and email
might be lost?


I don't really know what was the reason for this warning, but I can
guess that it's because the port creates a mdmfs ram disk of a fixed
size for the %%AMAVISDIR%%/tmp file system, and any fixed size small
disk may eventually run out of space, either during some peak mail
traffic rush-in, of perhaps when soma stale temporary files happen
to be left undeleted and accumulating, while this goes unnoticed
for some time.

Using tmpfs instead of mdmfs could avoid some of the above concerns
if you really want to use a ram disk. In my experience with a
modern host and file systems, especially with SSD, there is no longer
any substantial speedup by using a ram disk instead, so I don't
think it is worth sacrificing memory for a ram disk, which could
better be used by file system caches etc.


  - Or is it the fact that upon a crash de ramdisk is lost and email
might be lost?


No, mail should not be lost. Write failures would be noticed and
a feeding mailer would receive a temporary failure (smtp status 450),
so mail should stay in the mailer's queue for a later retry.
But left unattended for days, this would result in mail non-delivery
notification to the sender.

  Mark
___
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"

Synth and circular dependencies

2017-08-21 Thread Thomas Mueller 
I am on a FreeBSD 11.1-STABLE amd64 system, building ports with synth, started 
off really strong.

On the other computer (motherboard MSI Z77 MPOWER), synth doesn't work well, 
can't build packages, crashes the system most of the time.

But on this computer, no such system crashes, but I ran into circular 
dependencies which seemed related to print/texlive ports.

Synth screen output was, on several runs


graphics/gd scan aborted because a circular dependency on graphics/gd was 
detected.
... backtrace print/texlive-base
... backtrace print/texlive-texmf
... backtrace print/tex-dvipsk
... backtrace textproc/dblatex
... backtrace textproc/xmlto
... backtrace graphics/giflib
... backtrace graphics/webp
... backtrace graphics/gd

textproc/docproj scan aborted because a circular dependency on graphics/gd was 
detected.
... backtrace print/texlive-base
... backtrace print/texlive-texmf
... backtrace print/tex-dvipsk
... backtrace textproc/dblatex
... backtrace textproc/xmlto
... backtrace graphics/giflib
... backtrace graphics/webp
... backtrace graphics/gd
... backtrace graphics/scr2png
... backtrace textproc/docproj

math/gnumeric scan aborted because a circular dependency on print/texlive-texmf 
was detected.
... backtrace print/tex-dvipsk
... backtrace textproc/dblatex
... backtrace textproc/xmlto
... backtrace graphics/giflib
... backtrace graphics/webp
... backtrace graphics/gd
... backtrace print/texlive-base
... backtrace print/texlive-texmf
... backtrace print/tex-formats
... backtrace print/tex-jadetex
... backtrace textproc/docbook-utils
... backtrace graphics/colord
... backtrace x11-toolkits/gtk30
... backtrace databases/libgda5-ui
... backtrace math/gnumeric

www/seamonkey-i18n scan aborted because a circular dependency on 
print/texlive-texmf was detected.
... backtrace print/tex-dvipsk
... backtrace textproc/dblatex
... backtrace textproc/xmlto
... backtrace graphics/giflib
... backtrace graphics/webp
... backtrace graphics/gd
... backtrace print/texlive-base
... backtrace print/texlive-texmf
... backtrace print/tex-formats
... backtrace print/tex-jadetex
... backtrace textproc/docbook-utils
... backtrace graphics/colord
... backtrace x11-toolkits/gtk30
... backtrace www/seamonkey
... backtrace www/seamonkey-i18n


Only web browser I built successfully was elinks; SeaMonkey, Firefox, Otter 
browser and Netsurf all failed on similar circular dependencies.

I think the fault is in the print/texlive ports rather than synth, but I could 
be wrong.  Abiword also failed on similar circular dependency.

I was successful building llvm40, Xorg, IceWM, jwm, i3 and ratpoison (four 
window managers) but haven't run them yet.

It seems the ports go overboard with an awful lot of dependencies, of which not 
all install with the main port.  So I expect some of these dependencies might 
be false dependencies.

Tom

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

Question on Amavis and ramdisk

2017-08-21 Thread Willem Jan Withagen 
Hi,

In the amavis rc.d file is noted:
""
"WARNING: using ramdisk is reported to be unstable and"
"thus it is highly recommended to be turned off."
""

And this warning seems there since 2012

Is this warning still valid?
And if YES, could somebody try and enlighten me as to what is unstable
on this config?
  - Is the ramdisk itself unstable?
  - Or is it the fact that upon a crash de ramdisk is lost and email
might be lost?

Thanx,
--WjW
___
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: security/libressl: Add the possibility to build only libtls

2017-08-21 Thread Franco Fichtner 
> On 21. Aug 2017, at 11:59 AM, David Wahlund  wrote:
> 
> I'd like to use the libtls library of LibreSSL on FreeBSD. Or the python 
> bindings to libtls specifically. I do NOT however want to replace openssl or 
> use the libssl library.
> 
> From what I understand it would be possible in practice as I assume it's only 
> libssl that overwrites files used by openssl.
> 
> Would it be possible to create an option in LibreSSL, or preferably make a 
> separate port, for libtls only? That way future ports can depend on libtls 
> only. For example a future python-libtls port could depend on that.


Unless you build your own packages with OpenSSL from ports
you can just install LibreSSL and use it in your programs...

# pkg install libressl

OpenSSL lives in the base system, LibreSSL will be an optional
install under /usr/local.


Cheers,
Franco
___
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"

security/libressl: Add the possibility to build only libtls

2017-08-21 Thread David Wahlund 

Hi
I'd like to use the libtls library of LibreSSL on FreeBSD. Or the python 
bindings to libtls specifically. I do NOT however want to replace 
openssl or use the libssl library.


From what I understand it would be possible in practice as I assume 
it's only libssl that overwrites files used by openssl.


Would it be possible to create an option in LibreSSL, or preferably make 
a separate port, for libtls only? That way future ports can depend on 
libtls only. For example a future python-libtls port could depend on that.


-David
___
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"