I had to revert /usr/local/aarch64-freebsd from 2.28 for its bin/ld to work for -r315870 buildworld (adm64 -> arm64 cross build)

Building /usr/obj/pine64_clang/arm64.aarch64/usr/src/lib/libc/libc.so.7.full --- libc.so.7.full --- building shared library libc.so.7 /usr/local/aarch64-freebsd/bin/ld: getutxent.pico(.debug_info+0x3b): R_AARCH64_ABS64 used with TLS symbol udb /usr/local/aarch64-freebsd/bin/ld:

Re: devel/gvfs fails to build on 11-stable and ports r436799

Try recomüile sysutils/libcdio-paranoia. ___ 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"

devel/gvfs fails to build on 11-stable and ports r436799

Hello ports@, I'm on 11-stable r314138 with very recent ports (r436799). I'm trying to build devel/gvfs from ports. I'm getting the error below. Can anyone help please? mv -f .deps/gvfsd_cdda-daemon-main.Tpo .deps/gvfsd_cdda-daemon-main.Po cc -DHAVE_CONFIG_H -I. -I.. -I.. -I../common -I..

Re: Where is the library for icu-i18n ?

Thank you! Firefox is compiling now...in a day or two I might get to see if it works. 8-) bob On Thu, Mar 23, 2017 at 09:25:02PM +0100, Herbert J. Skuhra wrote: > bob prohaska skrev: > > > > In playing with compiling firefox on raspberry pi the process has gotten > > far enough to report: > >

Re: Where is the library for icu-i18n ?

bob prohaska skrev: > > In playing with compiling firefox on raspberry pi the process has gotten > far enough to report: > > DEBUG: configure: error: Library requirements (icu-i18n >= 58.1) not > met; consider adjusting the PKG_CONFIG_PATH environment variable if > your libraries are in a

Re: FreeBSD Port: kodi-16.1_9

Compiles with a "dirty" hack with doxygen installed (starts without problems, but not testes fully functionallity). patch-codegenerator.mk --- codegenerator.mk.orig 2017-03-23 19:10:40 UTC +++ codegenerator.mk @@ -11,20 +11,10 @@ ifeq ($(SWIG),) SWIG = swig-not-found endif -DOXYGEN

Where is the library for icu-i18n ?

In playing with compiling firefox on raspberry pi the process has gotten far enough to report: DEBUG: configure: error: Library requirements (icu-i18n >= 58.1) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can

TR: FreeBSD Port: xf86-video-intel-2.99.917.20170228

Hello, I have seen recently that libdrm has has been revised for an obscur minor/major checking. So I have updated libdrm and I have rebuilt the intel driver hoping this woult be linked with my issue. Unfortunately…. Same result = kernel panic I can confirm that my system is intializing drm

FreeBSD Port: kodi-16.1_9

Hello, Last KODI revision doesn’t build when port /devel/doxygen is installed. For un unknown reason at an early build stage in XML parsing building process is invoking doxygen, but doxygen process exit with an error and build stop shortly after. Deinstalling Doxygen solves the issue There is

RE: Samba 4.3

> -Original Message- > From: Jack L. [mailto:xxjack1...@gmail.com] > > I solved the issue by pkg delete -f *samba* and then it reinstalled fine. > Worked for me too in the FreeBSD 11/i386 case that had the same build error as you. The FreeBSD 11/amd64 build is still failing with the

Re: devel/pear update?

On 03/23/17 16:04, Jochen Neumeister wrote: Hi, We still have devel/pear 1.10.1 in the port tree: it is vulnerable, although "pkg audit" does not report this. 1.10.3 has been out for almost a month now. Do you have any plan to upgrade this? Are you encountering any showstopper? I hope to

Re: devel/pear update?

Hi! > We still have devel/pear 1.10.1 in the port tree: it is vulnerable, > although "pkg audit" does not report this. > > 1.10.3 has been out for almost a month now. > > Do you have any plan to upgrade this? > Are you encountering any showstopper? Can you submit a patch and test it ? Maybe

Re: devel/pear update?

Hi, We still have devel/pear 1.10.1 in the port tree: it is vulnerable, although "pkg audit" does not report this. 1.10.3 has been out for almost a month now. Do you have any plan to upgrade this? Are you encountering any showstopper? I hope to offer it at the weekend. Regards Jochen

devel/pear update?

Hello. We still have devel/pear 1.10.1 in the port tree: it is vulnerable, although "pkg audit" does not report this. 1.10.3 has been out for almost a month now. Do you have any plan to upgrade this? Are you encountering any showstopper? bye & Thanks av.

Re: Samba 4.3

On Thu, Mar 23, 2017 at 07:48:48AM +0100, Herbert J. Skuhra wrote: > The Doctor skrev: > > > > All right anyone seeing a failure in compilation > > due to a GSSAPI call? > > Why do you install Samba 4.3 and not 4.4? > > Are the samba ports still maintained? > > 4.2 discontinued (EOL)

RE: Samba 4.3

> Hello Wolfgang, > > are you building with default options, or did you set some specific (e.g. > DEVELOPMENT)? > > Best regards, > Matthias > > These are my options used (should be pretty much default to my knowledge): # This file is auto-generated by 'make config'. # Options for

Re: Samba 4.3

Hello Wolfgang, are you building with default options, or did you set some specific (e.g. DEVELOPMENT)? Best regards, Matthias Am Donnerstag, März 23, 2017 10:23 CET, "Meyer, Wolfgang" schrieb: > I am getting The Doctor's compilation issue for samba43 and samba44

Re: Samba 4.3

I solved the issue by pkg delete -f *samba* and then it reinstalled fine. On Thu, Mar 23, 2017 at 2:23 AM, Meyer, Wolfgang wrote: > I am getting The Doctor's compilation issue for samba43 and samba44 on a > FreeBSD 11.0/amd64 machine and Jack's compilation issue on a

Re: Samba 4.3

I am getting The Doctor's compilation issue for samba43 and samba44 on a FreeBSD 11.0/amd64 machine and Jack's compilation issue on a FreeBSD 11.0/i386 machine. The port (samba44) compiles fine on a FreeBSD 10.3/amd64 machine. Regards, Wolfgang Follow HOB: -

Re: Samba 4.3

Herbert J Skuhra skrev: > > The Doctor skrev: >> >> All right anyone seeing a failure in compilation >> due to a GSSAPI call? > > Why do you install Samba 4.3 and not 4.4? > > Are the samba ports still maintained? > > 4.2 discontinued (EOL) 2016-09-07 -> expire? > 4.3 discontinued

Re: Samba 4.3

The Doctor skrev: > > All right anyone seeing a failure in compilation > due to a GSSAPI call? Why do you install Samba 4.3 and not 4.4? Are the samba ports still maintained? 4.2 discontinued (EOL)2016-09-07 -> expire? 4.3 discontinued (EOL)2017-03-07 -> expire? 4.4 security fixes