Re: 4 issues

2017-04-06 Thread Lars Engels
On Wed, Apr 05, 2017 at 10:02:15PM -0600, The Doctor wrote:
> Failures on
> 
> devel/protobuf
> 
> misc/seabios
> 
> devel/openmpi
> 
> devel/kBuild
> 
> .
> 
> Are there others seeing failures?

Yes.


pgp1HWMxYGjtG.pgp
Description: PGP signature


Re: 4 issues

2017-04-06 Thread Walter Schwarzenfeld

For openmpi (I guess it is the libgcc_s.so error).

add to /etc/libmap.conf

libgcc_s.so.1   gcc5/libgcc_s.so.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: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example)

2017-04-06 Thread Alexey Dokuchaev
On Wed, Apr 05, 2017 at 08:46:22PM +0200, Mathieu Arnold wrote:
> Le 05/04/2017 ?? 19:20, Alexey Dokuchaev a ??crit :
> > On Wed, Apr 05, 2017 at 07:12:06PM +0200, Mathieu Arnold wrote:
> >> Le 05/04/2017 ?? 18:15, Alexey Dokuchaev a ??crit :
> >>> ...
> >>> That 1G looks like a big jump from 259M of llvm39-3.9.1_1.txz to me.
> >> 
> >> So, you are comparing the size of the llvm39 package with the size of
> >> the llvm40 after extraction ?
> > 
> > Ha, didn't realize it, I'm so dumb.  What [is] the size of llvm40-*.txz
> > then?  I don't have it cached locally yet...
> 
> On my builds:
> 
> -rw-r--r--  6 nobody  wheel  256105968  4 avr.  17:54 llvm39-3.9.1_4.txz
> -rw-r--r--  6 nobody  wheel  304951340  4 avr.  18:02 llvm40-4.0.0_2.txz

Thanks, now it all makes sense, sorry for confusion.

./danfe
___
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"


Excessive CFLAGS: -pthread -D_THREAD_SAFE

2017-04-06 Thread Jan Beich
A few weeks ago (just before 2017Q2 has branched) many GUI apps started
to have very long compile lines. Most of it is composed of duplicate
occurence of the same flags with the first bad being r437182 e.g.,

$ pkg-config --cflags gtk+-2.0
-I/usr/local/include/gtk-2.0 -I/usr/local/include/pango-1.0 
-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include 
-I/usr/local/include -I/usr/local/include/cairo 
-I/usr/local/include/pixman-1-I/usr/local/include/freetype2 
-I/usr/local/include/libpng16 -I/usr/local/include/harfbuzz 
-I/usr/local/include/libdrm -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE 
-pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE 
-pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE 
-pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE 
-pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE 
-pthread -D_THREAD_SAFE -pthread -I/usr/local/include/gdk-pixbuf-2.0 
-I/usr/local/include/atk-1.0 -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE 
-pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE 
-pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE 
-pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE 
-pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE 
-pthread -D_THREAD_SAFE -pthread -pthread

Is this intentional? A bug in pkgconf or .pc file?


signature.asc
Description: PGP signature


Re: Excessive CFLAGS: -pthread -D_THREAD_SAFE

2017-04-06 Thread Matthew Rezny
On Thursday 06 April 2017 16:28:29 Jan Beich wrote:
> A few weeks ago (just before 2017Q2 has branched) many GUI apps started
> to have very long compile lines. Most of it is composed of duplicate
> occurence of the same flags with the first bad being r437182 e.g.,
> 
> $ pkg-config --cflags gtk+-2.0
> -I/usr/local/include/gtk-2.0 -I/usr/local/include/pango-1.0
> -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include
> -I/usr/local/include -I/usr/local/include/cairo
> -I/usr/local/include/pixman-1-I/usr/local/include/freetype2
> -I/usr/local/include/libpng16 -I/usr/local/include/harfbuzz
> -I/usr/local/include/libdrm -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE
> -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE
> -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE
> -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE
> -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE
> -pthread -D_THREAD_SAFE -pthread -I/usr/local/include/gdk-pixbuf-2.0
> -I/usr/local/include/atk-1.0 -pthread -D_THREAD_SAFE -pthread
> -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread
> -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread
> -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread
> -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread
> -D_THREAD_SAFE -pthread -D_THREAD_SAFE -pthread -pthread
> 
> Is this intentional? A bug in pkgconf or .pc file?

The commit to which you refer is the update of libpthread-stubs, which is no 
longer a library but simply a .pc file that adds -pthread to Cflags and Libs. 
That .pc is used for building a dozen or so ports, one of which is libxcb. 
libxcb happens to need a RUN_DEPENDS as well because it references pthread-
stubs in xcb.pc. The next step is libX11 which has a RUN_DEPENDS on libxcb via 
USE_XORG=xcb, and whose x11.pc references xcb and appends -D_THREAD_SAFE to 
Cflags. Thus, the culprit of the repeated -D_THREAD_SAFE -pthread must be 
multiple inclusions of x11.pc. X11 applications have a USE_XORG=x11 which is 
in effect both BUILD_ and RUN_DEPENDS on x11.pc. USE_XORG=x11 will appear 
multiple times up the chain to the application; in GTK+, in libs used by or 
with GTK that link to libX11, in the application itself, etc. If the x11.pc is 
used at every place that there is the dependency then that explains what we 
see now. The question now is where in the chain to fix it.


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


