Re: dns/bind-tools fails to build on 10-stable

On 20/01/2014 20:26, John wrote: > On Mon, Jan 20, 2014 at 07:14:04PM +0100, Niclas Zeising wrote: >> On 01/20/14 10:29, John wrote: >>> Hello list, >>> >>> On a new 10-stable system, I can't seem to build bind tools. I get the >>> following >>> error: >>> >>> checking host system type... x86_64-

Re: per-port make.conf options and hyphenated port names

On Tue, Jan 21, 2014 at 3:36 AM, Volodymyr Kostyrko wrote: > 21.01.2014 03:01, Matthew Pounsett wrote: >> >> >> At some point in the last couple of weeks I was pointed at >> as what has been >> implemented to deprecate make.conf settings such as “

Why is audio/pulseaudio so far behind current version?

Why is audio/pulseaudio, at 0.9.23, so far behind the current version, 4.0? NetBSD pkgsrc is at version 2.1. Might there be something compatible with Linux but not FreeBSD? It sticks out annoyingly when I get all those error messages spewed out on the console and captured in /var/log/messages.

Re: postfix-current spewing out warnings while building

On Thu, 2014-01-09 at 10:47:39 +0100, Jakob Breivik Grimstveit wrote: > Thank you for the explanatory reply. Much appreciated. I've tried, however, > patching mail/postfix (not lang/postfix), but I get the following erroneous > output: > > # pwd > /usr/ports/mail/postfix > # patch < postfix-also-

Re: Fwd: [thunderbird-24.1.0] FreeBSD 10-i386 jail at 11-amd64 host: Error while running startup cache precompilation

On 26/11/13 10:42 PM, Cy Schubert wrote: In message <5272af33.7030...@smeets.im>, Florian Smeets writes: This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --LjCOVwNOW3aPxiaJSC0KaksgOOBQirtv3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 31/10/13

net/avahi-app core dumps signal 11

Hello, avahi-daemon dumps core, and I am unable to determinw why because it aborts core just before reaching the main() procedure.. = #0 0x000801304604 in pthread_testcancel () from /lib/libthr.so.3 #1 0x0008012fc706 in open () fr

Re: How to determine type of system compiler in port?

On 22/01/2014 09:15, Lev Serebryakov wrote: > Hello, Ports. > > I want to turn off some clang-specific warnings via CFLAGS, as I'm not > able to patch all places when "dirty" (but valid!) code is used and upstream > software uses "-Werror"... > > I could not find any mentions of "clang" in bs

Re: How to determine type of system compiler in port?

On Wed, Jan 22, 2014 at 12:45 AM, Lev Serebryakov wrote: > Hello, Ports. > > I want to turn off some clang-specific warnings via CFLAGS, as I'm not > able to patch all places when "dirty" (but valid!) code is used and > upstream > software uses "-Werror"... > Using of a -Werror in a release bu

Re: USE_GCC doesn't set rpath

On 22/01/2014 08:04, Yuri wrote: > Current port net-p2p/libtorrent-rasterbar has > USES=compiler:c++11-lib which in turn sets USE_GCC=4.7+ Maintainer of > lang/gccNN says that USE_GCC is supposed to automatically set rpath > to this particular gcc shared library. However, this doesn't happen, > and

Re: How to determine type of system compiler in port?

On, Tue Jan 21, 2014, Lev Serebryakov wrote: > Hello, Ports. > > I want to turn off some clang-specific warnings via CFLAGS, as I'm not > able to patch all places when "dirty" (but valid!) code is used and upstream > software uses "-Werror"... > > I could not find any mentions of "clang" in bs

How to determine type of system compiler in port?

Hello, Ports. I want to turn off some clang-specific warnings via CFLAGS, as I'm not able to patch all places when "dirty" (but valid!) code is used and upstream software uses "-Werror"... I could not find any mentions of "clang" in bsd.port.mk and COMPILER_TYPE is not defined for ports.

USE_GCC doesn't set rpath

Current port net-p2p/libtorrent-rasterbar has USES=compiler:c++11-lib which in turn sets USE_GCC=4.7+ Maintainer of lang/gccNN says that USE_GCC is supposed to automatically set rpath to this particular gcc shared library. However, this doesn't happen, and qbittorrent fails as a result on 9.2: $

Re: FreeBSD Port: pecl-svn-1.0.2

At 21. 01. 2014 12:52, Sossi Andrej wrote: Hi, I have installed a new web server into the jail virtual machine. When I try to use the function svn_ls this cause a Segmentation fault. [...] I found the error. On my SVN server I use LDAP authentication. When I configured 'subversion16' port I

Re: Staging support, man pages, MANx and portlint

On Tue, Jan 21, 2014 at 10:37:17PM +0400, Lev Serebryakov wrote: > Hello, Baptiste. > You wrote 21 января 2014 г., 22:30:15: > > > >> LS> How could I turn on gizpping of man pages in such case? > >> Set MNAPREFIX > BD> MANDIRS+= ${PREFIX}/path/to/your/man > Is it better than setting MANP

