Hi
I'm regularly spammed by this mail.
Which I guess that it is due to the quartly snapshoted ports copy.
And that contains a missing patch that disables builing this port on 10.x
So am I going to be spammed until end of Q2, or is there actually a way
to get this port upgraded to the current Make
>> Building net/openmpi
build started at Fri Apr 14 08:28:00 UTC 2017
port directory: /usr/ports/net/openmpi
building for: FreeBSD 11rel0amd64-local-crayon2-job-01 11.0-RELEASE-p9
FreeBSD 11.0-RELEASE-p9 amd64
maintained by: dan...@freebsd.org
Makefile ident: $FreeBSD: head/net/openmpi/
>Makefile ident: $FreeBSD: head/net/openmpi/Makefile 437439
Builds fine for me at the same ports revision:
===>>> The following actions were performed:
Re-installation of openmpi-1.10.6_1
Re-installation of openmpi2-2.0.2_4
However, I use a custom /etc/make.conf:
# cat /et
No, with default GCC I still cannot reproduce your build
failure. Here's my build log:
http://eis.bris.ac.uk/~mexas/openmpi1-2.text
# pkg info -xd openmpi
openmpi-1.10.6_1:
slurm-wlm-16.05.9_1
gcc-5.4.0
libltdl-2.4.6
hwloc-1.11.1
openmpi2-2.0.2_4:
slurm-wlm
On 14/04/2017 09:47, Anton Shterenlikht wrote:
No, with default GCC I still cannot reproduce your build
failure. Here's my build log:
http://eis.bris.ac.uk/~mexas/openmpi1-2.text
# pkg info -xd openmpi
openmpi-1.10.6_1:
slurm-wlm-16.05.9_1
gcc-5.4.0
libltdl-2.4.6
>I don't know which ports default to MPICH. For me failed openmpi blocks
>141 ports:
>
>[00:05:53] >> [01][00:04:13] Finished build of net/openmpi: Failed:
>build
>[00:05:55] >> [01][00:04:15] Skipping build of graphics/ImageMagick:
>Dependent port net/openmpi failed
This is strange. It
Hi —
This is FreeBSD 11.0-STABLE #0 r316610.
IIRC, starting with the recent upgrade to ...
poudriere> clang --version
FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on
LLVM 4.0.0)
... audio/logitechmediaserver fails to compile (poudriere run):
gmake
On 4/14/17 6:33 PM, Willem Jan Withagen wrote:
> Hi
>
> I'm regularly spammed by this mail.
> Which I guess that it is due to the quartly snapshoted ports copy.
> And that contains a missing patch that disables builing this port on 10.x
>
> So am I going to be spammed until end of Q2, or is there
Hello,
Cloudflare deployed a bunch (74 apparently) of new f-root dns
servers, which do not permit AXFR like the other f-root instances
do.
Since our bind ports default configs suggest slaving . and arpa
from f-root this is a big problem in the cases where anycast
routing makes your requests hit
On Wed, Apr 12, 2017 at 12:06:42PM +0200, Michael Gmelin wrote:
> > On 12. Apr 2017, at 11:37, Alexey Dokuchaev wrote:
> > ...
> > Other alternative to PKG_NOCOMPRESS=1 could be PKGSUFFIX=.tbz (pkg-static
> > create -f tbz ...), will play with that as well.
>
> I don't think bzip will buy you muc
> On 14. Apr 2017, at 16:22, Alexey Dokuchaev wrote:
>
> On Wed, Apr 12, 2017 at 12:06:42PM +0200, Michael Gmelin wrote:
>>> On 12. Apr 2017, at 11:37, Alexey Dokuchaev wrote:
>>> ...
>>> Other alternative to PKG_NOCOMPRESS=1 could be PKGSUFFIX=.tbz (pkg-static
>>> create -f tbz ...), will pla
Hi,
I'm busy right now, could you open a PR so that I don't loose and forget
this ?
Le 14/04/2017 à 14:37, Thomas Steen Rasmussen a écrit :
> Hello,
>
> Cloudflare deployed a bunch (74 apparently) of new f-root dns
> servers, which do not permit AXFR like the other f-root instances
> do.
>
> Sin
On 04/14/2017 04:51 PM, Mathieu Arnold wrote:
Hi,
I'm busy right now, could you open a PR so that I don't loose and forget
this ?
Sure thing, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218656
/Thomas
___
freebsd-ports@freebsd.org mailing lis
Michael Grimm writes:
> uspoof.cpp:369:22: error: ordered comparison between pointer and zero
> ('int32_t *' (aka 'int *') and 'int')
> if (position > 0) {
> ^ ~
> 1 warning and 1 error generated.
>
> Any ideas on how to fix this?
See https://bugs.freebsd.org/bugzil
Jan Beich wrote:
> Michael Grimm writes:
>> uspoof.cpp:369:22: error: ordered comparison between pointer and zero
>> ('int32_t *' (aka 'int *') and 'int')
>>if (position > 0) {
>> ^ ~
>> 1 warning and 1 error generated.
>>
>> Any ideas on how to fix this?
>
> See h
On 2017-04-13 13:43, Rafael Henrique da Silva Faria wrote:
Hi everyone, I'm trying to compile Heimdal with LibreSSL on a server,
but there is a odd problem.
Actually, I'm updating a working server, updated the LibreSSL version,
and tried to recompile all dependent ports with "portmaster -fr
libr
# make -C /usr/ports/mail/spamassassin/ install
===> Options unchanged
===> Installing for spamassassin-3.4.1_10
===> spamassassin-3.4.1_10 depends on package: p5-Encode-Detect>=0 - found
===> spamassassin-3.4.1_10 depends on package: p5-HTML-Parser>=3.46 -
found
===> spamassassin-3.4.1_1
Thanks for the work on opencv, but PLEASE put something in UPDATING when
you make changes that impact large numbers of ports. I see opencv2 as
orphaned, so I can't stay there.
Do I reset the origin of opencv2 to opencv? Or will I need to delete all of
them and rebuild everything? Please put inform
On Thu, 13 Apr 2017, Pedro Giffuni wrote:
> I didn’t want to get into this but the problem is that as part of it's
> build/bootstrapping process, GCC historically takes system headers
> and attempts to “fix” them. I am unsure the fixes do anything at all
> nowadays but the effect is that the compil
On Sat, 15 Apr 2017 09:30:49 +1000 (AEST)
Gerald Pfeifer wrote:
> On Thu, 13 Apr 2017, Pedro Giffuni wrote:
> > I didn't want to get into this but the problem is that as part of
> > it's build/bootstrapping process, GCC historically takes system
> > headers and attempts to "fix" them. I am unsure
Alexander Kabaev kabaev at gmail.com on Sat Apr 15 00:20:40 UTC 2017
wrote:
. . .
> it was suggested multiple times that the whole fixinc step is
> ultimately harmful and serves no useful purpose and probably should be
> disabled in built packages outright. Is there a reason not to do it?
> Even R
Kevin Oberman writes:
> Thanks for the work on opencv, but PLEASE put something in UPDATING when
> you make changes that impact large numbers of ports. I see opencv2 as
> orphaned, so I can't stay there.
graphics/opencv has only 28 consumers which isn't that "large". I didn't
document the rename
On 2017-Apr-14, at 4:30 PM, Gerald Pfeifer wrote:
> On Thu, 13 Apr 2017, Pedro Giffuni wrote:
>> I didn’t want to get into this but the problem is that as part of it's
>> build/bootstrapping process, GCC historically takes system headers
>> and attempts to “fix” them. I am unsure the fixes do any
> On Apr 14, 2017, at 19:53, Mark Millard wrote:
>
> On 2017-Apr-14, at 4:30 PM, Gerald Pfeifer wrote:
>
>> On Thu, 13 Apr 2017, Pedro Giffuni wrote:
>>> I didn’t want to get into this but the problem is that as part of it's
>>> build/bootstrapping process, GCC historically takes system header
On 2017-Apr-14, at 6:54 PM, Mark Millard wrote:
> Alexander Kabaev kabaev at gmail.com on Sat Apr 15 00:20:40 UTC 2017
> wrote:
> . . .
>
>> it was suggested multiple times that the whole fixinc step is
>> ultimately harmful and serves no useful purpose and probably should be
>> disabled in buil
David Wolfskill writes:
> In case it helps someone else, I had encountered the symptoms cited in
> UPDATING entry 20170411, but the UPDATING entry didn't exist at the
> time.
>
> So I poked around, and discovered that -- in my case -- the thing that
> was apparently causing the problem was that l
On 2017-Apr-14, at 8:07 PM, Ngie Cooper (yaneurabeya) wrote:
> Is there a reason why you need ada support (that seems to be the only
> real reason for installing gcc6 vs gcc6-aux)? gcc6-aux uses a snapshot of
> gcc6 with custom options.
> Thanks!
> -Ngie
I got to lang/gcc6-aux indirectly
Am 15.04.2017 um 01:04 schrieb Kevin Oberman:
> Thanks for the work on opencv, but PLEASE put something in UPDATING when
> you make changes that impact large numbers of ports. I see opencv2 as
> orphaned, so I can't stay there.
>
> Do I reset the origin of opencv2 to opencv? Or will I need to dele
28 matches
Mail list logo