nano 2.8.0 reports bad regex when including nanorc files

2017-04-06 Thread Guy Yur
Hi,

nano 2.8.0 complains on bad regex for "[[:<:]]" and [[:>:]]
when I include nanorc files in /usr/local/etc/nanorc:
include "/usr/local/share/nano/awk.nanorc"

Error in /usr/local/share/nano/awk.nanorc on line 22: Bad regex
"[[:<:]](system|fflush)[[:>:]]": Invalid character class name

In 2.7.5 the libc regex was used but in 2.8.0 the bundled regex is used
and it doesn't support [[:<:]] and [[:>:]].

I saw it was already fixed upstream:
https://savannah.gnu.org/bugs/?50705
https://savannah.gnu.org/bugs/?50714
http://git.savannah.gnu.org/cgit/nano.git/commit/configure.ac?id=8f2b5bbf3d1b23007aedc9f07f224da91f0ec479
http://git.savannah.gnu.org/cgit/nano.git/commit/configure.ac?id=cc91ee603c24429375ace5d4b55d85c396668c2e

The fix defines GNU_WORDBOUNDS when the bundled regex lib is used
so nano won't convert \< to [[:<:] and \> to [[:>:]] in fixbounds().

I got working nano by removing the \< to [[:<:]] ... reinplace from the
Makefile and applying the commits to configure.ac and regenerating it.

Patch for the port:
https://github.com/guyyur/freebsd-ports_patches/blob/master/editors_nano__bad_regex.patch

Thanks,
Guy
___
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: net/samba46

2017-04-06 Thread Doug Sampson
> When I try to join a domain after building samba46, I get this error
> message:
> 
> root@aries:/usr/local/etc # net ads join -U dspadmin%
> Failed to join domain: failed to create kerberos keytab
> root@aries:/usr/local/etc #
> 
> 
> I cannot find anything in any of the samba4 logs.
> 
> root@aries:/usr/ports/net/samba46 # make showconfig
> ===> The following configuration options are available for samba46-
> 4.6.1_2:
>  ADS=on: Active Directory client support(implies LDAP)
>  AD_DC=on: Active Directory Domain Controller support
>  CUPS=off: CUPS printing system support
>  DEBUG=on: Build with debugging support
>  DEVELOPER=off: With development support(implies NTVFS)
>  DOCS=on: Build and/or install documentation
>  EXP_MODULES=off: Experimental modules(WANT_EXP_MODULES)
>  FAM=on: File Alteration Monitor support
>  LDAP=on: LDAP client support
>  MANPAGES=off: Build manpages from DOCBOOK templates
>  NTVFS=off: Build *DEPRECATED* NTVFS file server
>  QUOTAS=on: Disk quota support
>  SYSLOG=on: Syslog logging support
>  UTMP=on: UTMP accounting support
> > Options available for the radio DNS: you can only select none or
> one of them
>  NSUPDATE=off: Use samba NSUPDATE utility for AD DC
>  BIND99=off: Use Bind 9.9 as AD DC DNS server frontend
>  BIND910=off: Use Bind 9.10 as AD DC DNS server frontend
>  BIND911=off: Use Bind 9.11 as AD DC DNS server frontend
> > Options available for the radio ZEROCONF: you can only select none
> or one of them
>  AVAHI=off: Zeroconf support via Avahi
>  MDNSRESPONDER=off: Zeroconf support via mDNSResponder
> ===> Use 'make config' to modify these settings
> 
> Testparm reveals the following:
> 
> [global]
> realm = DOMAIN.TLD
> server string =
> workgroup = DOMAIN
> domain master = No
> local master = No
> preferred master = No
> client ldap sasl wrapping = seal
> log file = /var/log/samba4/log.%m
> disable spoolss = Yes
> load printers = No
> printcap name = /dev/null
> disable netbios = Yes
> max xmit = 65535
> min receivefile size = 16384
> name resolve order = lmhosts hosts bcast
> smb ports = 445
> kerberos method = system keytab
> security = ADS
> server signing = if_required
> deadtime = 15
> max open files = 65535
> socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE
> template shell = /bin/bash
> winbind cache time = 10
> winbind enum groups = Yes
> winbind enum users = Yes
> winbind nss info = rfc2307
> winbind offline logon = Yes
> winbind refresh tickets = Yes
> winbind separator = -
> nfs4:chown = yes
> nfs4:acedup = merge
> nfs4:mode = special
> idmap config *:range = 1000-5
> idmap config dsp:backend = rid
> idmap config dsp:default = yes
> idmap config dsp:range = 50001-6
> idmap config * : backend = tdb
> map readonly = no
> store dos attributes = Yes
> strict locking = No
> directory name cache size = 0
> map acl inherit = Yes
> admin users = DOMAIN-doug
> hosts allow = 192.168.xxx. 192.168.xxx. 127. 10.8.
> inherit owner = Yes
> inherit permissions = Yes
> read only = No
> aio read size = 16384
> aio write size = 16384
> max connections = 65535
> use sendfile = Yes
> vfs objects = zfsacl acl_xattr audit netatalk
> 
> Using the same make configure options and the same smb4.conf on
> net/samba45 allows me to join a domain successfully.
> 
Is anyone running www/samba46 on a FreeBSD 11.0-RELEASE system utilizing 
winbindd? If you're not utilizing winbindd, what are you using for your 
authentication? LDAP?

