Re: stable/12 broken?

2019-02-21 Thread Antoine Brodin
On Fri, Feb 22, 2019 at 7:39 AM Antoine Brodin wrote: > Hi, > > For your information, the stable/12 branch seems broken, at least on > i386, there is a segmentation fault when trying to run binaries and 0 > package can be produced. > The regression happened between > SVN Revision: Jail stable/12

stable/12 broken?

2019-02-21 Thread Antoine Brodin
Hi, For your information, the stable/12 branch seems broken, at least on i386, there is a segmentation fault when trying to run binaries and 0 package can be produced. The regression happened between SVN Revision: Jail stable/12 -> 344262 and SVN Revision: Jail stable/12 -> 344454 Antoine __

Re: Java support

2019-02-21 Thread Charlie Li via freebsd-stable
On 21/02/2019 18:00, Aristedes Maniatis wrote: > On 21/2/19 9:18pm, Kurt Jaeger wrote: >> Are there plans for the Foundation to sponsor some work in this area? >> Your point is, that the FreeBSD community should do regular testbuilds >> for >> >> https://github.com/AdoptOpenJDK/openjdk-jdk9u/ >> ht

Re: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)

2019-02-21 Thread Eugene Grosbein
21.02.2019 22:27, Harry Schmalzbauer wrote: >> The object is clearly corrupted. > > Thanks to your hint to readelf, I found out that it gets corrupted during > dump(8) (or resotore, not yet analyzed). > The obj tree contains the good version, the dump archive not. > The dump archive is used as s

Re: Java support

2019-02-21 Thread Aristedes Maniatis
On 21/2/19 9:18pm, Kurt Jaeger wrote: Are there plans for the Foundation to sponsor some work in this area? Your point is, that the FreeBSD community should do regular testbuilds for https://github.com/AdoptOpenJDK/openjdk-jdk9u/ https://github.com/AdoptOpenJDK/openjdk-jdk10u/ https://github.c

FreeBSD CI Weekly Report 2019-02-17

2019-02-21 Thread Li-Wen Hsu
(bcc -current and -stable for more audience) FreeBSD CI Weekly Report 2019-02-17 === Here is a summary of the FreeBSD Continuous Integration results for the period from 2019-02-11 to 2019-02-17. During this period, we have: * 2348 builds (93.4% passed, 6.6% faile

Re: Java support

2019-02-21 Thread Constantine A. Murenin
On Thu, 21 Feb 2019 at 04:19, Kurt Jaeger wrote: > Hi! > > > With the Java FreeBSD mailing list pretty quiet, I thought I might ask > > here whether anyone was working on porting the latest Java versions over > > to FreeBSD. > > There's the openjdk port, java/openjdk8. > > You are asking about in

Re: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)

2019-02-21 Thread Harry Schmalzbauer
Am 21.02.2019 um 10:36 schrieb Konstantin Belousov: … ELF Header: Magic: 7f 45 4c 46 02 01 01 09 00 00 00 00 00 00 00 00 Class: ELF64 Data: 2's complement, little endian Version: 1 (current)

Re: Java support

2019-02-21 Thread Kurt Jaeger
Hi! > With the Java FreeBSD mailing list pretty quiet, I thought I might ask > here whether anyone was working on porting the latest Java versions over > to FreeBSD. There's the openjdk port, java/openjdk8. You are asking about input from the FreeBSD community to openjdk9, 10 and 11 ? > While

Re: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)

2019-02-21 Thread Patrick M. Hausen
Hello, I don’t know if this is related or not, but when I compile the Nextcloud client port https://svnweb.freebsd.org/ports/head/deskutils/nextcloudclient/ on 11.2 by setting DEFAULT_VERSIONS+=ssl=openssl111 it dumps core, too. Kind regards Patrick -- punkt.de GmbH

Re: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)

2019-02-21 Thread Konstantin Belousov
On Thu, Feb 21, 2019 at 10:03:29AM +0100, Harry Schmalzbauer wrote: > Am 21.02.2019 um 09:54 schrieb Konstantin Belousov: > > On Thu, Feb 21, 2019 at 09:24:43AM +0100, Harry Schmalzbauer wrote: > >> Am 20.02.2019 um 17:51 schrieb Harry Schmalzbauer: > >>> Hello, > >>> > >> … > >>> gdb shows: > >>>

Re: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)

2019-02-21 Thread Harry Schmalzbauer
Am 21.02.2019 um 09:54 schrieb Konstantin Belousov: On Thu, Feb 21, 2019 at 09:24:43AM +0100, Harry Schmalzbauer wrote: Am 20.02.2019 um 17:51 schrieb Harry Schmalzbauer: Hello, … gdb shows: Core was generated by `/usr/sbin/auditdistd'. Program terminated with signal 11, Segmentation fault.

Re: Strange rtld-elf failure on stable/12 [Was: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)]

2019-02-21 Thread Konstantin Belousov
On Thu, Feb 21, 2019 at 09:24:43AM +0100, Harry Schmalzbauer wrote: > Am 20.02.2019 um 17:51 schrieb Harry Schmalzbauer: > > Hello, > > > … > > gdb shows: > > Core was generated by `/usr/sbin/auditdistd'. > > Program terminated with signal 11, Segmentation fault. > > Reading symbols from /lib/libut

Strange rtld-elf failure on stable/12 [Was: libcrypto.so.111 linked binaries SIGSEGV (in bhyve guest)]

2019-02-21 Thread Harry Schmalzbauer
Am 20.02.2019 um 17:51 schrieb Harry Schmalzbauer: Hello, … gdb shows: Core was generated by `/usr/sbin/auditdistd'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libutil.so.9...Reading symbols from /usr/lib/debug//lib/libutil.so.9.debug...done. done. Loade