Re: Segmentation fault running ntpd

2015-11-01 Thread Andre Albsmeier 
On Fri, 30-Oct-2015 at 19:47:59 +0100, Mark Martinec wrote:
> Not sure if it's the same issue, but it sure looks like it is.
> 
> I have upgraded a couple of hosts (amd64) from 10.2-RELEASE-p5
> to 10.2-RELEASE-p6, i.e. the freebsd-upgrade essentially just
> replaced the /usr/sbin/ntpd with a new one; then I restarted
> the ntpd.
> 
> On all host but one this was successful: the new ntpd starts
> fine and works normally. But on one of these machines the
> ntpd process immediately crashes with SIGSEGV. That machine
> has an Intel Xeon cpu. It is not apparent to me in what way
> this machine differs from others,

I'll add my observations here:

I am using an ntp.conf with a single server entry:

server ntp.some.domain.org

ntp.some.domain.org is a CNAME pointing to gate.some.domain.org
and the latter contains an A record pointing to 192.168.128.1.

After updating 9.3-STABLE to the latest version (one which includes ntp
4.2.8p4), ntpd crashes:

Nov 1 09:38:38 voyager kernel: pid 4443 (ntpd), uid 0: exited on signal 11

This happens in line 871 of ntpd.c where mlockall() is called:

&& 0 != mlockall(MCL_CURRENT|MCL_FUTURE))

It does NOT crash with MCL_FUTURE only.
It does crash with MCL_CURRENT only.

When adding

rlimit memlock -1