~Doug
___
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: net/samba46

2017-04-06 Thread Matthias Fechner
Am 05.04.2017 um 00:02 schrieb Doug Sampson:
> When I try to join a domain after building samba46, I get this error message:
>
> root@aries:/usr/local/etc # net ads join -U dspadmin%
> Failed to join domain: failed to create kerberos keytab
> root@aries:/usr/local/etc #
>

have you seen the following entry:
20170401:
  AFFECTS: net/samba44, net/samba45, net/samba46 and devel/p5-Parse-Pidl*
  AUTHOR: ti...@freebsd.org

  It turned out that arbitary versions of p5-Parse-Pidl may lead to the
  hard to explain crashes of the Samba server and utilities(in particular
  we suspect it was responsible for the troubles with the DC provisioning).

  So, from now on net/samba* ports use bundled version of Pidl. You need to
  remove external package from the system:

  pkg delete -f p5-Parse-Pidl p5-Parse-Pidl44


For me samba43 is working fine. Every newer version fails and all
windows PCs refuses to connect to samba.


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
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: net/samba46

2017-04-06 Thread Kurt Jaeger
Hi!

> > When I try to join a domain after building samba46, I get this error
> > message:
> > 
> > root@aries:/usr/local/etc # net ads join -U dspadmin%
> > Failed to join domain: failed to create kerberos keytab
> > root@aries:/usr/local/etc #
[...]

> Is anyone running www/samba46 on a FreeBSD 11.0-RELEASE system
> utilizing winbindd? If you're not utilizing winbindd, what are you
> using for your authentication? LDAP?

I have a 10.3 box with winbind and samba44, and it works.

Given your problem description, I'm hesitant to upgrade that box
to 4.6.

-- 
p...@opsec.eu+49 171 3101372 3 years to go !
___
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"


cl ktter flrr dns/unbound

2017-04-06 Thread Walter Schwarzenfeld

Need a commit fpr dns/unbound

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217737

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: cl ktter flrr dns/unbound

2017-04-06 Thread Walter Schwarzenfeld

sorry, for typos
should be committer for dns/unbound
___
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"


misc/seabios

2017-04-06 Thread The Doctor
Got it to work.

in work/seabios-X/Makefile

set CROSS_PREFIX=/usr/local/bin

-- 
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
http://www.fullyfollow.me/rootnl2k  Look at Psalms 14 and 53 on Atheism
God is dead! Yahweh lives! Jesus his only begotten Son is the Risen Saviour!!
___
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: net/samba46

2017-04-06 Thread Matthias Apitz
El día viernes, abril 07, 2017 a las 12:26:36a. m. +0200, Kurt Jaeger escribió:

> > Is anyone running www/samba46 on a FreeBSD 11.0-RELEASE system
> > utilizing winbindd? If you're not utilizing winbindd, what are you
> > using for your authentication? LDAP?
> 
> I have a 10.3 box with winbind and samba44, and it works.
> 
> Given your problem description, I'm hesitant to upgrade that box
> to 4.6.

I could not even compile none of the 4.3, 4.4 and 4.6 versions on
12-CURRENT :-(

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
Aus "Nie wieder Krieg!" wurde "Nie wieder Krieg ohne Deutschlands Truppen"
The "No wars anymore!" changed now to "No wars anymore without German battle 
groups!"
El "¡Nunca jamás guerra!" ha cambiado a "¡Nunca jamás guerra sin tropas 
alemanas!" 
___
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: net/samba46

2017-04-06 Thread Dewayne Geraghty
I use gcc5 to build most of my ports. And I have samba running as a
fileshare only, not a domain. Soon to change as I will be moving from
samba36 pdc.

On 11.0stable (most recent build of base using clang4) works well.  I'll
see if we can bring forward testing of AD on Samba46 & FreeBSD 11 to this
weekend?




-- 
*Disclaimer:*



*As implied by email protocols, the information in this message is not
confidential. Any intermediary or recipient may inspect, modify (add),
copy, forward, reply to, delete, or filter email for any purpose unless
said parties are otherwise obligated.  Nothing in this message may be
legally binding without cryptographic evidence of its integrity and/or
confidentiality.*
___
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: Excessive CFLAGS: -pthread -D_THREAD_SAFE

2017-04-06 Thread Rozhuk Ivan
On Thu, 06 Apr 2017 16:28:29 +0200
Jan Beich  wrote:

> A few weeks ago (just before 2017Q2 has branched) many GUI apps
> started to have very long compile lines. Most of it is composed of
> duplicate occurence of the same flags with the first bad being
> r437182 e.g.,


Try this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218453

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