Re: ports recently marked broken on -current
Em 23/05/2017 21:13, Mark Linimon escreveu: So during my pass over recent powerpc64 package errorlogs, I found a few ports that were actually broken across all archs on -current, and made those commits. I may not have enough cycles to investigate all these down by myself, so I'm asking for help. Does anyone recognize any of these failure modes, and if so, can recommend a fix? I've grouped them together based on my analysis, which may not be correct. Note: error messages from gcc and clang are intermixed. Thanks. mcl benchmarks/dbs tcp_debug.h: field has incomplete type 'struct tcpcb' security/revealrk revealrk.c: 'struct xtcpcb' has no member named 'xt_socket' security/pidentdk_freebsd2.c: storage size of 'pcbp' isn't known japanese/nethack34 stdlib.h: conflicting types for 'srandom' net-mgmt/netdatafreebsd_sysctl.c: storage size of 'vmmeter_data' isn't known sysutils/asmem read_mem.c: invalid use of undefined type 'struct vmmeter' net/lft lft_types.h: pcap-int.h: No such file or directory security/dsniff pcaputil.c: '/usr/include/pcap-int.h' file not found sysutils/pftop sf-gencode.h: pcap-int.h: No such file or directory sysutils/scprotect scprotect.c: 'sysctl__' undeclared (first use in this function) www/cherokeeunable to detect data struct is used by crypt_r ___ 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" Hi! I did some investigation about the "invalid use of undefined type 'struct vmmeter'" and found that for FreeBSD12 programs that uses the struct vmmeter needs define _WANT_VMMETER because /usr/src/sys/sys/vmmeter.h now have this test #if defined(_KERNEL) || defined(_WANT_VMMETER) before vmmeter definition. []'s -Otacilio #if __FreeBSD_version < 1200017 ___ 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: New 2017Q3 branch
> On 1 Jul, 2017, at 15:38, René Ladanwrote: > > On 01-07-2017 23:17, Larry Rosenman wrote: >> >> >> June 3 is long ago. Itym July 3 >> > [..snipped unreadable original :( ...] > > Ah yes, July 2nd will be when the new packages will start building. > Thanks for catching this. I was looking forward to a whole year of no package build failure notices. # Adam -- Adam Weinberger ad...@adamw.org https://www.adamw.org ___ 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"
[FreeBSD-Ports-Announce] New 2017Q3 branch
Hi, The 2017Q3 branch has been created. It means that the next update on the quarterly packages will be on the 2017Q3 branch. A lot of things happened in the last three months: - pkg 1.10.1 - New USES: cargo, groff, meson - Default version of PostgreSQL switched from 9.3 to 9.5 - Default version of Python 3 switched from 3.5 to 3.6 - Firefox 54.0.1 - Firefox-esr 52.2.1 - Chromium 59.0.3071.115 - Ruby 2.2.7 and 2.3.4 - default generator for USES=cmake ports has been switched to ninja Next quarterly package builds will start on June 2nd, 01:00 UTC and should be available on your closest mirrors few days later. For those stat nerds out there, here's what happened during the last 3 months on head: Number of commits: 7102 Number of committers: 171 Most active committers: 2457 sunpoet 309 amdmi3 252 miwi 186 jrm 181 antoine 155 bapt 151 jbeich 135 kwm 122 olgeni 114 linimon Diffstat: 17826 files changed, 300281 insertions(+), 260178 deletions(-) and on the 2017Q2 branch: Number of commits: 282 Number of committers: 54 Most active committers: 62 jbeich 24 feld 18 riggs 11 sunpoet 10 mat 9 rakuco 8 tz 8 miwi 8 brnrd 8 adamw Diffstat: 2909 files changed, 25534 insertions(+), 17588 deletions(-) Regards, René Ladan signature.asc Description: OpenPGP digital signature
Re: New 2017Q3 branch
On 01-07-2017 23:17, Larry Rosenman wrote: > > > June 3 is long ago. Itym July 3 > [..snipped unreadable original :( ...] Ah yes, July 2nd will be when the new packages will start building. Thanks for catching this. René ___ 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: New 2017Q3 branch
June 3 is long ago. Itym July 3 > > On Jul 1, 2017 at 4:15 PM,wrote: > > > Hi, The 2017Q3 branch has been created. It means that the next update on the > quarterly packages will be on the 2017Q3 branch. A lot of things happened in > the last three months: - pkg 1.10.1 - New USES: cargo, groff, meson - Default > version of PostgreSQL switched from 9.3 to 9.5 - Default version of Python 3 > switched from 3.5 to 3.6 - Firefox 54.0.1 - Firefox-esr 52.2.1 - Chromium > 59.0.3071.115 - Ruby 2.2.7 and 2.3.4 - default generator for USES=cmake ports > has been switched to ninja Next quarterly package builds will start on June > 2nd, 01:00 UTC and should be available on your closest mirrors few days > later. For those stat nerds out there, here's what happened during the last 3 > months on head: Number of commits: 7102 Number of committers: 171 Most active > committers: 2457 sunpoet 309 amdmi3 252 miwi 186 jrm 181 antoine 155 bapt 151 > jbeich 135 kwm 122 olgeni 114 linimon Diffstat: 17826 files changed, 300281 > insertions(+), 260178 deletions(-) and on the 2017Q2 branch: Number of > commits: 282 Number of committers: 54 Most active committers: 62 jbeich 24 > feld 18 riggs 11 sunpoet 10 mat 9 rakuco 8 tz 8 miwi 8 brnrd 8 adamw > Diffstat: 2909 files changed, 25534 insertions(+), 17588 deletions(-) > Regards, René Ladan > ___ 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"
New 2017Q3 branch
Hi, The 2017Q3 branch has been created. It means that the next update on the quarterly packages will be on the 2017Q3 branch. A lot of things happened in the last three months: - pkg 1.10.1 - New USES: cargo, groff, meson - Default version of PostgreSQL switched from 9.3 to 9.5 - Default version of Python 3 switched from 3.5 to 3.6 - Firefox 54.0.1 - Firefox-esr 52.2.1 - Chromium 59.0.3071.115 - Ruby 2.2.7 and 2.3.4 - default generator for USES=cmake ports has been switched to ninja Next quarterly package builds will start on June 2nd, 01:00 UTC and should be available on your closest mirrors few days later. For those stat nerds out there, here's what happened during the last 3 months on head: Number of commits: 7102 Number of committers: 171 Most active committers: 2457 sunpoet 309 amdmi3 252 miwi 186 jrm 181 antoine 155 bapt 151 jbeich 135 kwm 122 olgeni 114 linimon Diffstat: 17826 files changed, 300281 insertions(+), 260178 deletions(-) and on the 2017Q2 branch: Number of commits: 282 Number of committers: 54 Most active committers: 62 jbeich 24 feld 18 riggs 11 sunpoet 10 mat 9 rakuco 8 tz 8 miwi 8 brnrd 8 adamw Diffstat: 2909 files changed, 25534 insertions(+), 17588 deletions(-) Regards, René Ladan signature.asc Description: OpenPGP digital signature
Re: math/R: Build failure after PORTREVISION for shlib change
On Thu, Jun 29, 2017 at 12:39:50PM -0300, Joseph Mingrone wrote: > ... > With those options, the build succeeds in an 11.0-RELEASE-p1 jail. > http://pkg.awarnach.mathstat.dal.ca/data/11amd64-default/2017-06-28_16h53m48s/logs/R-3.4.0_2.log > ... > Everything matches. The successful build in poudriere even has the same > line that generates the error for you. > > /usr/local/bin/gcc-ar5 -cr libtre.a regcomp.o regerror.o regexec.o tre-ast.o > tre-compile.o tre-match-approx.o tre-match-backtrack.o tre-match-parallel.o > tre-mem.o tre-parse.o tre-stack.o xmalloc.o > > Could you have something in your environment or in make.conf that's > causing a problem? > As expected, further attempts to build math/R on my laptop have continued to fail as before -- and as mentioned, I ran a poudriere run, where building the package for math/R worked. That said, the line in the poudriere log that corresponds to the failing invocation is a bit different in my case. (I found a couple of small options differences, such as paper size; I don't believe those have anything to do with the observed differences, but I've corrected them for tomorrow's poudriere run.) The line in the failing case (with the immediately preceding line for context): ... gcc5 -I. -I. -I../../../src/include -I../../../src/include -DLIBICONV_PLUG -I/usr/local/include -isystem /usr/local/include -DHAVE_CONFIG_H -fopenmp -fpic -O2 -pipe -DLIBICONV_PLUG -fstack-protector -Wl,-rpath=/usr/local/lib/gcc5 -isystem /usr/local/include -fno-strict-aliasing -flto -fvisibility=hidden -c xmalloc.c -o xmalloc.o /usr/local/bin/gcc-ar5 -cr libtre.a regcomp.o regerror.o regexec.o tre-ast.o tre-compile.o tre-match-approx.o tre-match-backtrack.o tre-match-parallel.o tre-mem.o tre-parse.o tre-stack.o xmalloc.o ar: unrecognized option `--plugin' and in the successful poudriere run: ... cc -I. -I. -I../../../src/include -I../../../src/include -DLIBICONV_PLUG -I/usr/local/include -isystem /usr/local/include -DHAVE_CONFIG_H-fpic -O2 -pipe -DLIBICONV_PLUG -fstack-protector -isystem /usr/local/include -fno-strict-aliasing -fvisibility=hidden -c xmalloc.c -o xmalloc.o /usr/local/bin/ar -cr libtre.a regcomp.o regerror.o regexec.o tre-ast.o tre-compile.o tre-match-approx.o tre-match-backtrack.o tre-match-parallel.o tre-mem.o tre-parse.o tre-stack.o xmalloc.o Looking (on the laptop) at plausible "ar" executables in /usr/local/bin, I see: g1-227(12.0-C)[3] (cd /usr/local/bin && ls -lTi gcc-ar* ar) 1850562 -r-xr-xr-x 2 root wheel 6368928 Mar 23 05:10:40 2017 ar 1850780 -r-xr-xr-x 2 root wheel25728 May 1 05:47:28 2017 gcc-ar49 1846261 -r-xr-xr-x 2 root wheel26192 Jun 30 04:57:30 2017 gcc-ar5 g1-227(12.0-C)[4] Apparently "ar" was installed by binutils-2.28,1, while the gcc-ar* were installed by gcc49-4.9.4_3 and gcc5-5.4.0_2, respectively. Weird. Peace, david -- David H. Wolfskill da...@catwhisker.org Congratulations on the sesquicentennial, Canada! :-) See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
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 +-+ graphics/opencollada| 1.6.47 | v1.6.56 +-+ multimedia/vdr | 1.7.29 | 2.3.8 +-+ science/py-pyteomics| 3.4.1 | 3.4.2 +-+ 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"
Re: Vulnerability
Op 30-6-2017 om 18:23 schreef Carlos Jacobo Puga Medina: I have submitted a patch to update libgcrypt to 1.7.8 (still pending for an exp-run) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220382 You can grab the patch, apply and build the port. Thanks Carlos, appreciate your support. ./Jos ___ 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"