[Bug 205139] net/tigervnc: build breaks when gcc and g++ are present and clang is the system compiler

2015-12-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205139 Gerald Pfeifer changed: What|Removed |Added Flags|maintainer-feedback?(gerald | |@FreeBSD.org)

[Bug 205139] net/tigervnc: build breaks when gcc and g++ are present and clang is the system compiler

2015-12-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205139 Gerald Pfeifer changed: What|Removed |Added Flags||maintainer-feedback?(meta+p

[Bug 205139] net/tigervnc: build breaks when gcc and g++ are present and clang is the system compiler

2015-12-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205139 --- Comment #2 from Ting-Wei Lan --- I don't think this problem is specific to tigervnc because all projects using autotools can break because of this change in lang/gcc. Users that manually download sources can no longer expect './configur

Re: Fwd: Memory leak or misconfiguration: Repeated allocation of very large block

2015-12-08 Thread Jason Unovitch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On December 5, 2015 6:43:55 AM EST, Sebastian Wolfgarten wrote: >Any views on this? > >> Anfang der weitergeleiteten Nachricht: >> >> Von: Sebastian Wolfgarten >> Datum: 25. Oktober 2015 um 11:55:42 MEZ >> An: po...@freebsd.org >> Betreff: Wtr: Me

Re: Fwd: Memory leak or misconfiguration: Repeated allocation of very large block

2015-12-08 Thread sebastian
Hi, I believe this has been solved, thanks for following up. Adam in CC has taken care. Best regards Sebastian Am 2015-12-08 18:03, schrieb Jason Unovitch: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On December 5, 2015 6:43:55 AM EST, Sebastian Wolfgarten wrote: Any views on this?

[Bug 205139] net/tigervnc: build breaks when gcc and g++ are present and clang is the system compiler

2015-12-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205139 John Marino changed: What|Removed |Added Assignee|freebsd-ports@FreeBSD.org |freebsd-ports-bugs@FreeBSD.

Re: Python and SWIG support in ports?

2015-12-08 Thread Craig Rodrigues
On Fri, Dec 4, 2015 at 6:44 PM, Kubilay Kocak wrote: > On 5/12/2015 9:40 AM, Craig Rodrigues wrote: > > Hi, > > > > I am working with the upstream maintainer of M2Crypto ( > > https://gitlab.com/m2crypto/m2crypto ). > > > > In the distutils that comes with Python, the swig binary is harcoded > >

How do I use "USES=shebangfix"

2015-12-08 Thread Avery Rozar
I'm trying to build port for snort-2.9.8.0 and have run into a snag. I get this error during "make makeplist". How do I use "USES=shebangfix" to fix this error? Do I put it in /etc/make.conf, the make file for snort? > Running Q/A tests (stage-qa) Error: '/bin/bash' is an invalid shebang you

Re: How do I use "USES=shebangfix"

2015-12-08 Thread Ben Woods
On Tuesday, 8 December 2015, Avery Rozar wrote: > I'm trying to build port for snort-2.9.8.0 and have run into a snag. I get > this error during "make makeplist". How do I use "USES=shebangfix" to fix > this error? Do I put it in /etc/make.conf, the make file for snort? > > > Running Q/A test

Re: Call for Help: need script for patching ports tree, building with poudriere

2015-12-08 Thread Craig Rodrigues
On Sun, Dec 6, 2015 at 6:12 AM, Ricky G wrote: > Hey, > Added this to github. > https://github.com/Ultima1252/portest > Nice work! Thanks for putting the effort into writing this script. I'll provide feedback on github. -- Craig ___ freebsd-ports@fr

Re: Python and SWIG support in ports?

2015-12-08 Thread Kubilay Kocak
On 9/12/2015 4:53 AM, Craig Rodrigues wrote: > On Fri, Dec 4, 2015 at 6:44 PM, Kubilay Kocak > wrote: > > On 5/12/2015 9:40 AM, Craig Rodrigues wrote: > > Hi, > > > > I am working with the upstream maintainer of M2Crypto ( > > https://gitlab.com/m2cry

Re: Python and SWIG support in ports?

2015-12-08 Thread Craig Rodrigues
On Tue, Dec 8, 2015 at 4:09 PM, Kubilay Kocak wrote: > The correct thing to do is be PEP-394'ish compatible (even though swig > itself isnt a python package). Again swig20 is a short term solution. > > I have no idea why you refered to PEP394. > The root cause is technically an inadequate 'fin