[QAT] 354300: 4x leftovers
- Fix build on -current - Update uses, - Options helper PR: 188146 Submitted by: Ports Fury - Build ID: 20140517084400-11994 Job owner: m...@freebsd.org Buildtime: 33 minutes Enddate: Sat, 17 May 2014 09:16:52 GMT Revision: 354300 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=354300 - Port:games/tuxtype 1.8.1_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140517084400-11994-38/tuxtype-1.8.1_2.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140517084400-11994-39/tuxtype-1.8.1_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140517084400-11994-40/tuxtype-1.8.1_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~m...@freebsd.org/20140517084400-11994-41/tuxtype-1.8.1_2.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140517084400-11994 redports https://qat.redports.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
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 +-+ www/drupal6-imce| 6.x-1.4 | 6.x-2.7 +-+ 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 http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Please commit or comment on PR ports/188930
Hi all I would like to ask, if someone could commit patches from ports/188930. It's an update of games/py-mnemosyne to the newest version 2.3. I would also like to take the maintainership, if there are no objections. I'm quite new to the port system and have additional questions: 1. Some of the files in games/py-mnemosyne are explicitly listed in `pkg-plist' and some are handled by `PYDISTUTILS_AUTOPLIST' in Makefile. Which one is better to use in the future? 2. If I understand correctly the `py-' prefix in port's name means that it is a Python library. Since games/py-mnemosyne is a standalone program, it should rather be called games/mnemosyne. What's the best strategy to rename the port? Best regards Henryk ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: New/Updated port
Kurt Jaeger wrote: Hi! Set the PR as an Update OOps put it as 'maintainer update' rather than 'update' ... is that wrong or is it as good as? It's a maintainer update, if the update was submitted by the current maintainer -- or with the intent to change the maintainer and the old maintainer already approved that change. Have you asked the current maintainer if he's fine if you take over ? No, and to be honest I probably don't meet the main requirement to take over (I don't have the free time) So, technically, 'update' is correct, 'maintainer-update' is probably not correct. Suggestion: Have a short description (one liner) next to the dropbox as that is non obvious. My thought maintainer update was it would be an update sent to the maintainer, where as 'Update' would be an approved update (ie the reverse of what it actually means) I just linked my URL rather than trying to persuade my browser to 'shar' it... That's ok 8-) I'll be on the road the next week, but I'll have a look if it's still open at that time. thanks. Michelle -- Michelle Sullivan http://www.mhix.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Sage update
On 17 May 2014, at 04:26, Montgomery-Smith, Stephen step...@missouri.edu wrote: I have started to think about making sage compatible with FreeBSD-10. The main problem thus far is that clang's c++ compiler is missing some stuff like the include file ext/numeric. That header is not missing, it became standardized, so use numeric instead. The libstdc++ developers added a bunch of upcoming things into the ext/ and tr1/ subdirectories in the past, but there is really no need to use these anymore, these days. I don't know if clang's c++ compiler is far behind gcc-4.7, or whether it is a question of merely copying a few include files from gcc-4.7. It is really the other way around; the C++ support in clang 3.4 is more advanced than the gcc 4.7 port. Clang 3.4 supports all of the C++11 standard, and some bits of the upcoming C++1y standard. According to gcc's own status pages, gcc 4.7 implements much of the C++11 standard, and for gcc 4.8, as of GCC 4.8.1, GCC's C++11 mode implements all of the major features of the C++11 standard. -Dimitry signature.asc Description: Message signed with OpenPGP using GPGMail
Re: clamav-0.98.3_2: LibClamAV Warning: Cannot dlopen libclamunrar_iface...
On Fri, 16 May 2014 07:22:41 +0200 Dr. Peter Voigt wrote: Am Thu, 15 May 2014 18:33:36 -0400 schrieb Renato Botelho ga...@freebsd.org: On Thursday, May 15, 2014 04:23:28 PM Shawn Webb wrote: On Thu, May 15, 2014 at 3:59 PM, Dr. Peter Voigt pvo...@uos.de wrote: After the upgrade to clamav-0.98.3_2 I am obtaining following error on every start of ClamAV: # service clamav-clamd start Starting clamav_clamd. LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar support unavailable ClamAV, however, seems to work correctly. Is this a known issue? I am on 10.0-RELEASE-p3 amd64. Regards, Peter Hey Peter, This can be fixed by applying this patch: https://github.com/vrtadmin/clamav-devel/commit/d17ee49f75e23b43fadf745c27dc 4dd16ee372e5 CC'd on this email is the ports maintainer for ClamAV. Fixed. Thanks! Yeah, thanks, I've just pulled in clamav-0.98.3_3 which has this issue fixed. % pkg version -v |grep clamav clamav-0.98.3_3= up-to-date with port % sudo /usr/local/etc/rc.d/clamav-clamd start Starting clamav_clamd. LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar support unavailable What revision should fix this issue? Did you forget to bump port revision? I'll rebuild clamav. Thanks. -- Herbert ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: clamav-0.98.3_2: LibClamAV Warning: Cannot dlopen libclamunrar_iface...
On Sat, May 17, 2014 at 9:28 AM, Herbert J. Skuhra hsku...@eumx.net wrote: On Fri, 16 May 2014 07:22:41 +0200 Dr. Peter Voigt wrote: Am Thu, 15 May 2014 18:33:36 -0400 schrieb Renato Botelho ga...@freebsd.org: On Thursday, May 15, 2014 04:23:28 PM Shawn Webb wrote: On Thu, May 15, 2014 at 3:59 PM, Dr. Peter Voigt pvo...@uos.de wrote: After the upgrade to clamav-0.98.3_2 I am obtaining following error on every start of ClamAV: # service clamav-clamd start Starting clamav_clamd. LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar support unavailable ClamAV, however, seems to work correctly. Is this a known issue? I am on 10.0-RELEASE-p3 amd64. Regards, Peter Hey Peter, This can be fixed by applying this patch: https://github.com/vrtadmin/clamav-devel/commit/d17ee49f75e23b43fadf745c27dc 4dd16ee372e5 CC'd on this email is the ports maintainer for ClamAV. Fixed. Thanks! Yeah, thanks, I've just pulled in clamav-0.98.3_3 which has this issue fixed. % pkg version -v |grep clamav clamav-0.98.3_3= up-to-date with port % sudo /usr/local/etc/rc.d/clamav-clamd start Starting clamav_clamd. LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar support unavailable What revision should fix this issue? Did you forget to bump port revision? I'll rebuild clamav. Thanks. Hey Herbert, Applying this patch will fix the issue: https://github.com/vrtadmin/clamav-devel/commit/d17ee49f75e23b43fadf745c27dc4dd16ee372e5 Renato, can you please add that patch to the port? Thanks, Shawn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: clamav-0.98.3_2: LibClamAV Warning: Cannot dlopen libclamunrar_iface...
On Sat, 17 May 2014 10:35:55 -0400 Shawn Webb wrote: On Sat, May 17, 2014 at 9:28 AM, Herbert J. Skuhra hsku...@eumx.net wrote: On Fri, 16 May 2014 07:22:41 +0200 Dr. Peter Voigt wrote: Am Thu, 15 May 2014 18:33:36 -0400 schrieb Renato Botelho ga...@freebsd.org: On Thursday, May 15, 2014 04:23:28 PM Shawn Webb wrote: On Thu, May 15, 2014 at 3:59 PM, Dr. Peter Voigt pvo...@uos.de wrote: After the upgrade to clamav-0.98.3_2 I am obtaining following error on every start of ClamAV: # service clamav-clamd start Starting clamav_clamd. LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar support unavailable ClamAV, however, seems to work correctly. Is this a known issue? I am on 10.0-RELEASE-p3 amd64. Regards, Peter Hey Peter, This can be fixed by applying this patch: https://github.com/vrtadmin/clamav-devel/commit/d17ee49f75e23b43fadf745c27dc 4dd16ee372e5 CC'd on this email is the ports maintainer for ClamAV. Fixed. Thanks! Yeah, thanks, I've just pulled in clamav-0.98.3_3 which has this issue fixed. % pkg version -v |grep clamav clamav-0.98.3_3= up-to-date with port % sudo /usr/local/etc/rc.d/clamav-clamd start Starting clamav_clamd. LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar support unavailable What revision should fix this issue? Did you forget to bump port revision? I'll rebuild clamav. Thanks. Hey Herbert, Applying this patch will fix the issue: https://github.com/vrtadmin/clamav-devel/commit/d17ee49f75e23b43fadf745c27dc4dd16ee372e5 Renato, can you please add that patch to the port? OK, this has been added in r354178. No idea why I still got this error in clamav-0.98.3_3. After rebuilding the port once more the error is gone. Thanks. -- Herbert ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Change port Maintained by email address
I am listed as the maintainer of the security/ppars port. The Maintained by: fbsd_u...@a1poweruser.com email address is incorrect. That email address got harvested and got targeted by spam senders, so I had to change it. Would like to change the port Maintained by: email address from fbsd_u...@a1poweruser.com to jo...@a1poweruser.com http://www.freebsd.org/cgi/ports.cgi?query=Probing+Abuse+Reporting+System stype=all Thanks Joe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Change port Maintained by email address
On 5/17/2014 17:23, joeb1 wrote: I am listed as the maintainer of the security/ppars port. The Maintained by: fbsd_u...@a1poweruser.com email address is incorrect. That email address got harvested and got targeted by spam senders, so I had to change it. Would like to change the port Maintained by: email address from fbsd_u...@a1poweruser.com to jo...@a1poweruser.com You are aware that the maintainer address is published everywhere [1] so the new address is going to get harvested again? John [1] starting when you emailed this message as all posts are published on public web-based mail archive ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
RE: Change port Maintained by email address
-Original Message- From: John Marino (FreeBSD) [mailto:freebsd.cont...@marino.st] Sent: Saturday, May 17, 2014 11:52 AM To: jo...@a1poweruser.com; freebsd-ports@freebsd.org Subject: Re: Change port Maintained by email address On 5/17/2014 17:23, joeb1 wrote: I am listed as the maintainer of the security/ppars port. The Maintained by: fbsd_u...@a1poweruser.com email address is incorrect. That email address got harvested and got targeted by spam senders, so I had to change it. Would like to change the port Maintained by: email address from fbsd_u...@a1poweruser.com to jo...@a1poweruser.com You are aware that the maintainer address is published everywhere [1] so the new address is going to get harvested again? John [1] starting when you emailed this message as all posts are published on public web-based mail archive Of course I know that. I now have email filter that flags spam and returns postmaster message that email account is un-known. So can a committer make this change or do I have to send a PR with a diff of the Makefile? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
clang problems with math/octave-forge-miscellaneous
I am trying to make the port math/octave-forge-miscellaneous clang
compliant. In the file ${WRKSRC}/partarray.cc is are lines like this:
Arrayoctave_idx_type bidc [maxdims], eidc [maxdims];
... stuff ...
eidc[i] = eidx;
The compilation dies saying that eidc is not defined. If I rewrite the
first line as
Arrayoctave_idx_type bidc [maxdims];
Arrayoctave_idx_type eidc [maxdims];
then it compiles just fine.
Is this a bug in the clang C++ compiler, or am I misunderstanding
something about C++?
Thanks, Stephen
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Sage update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/17/2014 08:04 AM, Dimitry Andric wrote: On 17 May 2014, at 04:26, Montgomery-Smith, Stephen step...@missouri.edu wrote: I have started to think about making sage compatible with FreeBSD-10. The main problem thus far is that clang's c++ compiler is missing some stuff like the include file ext/numeric. That header is not missing, it became standardized, so use numeric instead. The libstdc++ developers added a bunch of upcoming things into the ext/ and tr1/ subdirectories in the past, but there is really no need to use these anymore, these days. Thank you. In that case I'll work on getting sage to work with clang. I'll ask C++ questions as they arise. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTd5YQAAoJEC3xK9GaktgH3JUH/138LvkGfTBketWYBKbVSThv sJ3tJQ7TZ2xQnq0WEZXylGCUIl6kgSERNQnvn1zBqxnHiYAFx/c1C6H4WiI6qyBl rrrUcHwr23k9torEACIt/Se8QyZaquyDzqqQAlTrZXj0uRIeIAMepZo9wAQpCc6U p/UvKUAQaXftctm+1LOmUiyyxiscbEfMcQzz3xN6mVeaso/fLoFoFly9rfwC4KcP /7ZghXIWqwP8guT9ZAvg7uAQXYbrpLhzYfWLjwoB91JggcvBp/grTWHo0EvSj8eq HZ5lcDPumJqZ3JjCQHp5BVC7fvb7p/ejvGb5psg+mBdY7xtLIjMUJsqEEc6wRws= =3a5v -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: clang problems with math/octave-forge-miscellaneous
On 05/17/2014 12:00 PM, Montgomery-Smith, Stephen wrote:
I am trying to make the port math/octave-forge-miscellaneous clang
compliant. In the file ${WRKSRC}/partarray.cc is are lines like this:
Arrayoctave_idx_type bidc [maxdims], eidc [maxdims];
... stuff ...
eidc[i] = eidx;
The compilation dies saying that eidc is not defined.
I see the problem. The compiler actually goes wrong with
Arrayoctave_idx_type bidc [maxdims];
saying
partarray.cc:42:31: error: variable length array of non-POD element type
'Arrayoctave_idx_type'
So the error is somewhere else. Sorry for the noise. But if I don't
figure out the latter error, I'll be back with more questions.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: clang problems with math/octave-forge-miscellaneous
On Sat, 17 May 2014 17:13:51 + Montgomery-Smith, Stephen wrote:
On 05/17/2014 12:00 PM, Montgomery-Smith, Stephen wrote:
I am trying to make the port math/octave-forge-miscellaneous clang
compliant. In the file ${WRKSRC}/partarray.cc is are lines like this:
Arrayoctave_idx_type bidc [maxdims], eidc [maxdims];
... stuff ...
eidc[i] = eidx;
The compilation dies saying that eidc is not defined.
I see the problem. The compiler actually goes wrong with
Arrayoctave_idx_type bidc [maxdims];
saying
partarray.cc:42:31: error: variable length array of non-POD element type
'Arrayoctave_idx_type'
So the error is somewhere else. Sorry for the noise. But if I don't
figure out the latter error, I'll be back with more questions.
You'll have to declare it as Arrayoctave_idx_type *bidc and
use new[] and delete[].
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: clang problems with math/octave-forge-miscellaneous
On 05/17/2014 12:40 PM, Tijl Coosemans wrote:
On Sat, 17 May 2014 17:13:51 + Montgomery-Smith, Stephen wrote:
On 05/17/2014 12:00 PM, Montgomery-Smith, Stephen wrote:
I am trying to make the port math/octave-forge-miscellaneous clang
compliant. In the file ${WRKSRC}/partarray.cc is are lines like this:
Arrayoctave_idx_type bidc [maxdims], eidc [maxdims];
... stuff ...
eidc[i] = eidx;
The compilation dies saying that eidc is not defined.
I see the problem. The compiler actually goes wrong with
Arrayoctave_idx_type bidc [maxdims];
saying
partarray.cc:42:31: error: variable length array of non-POD element type
'Arrayoctave_idx_type'
So the error is somewhere else. Sorry for the noise. But if I don't
figure out the latter error, I'll be back with more questions.
You'll have to declare it as Arrayoctave_idx_type *bidc and
use new[] and delete[].
Thank you, thank you, thank you. That fixed it!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Upgrade dri-9.1.7_3,2 to dri-9.1.7_4,2
Just to inform you that there is something going wrong updating this port update: --- cut --- CC lp_rast_tri.lo lp_rast_debug.c: In function 'lp_scene_bin_size': lp_rast_debug.c:320: warning: passing argument 1 of 'lp_scene_get_bin' discards qualifiers from pointer target type CC lp_scene.lo In file included from lp_rast_tri.c:143: ../../../../src/gallium/auxiliary/util/u_sse.h:180: warning: '__artificial__' attribute directive ignored ../../../../src/gallium/auxiliary/util/u_sse.h: In function 'mm_mullo_epi32': ../../../../src/gallium/auxiliary/util/u_sse.h:206: note: use -flax-vector-conversions to permit conversions between vectors with differing element types or numbers of subparts ../../../../src/gallium/auxiliary/util/u_sse.h:206: error: incompatible type for argument 1 of '__builtin_ia32_psrlqi128' ../../../../src/gallium/auxiliary/util/u_sse.h:207: error: incompatible type for argument 1 of '__builtin_ia32_psrlqi128' gmake[4]: *** [lp_rast_tri.lo] Error 1 gmake[4]: *** Waiting for unfinished jobs gmake[4]: Leaving directory `/usr/ports/graphics/dri/work/Mesa-9.1.7/src/gallium/drivers/llvmpipe' gmake[3]: *** [all-recursive] Error 1 gmake[3]: Leaving directory `/usr/ports/graphics/dri/work/Mesa-9.1.7/src/gallium/drivers' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/graphics/dri/work/Mesa-9.1.7/src/gallium' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/dri/work/Mesa-9.1.7/src' gmake: *** [all-recursive] Error 1 === Compilation failed unexpectedly. *** [do-build] Error code 1 Stop in /usr/ports/graphics/dri. === make failed for graphics/dri === Aborting update === Update for graphics/dri failed === Aborting update === Killing background jobs Terminated === Exiting --- cut --- can you tell me how to solve this? Thanks BR, Jos Chrispijn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