to ntpd.conf it does NOT crash (as mlockall() won't be called anymore).

When specifying the IP address (192.168.128.1) as the server it
does NOT crash.

When specifying gate.some.domain.org as the server it also does
NOT crash. tcpdump shows in this case:

09:49:59.542310 IP 192.168.128.2.21102 > 192.168.128.1.53: 7639+ A? 
gate.some.domain.org. (41)
09:49:59.542578 IP 192.168.128.1.53 > 192.168.128.2.21102: 7639* 1/1/0 A 
192.168.128.1 (71)
09:49:59.542612 IP 192.168.128.2.52455 > 192.168.128.1.53: 42047+ ? 
gate.some.domain.org. (41)
09:49:59.542792 IP 192.168.128.1.53 > 192.168.128.2.52455: 42047* 0/1/0 (88)

When reverting the server entry back to ntp.some.domain.org
it crashes and tcpdump shows:

09:36:05.172552 IP 192.168.128.2.17836 > 192.168.128.1.53: 49768+ A? 
ntp.some.domain.org. (40)
09:36:05.173320 IP 192.168.128.1.53 > 192.168.128.2.17836: 49768* 2/1/0 CNAME 
gate.some.domain.org., A 192.168.128.1 (89)
09:36:05.173361 IP 192.168.128.2.22611 > 192.168.128.1.53: 63808+ ? 
ntp.some.domain.org. (40)
09:36:05.173595 IP 192.168.128.1.53 > 192.168.128.2.22611: 63808* 1/1/0 CNAME 
gate.some.domain.org. (106)

The probability for crashing increases with the speed and the
number of cores of the machine: On my old single-core Pentiums
it never crashes, on my quad-cores i7-3770K it always crashes.

The (asynchronous) resolving of the names start in line 3876 of
ntp_config.c:

getaddrinfo_sometime(curr_peer->addr->address,

If we put the mlockall() call directly before this line, the
crash is gone.

Maybe you want to play around with rlimit, CNAMES, IPs and
so on...

-Andre

Anyone else seeing this?
> 2015-10-30 12:34, je David Wolfskill napisal
> > On Fri, Oct 30, 2015 at 09:42:07AM +0100, Dag-Erling Smørgrav wrote:
> >> David Wolfskill  writes:
> >> > ...
> >> > bound to 172.17.1.245 -- renewal in 43200 seconds.
> >> > pid 544 (ntpd), uid 0: exited on signal 11 (core dumped)
> >> > Starting Network: lo0 em0 iwn0 lagg0.
> >> > ...
> >> 
> >> Did you find a solution?  I'm wondering if the ntpd problems people 
> >> are
> >> reporting on freebsd-security@ are related.  I vaguely recall hearing
> >> that this had been traced to a pthread bug, but can't find anything
> >> about it in commit logs or mailing list archives.
> >> 
> > 
> > I don't recall finding "a solution" per se; that said, I also don't
> > recall seeing an occurrence of the above for enough time that I'm not
> > sure when I sent that message. :-}
> > 
> > As a reality check:
> > 
> > g1-252(11.0-C)[1] ls -lT /*.core
> > -rw-r--r--  1 root  wheel  13783040 Aug 18 04:19:03 2015 /ntpd.core
> > g1-252(11.0-C)[2]
> > 
> > So -- among other points -- my last sighting of whatever was causing
> > that was the day I built:
> > 
> > FreeBSD 11.0-CURRENT #157  r286880M/286880:1100079: Tue Aug 18
> > 04:45:25 PDT 2015
> > r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY  amd64
> > 
> > Note that the machines where I run head get updated daily (unless
> > there's enough of a problem with head that I can't build it or can't
> > boot it (and I'm unable to circumvent the issue within a reasonable
> > time)) -- and while I do attempt to run ntpd on the machines, the above
> > failure is more "annoying" than "crippling" in my particular case.
> > 
> > And I'm presently running:
> > 
> > FreeBSD 11.0-CURRENT #227  r290138M/290138:1100084: Thu Oct 29
> > 05:12:58 PDT 2015
> > r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY  amd64
> > 
> > and building head @r290190 as I type.
> > 
> > And FWIW, I *suspect* that one of the issues involved (in my case)
> > was a ... lack of determinism ... in events involving getting the
> > (wireless)

Panic with PF on current.

2015-11-01 Thread Daniel Dettlaff 
Hello.

I have my first kernel panic, probably related to pf/pflog in CURRENT:

I built kernel using this config: 
https://github.com/VerKnowSys/ServeD-OS/blob/master/kernel/VERKNOWSYS-11.0
My make.conf: https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/make.conf
My src.conf: https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/src.conf
My loader.conf: 
https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/loader.conf.served
My sysctl.conf: 
https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/sysctl.conf.served

I’m using Vmware Fusion 7.0 pro as host.

I catched that panic on main system console (verbose boot turned on):

http://s.verknowsys.com/18bfec6f00e939e0b93952a4117fda34.png

As you see it looks related to pfsync. Hence I tried to disable pf for test, 
but just after `service pf stop` more “detailed panic" happened:

http://s.verknowsys.com/a1500912956930aa9eda16383347657c.png
and with some backtrace:
http://s.verknowsys.com/9f413eec8be03faf898208ef9d2fe555.png

My build (kernel + world + HBSD patches) is here: 
http://served.verknowsys.com/ServeD-OS-Base-11.0-v0.11.7-amd64.tar.xz if you 
want to try to reproduce it maybe.


Panic will happen only if “pf" kernel module is loaded. Since I disabled “pf" 
and “pflog", system works as expected, no panic at all.


This issue was also reported to #HardenedBSD since I’m not sure it’s related to 
hardening patches or not. (It seems not related at the moment).

Thank you :) Hope this will help someone, let me know if I can help somehow 
further.

--
kind regards

Daniel (dmilith) Dettlaff



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Compilation failure with WITH_DTRACE_TESTS on mips/mips and powerpc/powerpc; it's trying to compile a host object on mips/powerpc because MAKEOBJDIRPREFIX is incorrect

2015-11-01 Thread Simon J. Gerraty 
NGie Cooper  wrote:

> And here’s the real issue — .PATH is completely broken when
> TARGET/TARGET_ARCH are specified as explicit values:

It would help if you could indicate what you think the right value
should be.
 
> $ env MAKEOBJDIRPREFIX=/scratch/tmp/ngie/obj/ make buildenv TARGET=powerpc 
> TARGET_ARCH=powerpc
> Entering world for powerpc:powerpc
> $ cd cddl/usr.sbin/dtrace/tests/common/json
> $ make -V.OBJDIR
> /scratch/tmp/ngie/obj//powerpc.powerpc/scratch/tmp/ngie/svn/cddl/usr.sbin/dtrace/tests/common/json
> $ make -VMAKEOBJDIRPREFIX
> /scratch/tmp/ngie/obj//powerpc.powerpc
> $ make depend
> (cd /scratch/tmp/ngie/svn/cddl/usr.sbin/dtrace/tests/common/json &&  
> DEPENDFILE=.depend.tst.usdt.exe  NO_SUBDIR=1 make -f 
> /scratch/tmp/ngie/svn/cddl/usr.sbin/dtrace/tests/common/json/Makefile 
> _RECURSING_PROGS=  PROG=tst.usdt.exe  depend)

If you are doing this on current (ie MAKE_VERSION==20151020), adding -w
would be useful, since will report entering src and obj dirs.

> $ make all
> (cd /scratch/tmp/ngie/svn/cddl/usr.sbin/dtrace/tests/common/json &&  
> DEPENDFILE=.depend.tst.usdt.exe  NO_SUBDIR=1 make -f 
> /scratch/tmp/ngie/svn/cddl/usr.sbin/dtrace/tests/common/json/Makefile 
> _RECURSING_PROGS=  PROG=tst.usdt.exe )
> dtrace -C -x nolibs -G -o usdt.o -s 
> /scratch/tmp/ngie/svn/cddl/contrib/opensolaris/cmd/dtrace/test/tst/common/json/usdt.d
>  tst.usdt.o
> dtrace: failed to link script 
> /scratch/tmp/ngie/svn/cddl/contrib/opensolaris/cmd/dtrace/test/tst/common/json/usdt.d:
>  incorrect ELF machine type for object file: tst.usdt.o

> Stop.
> make[2]: stopped in 
> /scratch/tmp/ngie/svn/cddl/usr.sbin/dtrace/tests/common/json
> $ make -V.PATH

what dir do you execute that in?
I'm *guessing* cddl/usr.sbin/dtrace/tests/common/json.

It's actually quite useful when reporting/describing problems to do
everything from src eg.

make -w -C cddl/usr.sbin/dtrace/tests/common/json

leaves very little room for confusion.


> . /scratch/tmp/ngie/svn/cddl/usr.sbin/dtrace/tests/common/json 
> /scratch/tmp/ngie/svn/cddl/contrib/opensolaris/cmd/dtrace/test/tst/common/json

What else do you expect in .PATH?
I didn't see anything in the Makefile or ../../Makefile.inc1 to add
anything else

You may also find it useful to set MAKE_PRINT_VAR_ON_ERROR
to a list of variables - that will be reported when make dies.
eg.

MAKE_PRINT_VAR_ON_ERROR=".CURDIR .OBJDIR MACHINE MACHINE_ARCH .PATH"

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

buildworld broken

2015-11-01 Thread Steve Kargl 
===> libexec/dma/dmagent (all)
cc  -I/usr/src/libexec/dma/dmagent/../../../contrib/dma  -DHAVE_REALLOCF 
-DHAVE_STRLCPY -DHAVE_GETPROGNAME  -DCONF_PATH='"/etc/dma"'  
-DLIBEXEC_PATH='"/usr/libexec"' -DDMA_VERSION='"v0.10"'  
-DDMA_ROOT_USER='"mailnull"'  -DDMA_GROUP='"mail"' -std=gnu99 
-fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W 
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith 
-Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter 
-Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls 
-Wold-style-definition -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args 
-Werror -Wmissing-variable-declarations -Wthread-safety -Wno-empty-body 
-Wno-string-plus-int -Wno-unused-const-variable -Qunused-arguments  -o dma 
aliases_parse.o aliases_scan.o base64.o conf.o crypto.o dma.o dns.o local.o 
mail.o net.o spool.o util.o  -lssl  -lcrypto
/usr/obj/usr/src/tmp/usr/lib/libcrypto.so: undefined reference to 
`PKCS7_digest_from_attributes'
/usr/obj/usr/src/tmp/usr/lib/libcrypto.so: undefined reference to 
`PKCS7_add_signed_attribute'
/usr/obj/usr/src/tmp/usr/lib/libcrypto.so: undefined reference to 
`PKCS7_dataFinal'
/usr/obj/usr/src/tmp/usr/lib/libcrypto.so: undefined reference to 
`PKCS7_get_signed_attribute'
/usr/obj/usr/src/tmp/usr/lib/libcrypto.so: undefined reference to 
`PKCS7_SIGNER_INFO_sign'
/usr/obj/usr/src/tmp/usr/lib/libcrypto.so: undefined reference to 
`PKCS7_dataInit'
/usr/obj/usr/src/tmp/usr/lib/libcrypto.so: undefined reference to 
`PKCS7_dataDecode'
/usr/obj/usr/src/tmp/usr/lib/libcrypto.so: undefined reference to 
`PKCS7_signatureVerify'


-- 
Steve
___
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: [HEADSUP] OpenSSL updated to 1.0.2d

2015-11-01 Thread Boris Samorodov 
30.10.2015 23:57, Jung-uk Kim пишет:

> OpenSSL on head has been updated to 1.0.2d.  Please make sure to
> recompile all binaries depending on libcrypto.so.7 or libssl.so.7.

Great, thanks!

How do those who use FreeBSD official packages supposed to upgrade
packages?

-- 
WBR, bsam
___
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: Panic with PF on current.

2015-11-01 Thread NGie Cooper 

> On Nov 1, 2015, at 10:54, Daniel Dettlaff  wrote:
> 
> Hello.
> 
> I have my first kernel panic, probably related to pf/pflog in CURRENT:
> 
> I built kernel using this config: 
> https://github.com/VerKnowSys/ServeD-OS/blob/master/kernel/VERKNOWSYS-11.0
> My make.conf: 
> https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/make.conf
> My src.conf: https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/src.conf
> My loader.conf: 
> https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/loader.conf.served
> My sysctl.conf: 
> https://github.com/VerKnowSys/ServeD-OS/blob/master/etc/sysctl.conf.served
> 
> I’m using Vmware Fusion 7.0 pro as host.
> 
> I catched that panic on main system console (verbose boot turned on):
> 
> http://s.verknowsys.com/18bfec6f00e939e0b93952a4117fda34.png
> 
> As you see it looks related to pfsync. Hence I tried to disable pf for test, 
> but just after `service pf stop` more “detailed panic" happened:
> 
> http://s.verknowsys.com/a1500912956930aa9eda16383347657c.png
> and with some backtrace:
> http://s.verknowsys.com/9f413eec8be03faf898208ef9d2fe555.png
> 
> My build (kernel + world + HBSD patches) is here: 
> http://served.verknowsys.com/ServeD-OS-Base-11.0-v0.11.7-amd64.tar.xz if you 
> want to try to reproduce it maybe.
> 
> 
> Panic will happen only if “pf" kernel module is loaded. Since I disabled “pf" 
> and “pflog", system works as expected, no panic at all.
> 
> 
> This issue was also reported to #HardenedBSD since I’m not sure it’s related 
> to hardening patches or not. (It seems not related at the moment).
> 
> Thank you :) Hope this will help someone, let me know if I can help somehow 
> further.

CCing kp.

What version of FreeBSD (revision, git hash) is this based on?

Thanks,
-NGie
___
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: [HEADSUP] OpenSSL updated to 1.0.2d

2015-11-01 Thread Tomoaki AOKI 
Thanks! Yours is very much faster than what I was trying. :-)

Attached is a modified one to generate updating script.
Currently it uses ports-mgmt/portupgrade(-devel), but modifying to use
other options or any other tool (such as ports-mgmt/portmaster).

Caution: No error checking for generated script.
 (Command line length, and so on are NOT checked.)


On Sat, 31 Oct 2015 09:23:06 -0500
Eric van Gyzen  wrote:

> On 10/31/15 5:25 AM, O. Hartmann wrote:
> > Am Fri, 30 Oct 2015 16:57:45 -0400
> > Jung-uk Kim  schrieb:
> >
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA256
> >>
> >> OpenSSL on head has been updated to 1.0.2d.  Please make sure to
> >> recompile all binaries depending on libcrypto.so.7 or libssl.so.7.
> >
> > That is good news.
> >
> > Could you provide, please, some hints how one could check all installed 
> > ports for the
> > usage of those specific libraries? Or could you provide a hint towards an 
> > existing port
> > already providing those tools? It would be great for those "from the set of 
> > ordinary
> > people" using FreeBSD.
> >
> > I ask for that because I recall that there were a couple of ports which 
> > explicitely asks
> > for a selection of what SSL lib should be used and in my case, I use the 
> > base system's
> > one.
> 
> I expect there's a port, but I'm not aware of one.
> 
> This should work:
> 
> find /usr/local/*bin /usr/local/lib* -type f | \
> while read F; do \
>   objdump -x $F 2>&1 | grep -Eq 'NEEDED  *lib(crypto|ssl).so.7' && \
>   echo $F; \
> done
> 
> This is in /bin/sh (or bash).  You could change "echo" to "pkg which"
> to show the package names.
> 
> Cheers,
> 
> Eric
> ___
> 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"
> 


-- 
Tomoaki AOKIjunch...@dec.sakura.ne.jp
___
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: [CFT] Unicode collation string and reworked locale definitions

2015-11-01 Thread Baptiste Daroussin 
On Wed, Oct 14, 2015 at 12:23:06AM +0200, Baptiste Daroussin wrote:
> Hi all,
> 
> I have been working for a while on bringing in Unicode string collation
> support by merging code from Illumos (by Garrett D'Amore who kindly made sure
> his work was made under BSD license) and Dragonfly (by John Marino), and some
> ancient work done on FreeBSD by edwin@ but never merged.
> 
> The result is available in the projects/collation branch.
> 
> As a result of this work, is:
> - Locales are now generated with the new localedef(1) tool from CLDR POSIX 
> files
> - The generated files are now identified as "BSD 1.0" format
> - Only "BSD 1.0" locales files are now read, all other version will be set to
>   "C"
> - The localedef(1) tool has been imported from Illumos and modidied to use
>   tree(3) instead of the CDDL avl(3)
> - A set of tool created by edwin@ and extended by marino@ for dragonfly has 
> been
>   added to be able to generate locales
> - Given our regex(3) does not support multibyte yet (actually it does not
>   support some single-byte codeset) it has been forced to always use locale C
> - Remove colldef(1) and mklocale(1)
> - Finish implementing the numeric BSD extension for ctypes
> - Add a bunch of new locales: some arabian locales, hebrew locales, some
>   regional locales, etc.
> - Make a bunch of ISO-8859-1 locales simple aliase on ISO-8859-15 where it 
> makes
>   sense
> - Add short version of locales
> - Add @euro aliases on the locales where that make sense
> 
> Please test the branch and report issues.
> 
> Note that yes that means the COLLATION_FIX patch on glib2 will not be 
> necessary
> anymore
> and yes the icu patch on postgresql will not be necessary anymore
> 
> Best regards,
> Bapt

All issues reported has been fixed, except if more issues are reported, this
will be merged into head next saturday: November 7th

Bapt


signature.asc
Description: PGP signature

Re: [HEADSUP] OpenSSL updated to 1.0.2d

2015-11-01 Thread Jason Unovitch 
On Nov 1, 2015 10:06 AM, "Boris Samorodov"  wrote:
>
> 30.10.2015 23:57, Jung-uk Kim пишет:
>
> > OpenSSL on head has been updated to 1.0.2d.  Please make sure to
> > recompile all binaries depending on libcrypto.so.7 or libssl.so.7.
>
> Great, thanks!
>
> How do those who use FreeBSD official packages supposed to upgrade
> packages?
>
> --
> WBR, bsam
> ___

This is on head so it should be the same process as any other source based
upgrade per the handbook.

https:// 
www.freebsd.org 
/doc/handbook/ 
makeworld.html 

The 'make delete-old-libs' step would have to wait until after the official
11-CURRENT package builders have been updated to a revision after this
change and a 'pkg upgrade' installs everything from that build.
___
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"

FreeBSD_HEAD-tests - Build #1634 - Unstable

2015-11-01 Thread jenkins-admin 
FreeBSD_HEAD-tests - Build #1634 - Unstable:

Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1634/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1634/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1634/console

Change summaries:

No changes


The failed test cases:

4 tests failed.
FAILED:  lib.libc.stdio.fmemopen2_test.test_data_length

Error Message:
/builds/FreeBSD_HEAD/lib/libc/tests/stdio/fmemopen2_test.c:203: pos == 0 not met

FAILED:  lib.libc.stdio.fmemopen_test.test09

Error Message:
3956 checks failed; see output for more details

FAILED:  lib.libc.stdio.fmemopen_test.test11

Error Message:
6020 checks failed; see output for more details

FAILED:  lib.libc.stdio.fmemopen_test.test14

Error Message:
1806 checks failed; see output for more details

___
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: [CFT] Unicode collation string and reworked locale definitions

2015-11-01 Thread Andreas Tobler 

On 01.11.15 22:30, Baptiste Daroussin wrote:

On Wed, Oct 14, 2015 at 12:23:06AM +0200, Baptiste Daroussin wrote:

Hi all,

I have been working for a while on bringing in Unicode string collation
support by merging code from Illumos (by Garrett D'Amore who kindly made sure
his work was made under BSD license) and Dragonfly (by John Marino), and some
ancient work done on FreeBSD by edwin@ but never merged.

The result is available in the projects/collation branch.

As a result of this work, is:
- Locales are now generated with the new localedef(1) tool from CLDR POSIX files
- The generated files are now identified as "BSD 1.0" format
- Only "BSD 1.0" locales files are now read, all other version will be set to
   "C"
- The localedef(1) tool has been imported from Illumos and modidied to use
   tree(3) instead of the CDDL avl(3)
- A set of tool created by edwin@ and extended by marino@ for dragonfly has been
   added to be able to generate locales
- Given our regex(3) does not support multibyte yet (actually it does not
   support some single-byte codeset) it has been forced to always use locale C
- Remove colldef(1) and mklocale(1)
- Finish implementing the numeric BSD extension for ctypes
- Add a bunch of new locales: some arabian locales, hebrew locales, some
   regional locales, etc.
- Make a bunch of ISO-8859-1 locales simple aliase on ISO-8859-15 where it makes
   sense
- Add short version of locales
- Add @euro aliases on the locales where that make sense

Please test the branch and report issues.

Note that yes that means the COLLATION_FIX patch on glib2 will not be necessary
anymore
and yes the icu patch on postgresql will not be necessary anymore

Best regards,
Bapt


All issues reported has been fixed, except if more issues are reported, this
will be merged into head next saturday: November 7th



Cool! Waiting for it!

Thanks,
Andreas

___
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: buildworld broken

2015-11-01 Thread NGie Cooper 

> On Nov 1, 2015, at 08:47, Steve Kargl  
> wrote:
> 
> ===> libexec/dma/dmagent (all)
> cc  -I/usr/src/libexec/dma/dmagent/../../../contrib/dma  -DHAVE_REALLOCF 
> -DHAVE_STRLCPY -DHAVE_GETPROGNAME  -DCONF_PATH='"/etc/dma"'  
> -DLIBEXEC_PATH='"/usr/libexec"' -DDMA_VERSION='"v0.10"'  
> -DDMA_ROOT_USER='"mailnull"'  -DDMA_GROUP='"mail"' -std=gnu99 
> -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W 
> -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes 
> -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow 
> -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs 
> -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wformat=2 
> -Wno-format-extra-args -Werror -Wmissing-variable-declarations 
> -Wthread-safety -Wno-empty-body -Wno-string-plus-int 
> -Wno-unused-const-variable -Qunused-arguments  -o dma aliases_parse.o 
> aliases_scan.o base64.o conf.o crypto.o dma.o dns.o local.o mail.o net.o 
> spool.o util.o  -lssl  -lcrypto
> /usr/obj/usr/src/tmp/usr/lib/libcrypto.so: undefined reference to 
> `PKCS7_digest_from_attributes'
> /usr/obj/usr/src/tmp/usr/lib/libcrypto.so: undefined reference to 
> `PKCS7_add_signed_attribute'
> /usr/obj/usr/src/tmp/usr/lib/libcrypto.so: undefined reference to 
> `PKCS7_dataFinal'
> /usr/obj/usr/src/tmp/usr/lib/libcrypto.so: undefined reference to 
> `PKCS7_get_signed_attribute'
> /usr/obj/usr/src/tmp/usr/lib/libcrypto.so: undefined reference to 
> `PKCS7_SIGNER_INFO_sign'
> /usr/obj/usr/src/tmp/usr/lib/libcrypto.so: undefined reference to 
> `PKCS7_dataInit'
> /usr/obj/usr/src/tmp/usr/lib/libcrypto.so: undefined reference to 
> `PKCS7_dataDecode'
> /usr/obj/usr/src/tmp/usr/lib/libcrypto.so: undefined reference to 
> `PKCS7_signatureVerify'

Hi Steve,
What are your custom build options? Have you patched your copy of 
FreeBSD?
Thanks!
-NGie
___
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"

FreeBSD_HEAD-tests - Build #1635 - Still Unstable

2015-11-01 Thread jenkins-admin 
FreeBSD_HEAD-tests - Build #1635 - Still Unstable:

Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1635/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1635/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1635/console

Change summaries:

No changes


The failed test cases:

4 tests failed.
FAILED:  lib.libc.stdio.fmemopen2_test.test_data_length

Error Message:
/builds/FreeBSD_HEAD/lib/libc/tests/stdio/fmemopen2_test.c:203: pos == 0 not met

FAILED:  lib.libc.stdio.fmemopen_test.test09

Error Message:
3956 checks failed; see output for more details

FAILED:  lib.libc.stdio.fmemopen_test.test11

Error Message:
6020 checks failed; see output for more details

FAILED:  lib.libc.stdio.fmemopen_test.test14

Error Message:
1806 checks failed; see output for more details

___
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: [HEADSUP] OpenSSL updated to 1.0.2d

2015-11-01 Thread O. Hartmann 
On Sat, 31 Oct 2015 09:23:06 -0500
Eric van Gyzen  wrote:

> On 10/31/15 5:25 AM, O. Hartmann wrote:
> > Am Fri, 30 Oct 2015 16:57:45 -0400
> > Jung-uk Kim  schrieb:
> >  
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA256
> >>
> >> OpenSSL on head has been updated to 1.0.2d.  Please make sure to
> >> recompile all binaries depending on libcrypto.so.7 or libssl.so.7.  
> >
> > That is good news.
> >
> > Could you provide, please, some hints how one could check all installed
> > ports for the usage of those specific libraries? Or could you provide a
> > hint towards an existing port already providing those tools? It would be
> > great for those "from the set of ordinary people" using FreeBSD.
> >
> > I ask for that because I recall that there were a couple of ports which
> > explicitely asks for a selection of what SSL lib should be used and in my
> > case, I use the base system's one.  
> 
> I expect there's a port, but I'm not aware of one.
> 
> This should work:
> 
> find /usr/local/*bin /usr/local/lib* -type f | \
> while read F; do \
>   objdump -x $F 2>&1 | grep -Eq 'NEEDED  *lib(crypto|ssl).so.7' && \
>   echo $F; \
> done
> 
> This is in /bin/sh (or bash).  You could change "echo" to "pkg which"
> to show the package names.
> 
> Cheers,
> 
> Eric

Thank you very much.

For a "simple headless server" the update is much more convenient than for
systems with a graphical user's interface like X11, so having such a script at
hand via "UPDATING" other than a simple Email would be great.

Kind regards and thank you,

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