On 12/12/2016 13:12, Janky Jay, III wrote:
Hello scratch,
On 12/11/2016 03:35 PM, scratch65...@att.net wrote:
I have to admit that I avoid ports if at all possible because
I've hardly ever been able to do a build that ran to completion.
There's always some piece of code that's missing and
On 12/12/2016 02:42, Janky Jay, III wrote:
Hello scratch,
On 12/11/2016 03:35 PM, scratch65...@att.net wrote:
I have to admit that I avoid ports if at all possible because
I've hardly ever been able to do a build that ran to completion.
There's always some piece of code that's missing and
Hi Vlad,
On 12/11/2016 07:58 PM, Vlad K. wrote:
> On 2016-12-12 03:42, Janky Jay, III wrote:
>> This very, VERY rarely happens to me and I use ports *ONLY* in
>> production environments. If you could please provide examples and report
>> the issues to the port maintainer of the ports with
Hello scratch,
On 12/11/2016 03:35 PM, scratch65...@att.net wrote:
> I have to admit that I avoid ports if at all possible because
> I've hardly ever been able to do a build that ran to completion.
> There's always some piece of code that's missing and can't be
> found, or is the wrong version,
On 2016-Dec-11, at 3:11 PM, Mark Linimon wrote:
> On Sun, Dec 11, 2016 at 02:59:36PM -0800, Mark Millard wrote:
>> I tend to have powerpc64 and powerpc patches because of my
>> experimenting with clang targeting them and that the standard
>> powerpc64 build does not boot PowerMac G5's reliably.
On Sun, Dec 11, 2016 at 02:59:36PM -0800, Mark Millard wrote:
> I tend to have powerpc64 and powerpc patches because of my
> experimenting with clang targeting them and that the standard
> powerpc64 build does not boot PowerMac G5's reliably.
Is that on 10, 11 or -current?
On 10 I remember being
[After "BUILD_DEPENDS+= gcc6:lang/gcc6" below shows that
portmaster does not do what you indicate the build environment
should do. The beginning is not essential material.]
On 2016-Dec-11, at 4:40 AM, Gerald Pfeifer wrote:
> On Sun, 11 Dec 2016, Mark Millard wrote:
>> I reported already that
I have to admit that I avoid ports if at all possible because
I've hardly ever been able to do a build that ran to completion.
There's always some piece of code that's missing and can't be
found, or is the wrong version, et lengthy cetera. I've never
done release engineering, but I honestly
On Tue, Nov 29, 2016 at 9:28 PM, Fernando Apesteguía
wrote:
> El 29 nov. 2016 18:58, "Rainer Hurling" escribió:
>>
>> Hi Fernando,
>>
>> Am 29.11.2016 um 17:50 schrieb Fernando Apesteguía:
>> > I maintain a port written mostly in C++ (cad/openvsp).
On Sun, 11 Dec 2016, Mark Millard wrote:
> I reported already that devel/kBuild/Makefile has in its
> Makefile:
>
> USE_GCC= any
>
> and devel/kBuild is what causes the lang/gcc* build. (I
> reported more than that but it is the part relevant here.)
I had read that, and I di investigate.
On 2016-Dec-11, at 1:39 AM, Gerald Pfeifer wrote:
> Hi Mark,
>
> On Sat, 10 Dec 2016, Mark Millard wrote:
>> [Top post of example lack of lang/gcc6-devel vs. lan/gcc6
>> substitutability. Context /usr/ports/ at -r428325 (other
>> than a few specially controlled items.]
>
> I had another look,
> On 9 Dec 2016, at 11:51 AM, Dmitry Sivachenko wrote:
>
> If they reject it and refuse to support libressl for some reason, we will not
> add your patches too, because this is not something FreeBSD-specific.
Strongswan developers said similar things. Unfortunately,
we
12 matches
Mail list logo