Hi,
Il often notice, when upgrading a port, a notice like this :
<>
It obviously applies to the [MAKE ARGS] section of pkgtools.conf, since
section MAKE_ARGS is a list of make command line variables
So with the new convention, just taking an example from my file :
postfix*' => 'WITH_PCRE=yes W
[Looks like I'll soon be suspending my FreeBSD explorations for a time again.
So this completes my notes for the subject and related material.]
Reminder of the "long int" issue in gcc-4.9.1/gcc/config/rs6000/freebsd64.h
that gets the wrong type for L" . . . " notation for FreeBSD:
> /* rs6000.h
Hi Mike,
On Fri, Apr 10, 2015 at 5:12 AM, Mike wrote:
> Hi. I love that you have a updated version of subsonic.
>
> Subsonic is opensource as you know but also is a paid application. But since
> its OSS there is a fork of it that is the full version with all features.
> The repo for the fully fre
Hi Daniel,
Thank you for maintaining the Phalcon port.
I’m wondering do you have any plans to upgrade the port to 2.0?
All the best.
Ruud
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe,
I'm attempting a re-install of 10.1 amd, and cmake is a show stopper,
appearing to have a problem with liblzma. I re-installed liblzma, yet
cmake continues to fail. Without cmake many other things such as mysql
fail because of the dependency on cmake.
I am not sure what to do.
Any help would be
Hello.
On a lot of systems, "pkg audit" gives:
ruby-2.0.0.645,1 is vulnerable:
Ruby -- OpenSSL Hostname Verification Vulnerability
CVE: CVE-2015-1855
WWW: http://vuxml.FreeBSD.org/freebsd/d4379f59-3e9b-49eb-933b-61de4d0b0fdb.html
However the links above states "ruby20 *<* 2.0.0.645,1" is affe