remmina-plugin-rdp seems to be broken after last update

[I first tried to send this to po...@logvinov.com, but it bounced with a "no such user" message] Hello, I've just used portmaster to update freerdp & the remmina ports on my 9.2-STABLE r260910 system, and I can no longer make RDP connections to Windows boxes. If I run remmina from the command li

Re: Staging support, man pages, MANx and portlint

Hello, Baptiste. You wrote 21 января 2014 г., 22:30:15: >> LS> How could I turn on gizpping of man pages in such case? >> Set MNAPREFIX BD> MANDIRS+= ${PREFIX}/path/to/your/man Is it better than setting MANPREFIX? -- // Black Lion AKA Lev Serebryakov _

Re: Staging support, man pages, MANx and portlint

On Tue, Jan 21, 2014 at 07:46:08PM +0400, Lev Serebryakov wrote: > Hello, Lev. > You wrote 21 января 2014 г., 19:06:47: > > LS> How could I turn on gizpping of man pages in such case? > Set MNAPREFIX > > > > -- > // Black Lion AKA Lev Serebryakov > > ___

Re: Staging support, man pages, MANx and portlint

Hello, John. You wrote 21 января 2014 г., 21:48:54: JM> Why are you using a non-standard path for man pages? JM> You can using the post-install target to move them to their expected JM> location if the port installs them in the wrong place. Because I try to mimic upstream package as close as pos

Re: Staging support, man pages, MANx and portlint

On 1/21/2014 16:06, Lev Serebryakov wrote: > Hello, Ports. > > Wiki on Stage dir support says, that if port supports staging, MANx > variables in Makefile is useless and I need simply list all man pages in > pkg-plist and they will be gzipped automagically. > > portlint -A says, that I need to

Re: per-port make.conf options and hyphenated port names

On Jan 21, 2014, at 04:36 , Volodymyr Kostyrko wrote: > 21.01.2014 03:01, Matthew Pounsett wrote: >> >> Digging through /usr/ports/Mk/ I can’t find anywhere that $UNIQUENAME is >> modified to guarantee that it references a safe variable name (i.e. I don’t >> see anywhere that $UNIQUENAME has

Maintainer timeout to fix 4 ports on 10.0?

In December, I fixed a few ports to compile on 10.0: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/185032 submitted: 2013-12-20 (mail to maintainer: 2013-12-06) http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/185033 submitted: 2013-12-20 (mail to maintainer: 2013-12-06) http://www.freebsd.or

NOPORTDOCS doesn't cancel INFO installation

Hello, Ports. Is it by design or INFO was overlooked by stage support? -- // Black Lion AKA Lev Serebryakov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-

Re: Staging support, man pages, MANx and portlint

Hello, Lev. You wrote 21 января 2014 г., 19:06:47: LS> How could I turn on gizpping of man pages in such case? Set MNAPREFIX -- // Black Lion AKA Lev Serebryakov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo

Staging support, man pages, MANx and portlint

Hello, Ports. Wiki on Stage dir support says, that if port supports staging, MANx variables in Makefile is useless and I need simply list all man pages in pkg-plist and they will be gzipped automagically. portlint -A says, that I need to list all man pages as gzipped (xxx.1.gz, not xxx.1). Bu

Re: Blanket approval to modernize the Ports Tree

FreeBSD Ports Management Team Secretary wrote: > In years gone by, and I am thinking of FreeBSD 7.0 specifically, portmgr@ > gave some latitude to *ALL* committers to "just fix things" to get a port > into shape. In the case of 7.0, it was making ports build for gcc4. > > What we have laying ah

FreeBSD Port: pecl-svn-1.0.2

Hi, I have installed a new web server into the jail virtual machine. When I try to use the function svn_ls this cause a Segmentation fault. At first time I have used apache httpd24 and php55. For test I have deinstalled php55 and pecl-svn then I have reinstalled php53 and I have (recompiled an

Re: per-port make.conf options and hyphenated port names

21.01.2014 03:01, Matthew Pounsett wrote: At some point in the last couple of weeks I was pointed at as what has been implemented to deprecate make.conf settings such as “WITHOUT_X11=yes”. That document says it has been committed, but the p

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

www.freebsd.org

Hi, I just wanted to send you a quick note. With a few simple changes to make your site more SEO-friendly I’m sure you can convert more visitors into leads and get it placed higher in the organic search results, for keywords that matter to you the most. We are an Australian based company with a

FreeBSD ports which are currently marked forbidden

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as "forbidden" in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, inclu

FreeBSD unmaintained ports which are currently scheduled for deletion

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on th

FreeBSD ports which are currently scheduled for deletion

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on th

FreeBSD ports which are currently marked broken

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common probl

FreeBSD unmaintained ports which are currently marked broken

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common probl