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 mail to "freebsd-ports-unsubscr...@freebsd.org"
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 materials but not supporting both ways of > building is likely a problem with the port(?).] x11/pixman builds fine on armv7 even with -O. Tested both Clang/LLD 6.0 and 7.0 after forcing MACHINE_CPUARCH=arm on command line. ___ 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"
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 ===> nginx-full-1.14.1,2 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by nginx-full-1.14.1,2 for building ===> Extracting for nginx-full-1.14.1,2 => SHA256 Checksum OK for nginx-1.14.1.tar.gz. => SHA256 Checksum OK for ngx_cache_purge-2.3.tar.gz. => SHA256 Checksum OK for nginx_mogilefs_module-1.0.4.tar.gz. => SHA256 Checksum OK for nginx_mod_h264_streaming-2.2.7.tar.gz. => SHA256 Checksum OK for ngx_http_redis-0.3.9.tar.gz. => SHA256 Checksum OK for ngx_http_response-0.3.tar.gz. => SHA256 Checksum OK for 08a395c66e42.tar.gz. => SHA256 Checksum OK for modsecurity-2.9.2.tar.gz. => SHA256 Checksum OK for passenger-5.3.5.tar.gz. => SHA256 Checksum OK for ngx_slowfs_cache-1.10.tar.gz. => SHA256 Checksum OK for yaoweibin-nginx_ajp_module-bf6cd93_GH0.tar.gz. => SHA256 Checksum OK for openresty-array-var-nginx-module-v0.05_GH0.tar.gz. => SHA256 Checksum OK for anomalizer-ngx_aws_auth-1e62670_GH0.tar.gz. => SHA256 Checksum OK for eustas-ngx_brotli-e26248e_GH0.tar.gz. => SHA256 Checksum OK for nginx-clojure-nginx-clojure-v0.4.5_GH0.tar.gz. => SHA256 Checksum OK for grahamedgecombe-nginx-ct-v1.3.2_GH0.tar.gz. => SHA256 Checksum OK for simpl-ngx_devel_kit-v0.3.0_GH0.tar.gz. => SHA256 Checksum OK for openresty-drizzle-nginx-module-v0.1.11_GH0.tar.gz. => SHA256 Checksum OK for cubicdaiya-ngx_dynamic_upstream-v0.1.3_GH0.tar.gz. => SHA256 Checksum OK for openresty-echo-nginx-module-c65f5c6_GH0.tar.gz. => SHA256 Checksum OK for openresty-encrypted-session-nginx-module-v0.07_GH0.tar.gz. => SHA256 Checksum OK for happyfish100-fastdfs-nginx-module-8796a7d_GH0.tar.gz. => SHA256 Checksum OK for calio-form-input-nginx-module-v0.12_GH0.tar.gz. => SHA256 Checksum OK for mdirolf-nginx-gridfs-v0.8_GH0.tar.gz. => SHA256 Checksum OK for mongodb-mongo-c-driver-v0.3.1_GH0.tar.gz. => SHA256 Checksum OK for openresty-headers-more-nginx-module-55fbdab_GH0.tar.gz. => SHA256 Checksum OK for giom-nginx_accept_language_module-2f69842_GH0.tar.gz. => SHA256 Checksum OK for atomx-nginx-http-auth-digest-cd86418_GH0.tar.gz. => SHA256 Checksum OK for stnoonan-spnego-http-auth-nginx-module-7e028a5_GH0.tar.gz. => SHA256 Checksum OK for kvspb-nginx-auth-ldap-42d195d_GH0.tar.gz. => SHA256 Checksum OK for sto-ngx_http_auth_pam_module-v1.5.1_GH0.tar.gz. => SHA256 Checksum OK for arut-nginx-dav-ext-module-v0.1.0_GH0.tar.gz. => SHA256 Checksum OK for openresty-nginx-eval-module-582bd25_GH0.tar.gz. => SHA256 Checksum OK for aperezdc-ngx-fancyindex-v0.4.3_GH0.tar.gz. => SHA256 Checksum OK for alibaba-nginx-http-footer-filter-1.2.2_GH0.tar.gz. => SHA256 Checksum OK for leev-ngx_http_geoip2_module-3.2_GH0.tar.gz. => SHA256 Checksum OK for nginx-modules-ngx_http_json_status_module-1d2f303_GH0.tar.gz. => SHA256 Checksum OK for kr-nginx-notice-3c95966_GH0.tar.gz. => SHA256 Checksum OK for slact-nchan-v1.1.14_GH0.tar.gz. => SHA256 Checksum OK for wandenberg-nginx-push-stream-module-0.5.4_GH0.tar.gz. => SHA256 Checksum OK for yaoweibin-ngx_http_substitutions_filter_module-v0.6.4_GH0.tar.gz. => SHA256 Checksum OK for tarantool-nginx_upstream_module-1278ee5_GH0.tar.gz. => SHA256 Checksum OK for Austinb-nginx-upload-module-72ec037_GH0.tar.gz. => SHA256 Checksum OK for masterzen-nginx-upload-progress-module-afb2d31_GH0.tar.gz. => SHA256 Checksum OK for yaoweibin-nginx_upstream_check_module-9aecf15_GH0.tar.gz. => SHA256 Checksum OK for cryptofuture-nginx-upstream-fair-b5be36f_GH0.tar.gz. => SHA256 Checksum OK for wandenberg-nginx-video-thumbextractor-module-0.9.0_GH0.tar.gz. => SHA256 Checksum OK for anthonyryan1-mod_zip-74ef235_GH0.tar.gz. => SHA256 Checksum OK for calio-iconv-nginx-module-v0.14_GH0.tar.gz. => SHA256 Checksum OK for arut-nginx-let-module-v0.0.4_GH0.tar.gz. => SHA256 Checksum OK for openresty-lua-nginx-module-v0.10.13_GH0.tar.gz. => SHA256 Checksum OK for openresty-memc-nginx-module-v0.18_GH0.tar.gz. => SHA256 Checksum OK for nbs-system-naxsi-0.56_GH0.tar.gz. => SHA256 Checksum OK for nginx-njs-992e93d_GH0.tar.gz. => SHA256 Checksum OK for FRiCKLE-ngx_postgres-1.0rc7_GH0.tar.gz. => SHA256 Checksum OK for openresty-rds-csv-nginx-module-v0.08_GH0.tar.gz. => SHA256 Checksum OK for openresty-rds-json-nginx-module-v0.14_GH0.tar.gz. => SHA256 Checksum OK for openresty-redis2-nginx-module-v0.15_GH0.tar.gz. => SHA256 Checksum OK for arut-nginx-rtmp-module-v1.2.1_GH0.tar.gz. => SHA256 Checksum OK for openresty-set-misc-nginx-module-cda7e50_GH0.tar.gz. => SHA256 Checksum OK for sflow-nginx-sflow-module-543c72a_GH0.tar.gz. => SHA256 Checksum OK for nginx-shib-nginx-http-shibboleth-f07bf3c_GH0.tar.gz. => SHA256 Checksum OK for cubicdaiya-ngx_small_light-v0.9.2_GH0.tar.gz. => SHA256 Checksum OK for
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] [07] [00:02:56] Saved lang/ruby24 | ruby-2.4.5,1 wrkdir to: > /usr/local/poudriere/data/wrkdirs/FBSDFSSDjailArmV7-default/default/ruby-2.4.5,1.tbz > [00:18:32] [07] [00:02:56] Finished lang/ruby24 | ruby-2.4.5,1: Failed: build > > The log showed: > > --- miniruby --- > linking miniruby > --- .rbconfig.time --- > --- encdb.h --- > generating encdb.h > --- .rbconfig.time --- > qemu: uncaught target signal 11 (Segmentation fault) - core dumped > Segmentation fault > *** [.rbconfig.time] Error code 139 > > make[1]: stopped in /wrkdirs/usr/ports/lang/ruby24/work/ruby-2.4.5 > --- encdb.h --- > qemu: uncaught target signal 11 (Segmentation fault) - core dumped > Segmentation fault > *** [encdb.h] Error code 139 > > make[1]: stopped in /wrkdirs/usr/ports/lang/ruby24/work/ruby-2.4.5 > 2 errors > > > Despite how the above looks, I find only one .core file in the > tar archive produced for the failure: > > # find /wrkdirs/usr/ports/lang/ruby/ -name "*.core" -print > /wrkdirs/usr/ports/lang/ruby/work/ruby-2.4.5/qemu_miniruby.core > > Apparently qemu does not allow for separate files for distinct > processes. > > For that .core file I find (libexec/gdb): > > # chroot /usr/obj/DESTDIRs/clang-armv7-installworld-poud > # cd /wrkdirs/usr/ports/lang/ruby/work/ruby-2.4.5/ > # /usr/libexec/gdb miniruby qemu_miniruby.core > . . . > (gdb) bt > #0 0x00113f84 in rb_gc_writebarrier_unprotect (obj=4104601600) at gc.c:1119 > 1119 return RVALUE_WB_UNPROTECTED_BITMAP(obj) != 0; > [New Thread f4b5d000 (LWP 100638/)] > [New LWP 61684] > Current language: auto; currently minimal > (gdb) bt > #0 0x00113f84 in rb_gc_writebarrier_unprotect (obj=4104601600) at gc.c:1119 > #1 0x000c3fc8 in rb_include_class_new (module=4104569400, super= optimized out>) at ruby.h:1456 > #2 0x000c4424 in include_modules_at (klass=4104602160, c=4104602160, > module=4104569400, search_super=) at class.c:913 > #3 0x000c41f0 in rb_include_module (klass=4104602160, module=4104569400) at > class.c:870 > #4 0x001f6dec in Init_String () at string.c:10021 > #5 0x00129398 in rb_call_inits () at inits.c:28 > #6 0x00103bac in ruby_setup () at eval.c:60 > #7 0x00103be8 in ruby_init () at eval.c:76 > #8 0x000a3300 in main (argc=11, argv=0x9fffe41c) at main.c:35 > (gdb) up > #1 0x000c3fc8 in rb_include_class_new (module=4104569400, super= optimized out>) at ruby.h:1456 > 1456 rb_gc_writebarrier_unprotect(x); > (gdb) up > #2 0x000c4424 in include_modules_at (klass=4104602160, c=4104602160, > module=4104569400, search_super=) at class.c:913 > 913 iclass = rb_include_class_new(module, RCLASS_SUPER(c)); > (gdb) up > #3 0x000c41f0 in rb_include_module (klass=4104602160, module=4104569400) at > class.c:870 > 870 changed = include_modules_at(klass, RCLASS_ORIGIN(klass), module, > TRUE); > (gdb) up > #4 0x001f6dec in Init_String () at string.c:10021 > 10021 rb_include_module(rb_cString, rb_mComparable); > (gdb) up > #5 0x00129398 in rb_call_inits () at inits.c:28 > 28CALL(String); > (gdb) up > #6 0x00103bac in ruby_setup () at eval.c:60 > 60rb_call_inits(); > (gdb) up > #7 0x00103be8 in ruby_init () at eval.c:76 > 76int state = ruby_setup(); > (gdb) up > #8 0x000a3300 in main (argc=11, argv=0x9fffe41c) at main.c:35 > 35ruby_init(); > > (I'm not familiar with what details libexec/gdb gets > right vs. wrong. But the call chain seems coherent.) > > Host environment: > > # uname -apKU > FreeBSD FBSDFSSD 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r340287M: Fri Nov 9 > 08:37:01 PST 2018 > markmi@FBSDFSSD:/usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/sys/GENERIC-NODBG > amd64 amd64 133 133 A prior example that fails for native armv7 builds but works for poudriere-devel/qemu-arm-static/nxb-bin/ (native cross tools based) amd64 -> armv7 cross builds is x11/pixman. Previously I discovered that x11/pixman builds fine in poudriere-devel/qemu-arm-static/nxb-bin/ amd64 -> armv7 cross builds but a link fails during native armv7 builds. It turned out that with the host-native cross tools involved -O2 was being used where native -O was being used: the code in share/mk/sys.mk that is designed to use -O for arm fails to do so and uses -O2 instead. (MACHINE_ARCH temporarily looks to be amd64, which gets a -O2 put in CFLAGS instead of -O .) ruby seems to go the other direction: with -O2 involved something builds that fails to run during the build. With -O involved instead ruby builds fine and produces a ruby that works. (I've not done any analysis to see if the -O2 based build failure is because of code making assumption that are not guaranteed vs. if the compiler/linker is
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 the maintainer of that port (now in CC) and request a "MFH" or "Move From Head". You can see who this in the Makefile or via https://www.freshports.org/databases/mysql56-server for example. A+ Dave ___ 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: 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 upgrade mod_php71 to mod_php72 and restart Apache afterwards. Now Icinga Web 2 is up and running again. ___ 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: 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: <201811141200.waec0kdi079...@kx.openedu.org> > Content-Type: text/plain; charset=US-ASCII > > Hi all, > > umplayer-0.97_4 (multimedia/umplaye) failed to build in > 13.0-CURRENT with port revision r339677 (detail log in [1]): This is unrelated to multimedia/umplayer, and is simply that net/qt4-qnetwork does not build with the latest openssl. *Some* fixes have gone in (and out), but they are not enough and I'm having a devil of a time finding hours in the day to work on this (aside from the fact that Qt4 is scheduled for removal and was EOL'ed upstream years ago). [ade] signature.asc Description: This is a digitally signed message part.
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, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ databases/bbdb | 3.2 | bbdb_file.format.5 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt 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"
