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

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205139

Gerald Pfeifer  changed:

   What|Removed |Added

  Flags|maintainer-feedback?(gerald |
   |@FreeBSD.org)   |
   Assignee|ger...@freebsd.org  |freebsd-ports@FreeBSD.org
 CC||ger...@freebsd.org,
   ||meta+po...@vmeta.jp
Summary|lang/gcc: gcc and g++   |net/tigervnc: build breaks
   |symlinks break tigervnc |when gcc and g++ are
   |build and possibly many |present and clang is the
   |other programs  |system compiler

--- Comment #1 from Gerald Pfeifer  ---
If a port breaks because some other packages are installed, but should
not be used for that port (Why is that happening here, by the way?) that
looks like an issue with that port, doesn't it?

Adding maintainer for net/tigervnc.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
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"

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

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205139

Gerald Pfeifer  changed:

   What|Removed |Added

  Flags||maintainer-feedback?(meta+p
   ||o...@vmeta.jp)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
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"

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

[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 './configure && make' to work. We can set
environment variables in ports to prevent gcc and g++ from being found by
configure scripts, but I don't think we should force all users to set CC, CPP,
CXX to keep their systems working after installing a package.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
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: Fwd: Memory leak or misconfiguration: Repeated allocation of very large block

[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: Memory leak or misconfiguration: Repeated allocation of
>very large block
>>
>> To whom it may concern,
>>
>> in view of the discussion below may I suggest we remove the --with-gc
>option from the Dovecot default options?
>>
>> Thanks.
>>
>> Kind regards
>> Sebastian
>>
>>> Anfang der weitergeleiteten Nachricht:
>>>
>>> Von: Sebastian Wolfgarten >
>>> Datum: 25. Oktober 2015 um 11:54:15 MEZ
>>> An: Timo Sirainen mailto:t...@iki.fi>>
>>> Kopie: dove...@dovecot.org 
>>> Betreff: Aw: Memory leak or misconfiguration: Repeated allocation of
>very large block
>>>
>>> Hi Timo,
>>>
>>> alright, thanks I will recompile without gc - this is a standard
>build option on FreeBSD but I will get the port maintainer to maybe
>change this.
>>>
>>> Best regards
>>> Sebastian
>>>
 Am 24.10.2015 um 23:19 schrieb Timo Sirainen >:

 On 24 Oct 2015, at 14:59, Sebastian Wolfgarten
>mailto:sebast...@wolfgarten.com>> wrote:
>
> Dear all,
>
> I am using Dovecot 2.2.19 and I keep on getting the following
>warnings in my mail.log file on FreeBSD 10:
>
> Oct 24 10:45:28 server1 dovecot: imap: Error: GC Warning: Repeated
>allocation of very large block (appr. size 20480):
> Oct 24 10:45:28 server1 dovecot: imap: Error: May lead to memory
>leak and poor performance.
>
> I am wondering whether this is a configuration issue (i.e. a
>mistake in my current config) or whether I am hitting a bug. What’s the
>best way of figuring this one out? I tried increasing the verbosity of
>the logs but it did not really provide me with further information.

 I guess you have configured Dovecot --with-gc? I guess it's
>possible this is a bug, but it could just as well be a false alarm. In
>general I don't recommend/support --with-gc option (and I should
>probably just remove it altogether). The easiest and the most usable
>way of finding memory leaks is to run with valgrind (which must be done
>without-gc):

 service imap {
 executable = /usr/bin/valgrind -q --show-reachable=yes
>--leak-check=full /usr/libexec/dovecot/imap
 }

 I'm not aware of any memory leaks right now.

>>>
>>

Have you filed a PR for the issue and/or reported this to the mail/dovecot2 
maintainer?
-BEGIN PGP SIGNATURE-

iQFHBAEBCgAxKhxKYXNvbiBVbm92aXRjaCA8amFzb24udW5vdml0Y2hAZ21haWwu
Y29tPgUCVmcNXAAKCRBv1JwwFhyqbuCBB/0Yqw6Bhecsegznzx21WxZD+aJzd9k5
8OPUT3VbTtkK33BKgozZYFzEW0+9XSdU6vK+AreuBcWAtMb34F5W6H3uqfezv0by
HvdftdIbUao1TYUhGlDL21k1PaNNPpfoDkqpTTV0eEAuM0p3ZZP3YWwWSXGzmvgu
KGZKdx3SF/oy6Ut2DHYZIj5JQVBd20wZrFtKt6/orudn12eFEfWcB9fTqQ1ESJBf
Q1Ue2zsPUQn7AcbP/UW99CdgV+BTM5rI7yZu8ohnJWj0rimSmWMWY5cqbzbBkTem
hBRdJ+KMD0SpdOHw7zGMHKN+MHLWCBl+4ZmIUxOEPbolLoljAdvbTt4i
=FN+e
-END PGP SIGNATURE-

___
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: Fwd: Memory leak or misconfiguration: Repeated allocation of very large block

[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?


Anfang der weitergeleiteten Nachricht:

Von: Sebastian Wolfgarten 
Datum: 25. Oktober 2015 um 11:55:42 MEZ
An: po...@freebsd.org
Betreff: Wtr: Memory leak or misconfiguration: Repeated allocation of

very large block


To whom it may concern,

in view of the discussion below may I suggest we remove the --with-gc

option from the Dovecot default options?


Thanks.

Kind regards
Sebastian


Anfang der weitergeleiteten Nachricht:

Von: Sebastian Wolfgarten 
>

Datum: 25. Oktober 2015 um 11:54:15 MEZ
An: Timo Sirainen mailto:t...@iki.fi>>
Kopie: dove...@dovecot.org 
Betreff: Aw: Memory leak or misconfiguration: Repeated allocation of

very large block


Hi Timo,

alright, thanks I will recompile without gc - this is a standard

build option on FreeBSD but I will get the port maintainer to maybe
change this.


Best regards
Sebastian


Am 24.10.2015 um 23:19 schrieb Timo Sirainen 
>:


On 24 Oct 2015, at 14:59, Sebastian Wolfgarten

mailto:sebast...@wolfgarten.com>> wrote:


Dear all,

I am using Dovecot 2.2.19 and I keep on getting the following

warnings in my mail.log file on FreeBSD 10:


Oct 24 10:45:28 server1 dovecot: imap: Error: GC Warning: Repeated

allocation of very large block (appr. size 20480):

Oct 24 10:45:28 server1 dovecot: imap: Error:   May lead to memory

leak and poor performance.


I am wondering whether this is a configuration issue (i.e. a
mistake in my current config) or whether I am hitting a bug. What’s 
the

best way of figuring this one out? I tried increasing the verbosity of
the logs but it did not really provide me with further information.


I guess you have configured Dovecot --with-gc? I guess it's

possible this is a bug, but it could just as well be a false alarm. In
general I don't recommend/support --with-gc option (and I should
probably just remove it altogether). The easiest and the most usable
way of finding memory leaks is to run with valgrind (which must be 
done

without-gc):


service imap {
executable = /usr/bin/valgrind -q --show-reachable=yes

--leak-check=full /usr/libexec/dovecot/imap

}

I'm not aware of any memory leaks right now.







Have you filed a PR for the issue and/or reported this to the
mail/dovecot2 maintainer?
-BEGIN PGP SIGNATURE-

iQFHBAEBCgAxKhxKYXNvbiBVbm92aXRjaCA8amFzb24udW5vdml0Y2hAZ21haWwu
Y29tPgUCVmcNXAAKCRBv1JwwFhyqbuCBB/0Yqw6Bhecsegznzx21WxZD+aJzd9k5
8OPUT3VbTtkK33BKgozZYFzEW0+9XSdU6vK+AreuBcWAtMb34F5W6H3uqfezv0by
HvdftdIbUao1TYUhGlDL21k1PaNNPpfoDkqpTTV0eEAuM0p3ZZP3YWwWSXGzmvgu
KGZKdx3SF/oy6Ut2DHYZIj5JQVBd20wZrFtKt6/orudn12eFEfWcB9fTqQ1ESJBf
Q1Ue2zsPUQn7AcbP/UW99CdgV+BTM5rI7yZu8ohnJWj0rimSmWMWY5cqbzbBkTem
hBRdJ+KMD0SpdOHw7zGMHKN+MHLWCBl+4ZmIUxOEPbolLoljAdvbTt4i
=FN+e
-END PGP SIGNATURE-


___
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"

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

[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.
   ||org

--- Comment #3 from John Marino  ---
taking the ports@ mail list off of assignment ...

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
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: Python and SWIG support in ports?

[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
> > to "swig" if on a POSIX system:
> >
> >
> https://hg.python.org/cpython/file/v2.6.2/Lib/distutils/command/build_ext.py#l635
>
> Short-term, swig20 could provide a symlink to the versioned binary until
> a 'more correct' and permanent fix can be made.
>
> I'm not sure what to do about those ports that depend on swig30 in the
> presence of swig20 also being installed, given they don't appear to
> CONFLICT_INSTALL on each other. They both can't provide the swig
> symlink. Supporting swig in DEFAULT_VERSIONS doesn't sound right and is
> probably overkill.
>
>
Actually, fixing the swig port in this way with a symlink is not a bad idea
at all.
I've looked at multiple platforms (Linux, OS X, Windows)
and they all install a binary "swig".
Pushing an upstream fix to Python distutils just to appease FreeBSD may not
work out.

The down side of this change would be that you would not be able
to install swig1, swig2, and swig3 at the same time, but that might be OK.

--
Craig
___
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"

How do I use "USES=shebangfix"

[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 need USES=shebangfix for
'bin/appid_detector_builder.sh'


Thank you,
Avery
___
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: How do I use "USES=shebangfix"

[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 tests (stage-qa)
>
> Error: '/bin/bash' is an invalid shebang you need USES=shebangfix for
> 'bin/appid_detector_builder.sh'
>
>
> Thank you,
> Avery
>
>
The FreeBSD porter's handbook has your answer here:

https://www.freebsd.org/doc/en/books/porters-handbook/book.html#uses-shebangfix

The rest of that document is a great read and ongoing reference for all
your porting needs :)

Good luck!
-Ben


-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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: Call for Help: need script for patching ports tree, building with poudriere

[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@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Python and SWIG support in ports?

[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/m2crypto/m2crypto ).
> >
> > In the distutils that comes with Python, the swig binary is harcoded
> > to "swig" if on a POSIX system:
> >
> > 
> https://hg.python.org/cpython/file/v2.6.2/Lib/distutils/command/build_ext.py#l635
> 
> Short-term, swig20 could provide a symlink to the versioned binary until
> a 'more correct' and permanent fix can be made.
> 
> I'm not sure what to do about those ports that depend on swig30 in the
> presence of swig20 also being installed, given they don't appear to
> CONFLICT_INSTALL on each other. They both can't provide the swig
> symlink. Supporting swig in DEFAULT_VERSIONS doesn't sound right and is
> probably overkill.
> 
> 
> Actually, fixing the swig port in this way with a symlink is not a bad
> idea at all.
> I've looked at multiple platforms (Linux, OS X, Windows)
> and they all install a binary "swig".
> Pushing an upstream fix to Python distutils just to appease FreeBSD may
> not work out.
> 
> The down side of this change would be that you would not be able
> to install swig1, swig2, and swig3 at the same time, but that might be OK.
> 
> --
> Craig

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.

The root cause is technically an inadequate 'find the binary file name'
method.

We do want to keep/allow concurrent swig install support if they don't
already CONFLICT_INSTALL
___
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: Python and SWIG support in ports?

[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 'find the binary file name'
> method.
>

Probably, but pushing a change upstream to Python distutils just to appease
FreeBSD
might be hard.  Unless you want to patch the distutils in all our our
Python ports.



>
> We do want to keep/allow concurrent swig install support if they don't
> already CONFLICT_INSTALL
>

Why?
swig isn't used a lot.  It is inconvenient, but not a big deal to
install/uninstall different swig versions.

--
Craig
___
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"