Re: www/nginx-full build failed (13.0-CURRENT/r484802)

there is a newer update https://svnweb.freebsd.org/ports?view=revision=485016 => update encrypted_session module to 0.08 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any

Re: ports head -r487783: on armv7 x11/pixman fails to build: /usr/bin/ld: error: can't create dynamic relocation R_ARM_V4BX against local symbol in readonly segment; recompile object files with -fPIC

Mark Millard via freebsd-x11 writes: > [Added: The original cross-build via poudriere-devel and qemu-user-static > did not get this problem. I give details later. Sumamry: Looks like -O2 > was used for the cross build and -O was used for armv7 native. The > difference is likely(?) from my

www/nginx-full build failed (13.0-CURRENT/r484802)

Hi all, nginx-full-1.14.1,2 (www/nginx-full) failed to build in 13.0-CURRENT with ports revision r484802 (detail log in [1]): Enable http_ssl module to build upstream_fair with SSL support This port install Passenger module only ===> License BSD2CLAUSE accepted by the user ===>

Re: ports head -r484652: lang/ruby24 fails to amd64 -> armv7 cross build: qemu: uncaught target signal 11 (2 of them) [armv7 native build worked]

[While the poudriere-devel/qemu-arm-static/nxb-bin/ amd64 -> armv7 cross build failed, a native armv7 build worked. It turns out the difference that matters is likely -O2 use vs -O use. More later below.] On 2018-Nov-10, at 23:29, Mark Millard wrote: > Poudriere-devel reported: > > [00:18:32]

Re: pkg falls behind port version - how do ports become pkg's?

On Mon, 12 Nov 2018, at 23:06, Karl Pielorz wrote: > >From what I can see mysql56-server in quarterly really does need updating > to fix the CVE's - so who am I best emailing to ask if > mysql56-server/client could be updated on security grounds? > > Thanks again, Hi Karl the best person is

Re: Upgrade from PHP71 to PHP72 breaks icingaweb2

On Thu, Nov 08, 2018 at 10:06:15PM +0100, Xavier wrote: > On 08/11/2018 14:17, Lars Engels wrote: > > Do you see any php related entries in your apache logs? > > > > No, just the stack trace on screen > I just encountered the same problem after upgrading from php71 to php72. I had to also

Re: freebsd-ports Digest, Vol 807, Issue 5

On Wednesday, 14 November 2018 22:05:38 CET freebsd-ports-requ...@freebsd.org wrote: > Date: Wed, 14 Nov 2018 21:00:20 +0900 > From: KIRIYAMA Kazuhiko > To: freebsd-ports@freebsd.org > Cc: k...@kx.openedu.org > Subject: multimedia/umplayer build failed (13.0-CURRENT/r339677) > Message-ID:

FreeBSD ports you maintain which are out of date

Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated,