Re: binutils 2.27 [not working for powerpc64 (and powerpc?)]

2016-09-20 Thread Bill Sorenson 
I don't have a massive amount expertise in this area but I'll look into it.
>From what I can tell this seems to only affect powerpc64.

Bill

On Tue, Sep 20, 2016 at 4:55 PM, Mark Millard  wrote:

>
> On 2016-Sep-20, at 1:59 PM, Dimitry Andric  wrote:
>
> > Has anyone succeeded in bisecting upstream binutils, to see where this
> problem was introduced?
> >
> > -Dimitry
>
> Apparently not from what I've seen in the lists. It will be a couple/few
> weeks before I again have powerpc64 or powerpc access. I've just been
> monitoring powerpc64 & powerpc things in hopes of things working once I
> have access again --or at least my knowing what to do to sidestep issues
> and what sequence to progress in from what I had in very early 2016-June
> when I lost access temporarily.
>
> May be someone will have the time & knowledge to bisect the upstream
> binutils materials. I may figure how to sometime after I get access again.
> But it is not the only FreeBSD powerpc64 (PowerMac) thing that I'd likely
> be investigating. (Example: because of problems with sprg0-value handling
> for FreeBSD vs. OpenFirmware on PowerMac powerpc64's: testing usefdt=1 mode
> for Nathan Whitehorn in hopes of future changes avoiding OpenFirmware use
> from FreeBSD. Nathan put the hooks in place for testing somewhat after I'd
> already lost access.)
>
> I wonder if the various(?) binutil port(s) that are 2.27 based now and can
> be built to target powerpc64/powerpc should be marked broken for
> powerpc64/powerpc until this is figured out. Any ports that are only for
> targeting powerpc64 or powerpc probably should not be at 2.27 at this point.
>
> I've submited a bugzilla report 212868 for devel/binutils with the text of
> the list reports that I've quoted.
>
>
> > On 20 Sep 2016, at 22:56, Mark Millard  wrote:
> >>
> >> The below forward from freebsd-pcc's list confirms that binutils 2.27
> not working for powerpc64 (& powerpc?) contexts.
> >>
> >> Note: Krzysztof Parzyszek is one of the two people that have recently
> been working on updating clang/llvm for fixing some of the issues that
> block FreeBSD from using clang for powerpc and powerpc64 for buildworld and
> buildkernel.
> >>
> >> ===
> >> Mark Millard
> >> markmi at dsl-only.net
> >>
> >> On 2016-Sep-20, at 11:19 AM, Krzysztof Parzyszek  swissmail.org> wrote:
> >>
> >>> I've had similar problems after building gcc-4.8.  After reverting
> back to binutils 2.25 and rebuilding, it worked fine.
> >>>
> >>> -Krzysztof
> >>>
> >>> On 9/9/2016 11:32 AM, Bill Sorenson wrote:
>  Everything I've built with the new binutils using either GCC 4.9, 5.4
> or
>  6.2 instantly dumps when run. This is on an Xserve G5. Is this just
> me or
>  is there something genuinely broken here?
> 
>  Thanks,
>  Bill
>
>
> ===
> Mark Millard
> markmi at dsl-only.net
>
> ___
> freebsd-toolch...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
> To unsubscribe, send any mail to "freebsd-toolchain-
> unsubscr...@freebsd.org"
>
___
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"

Problems with item delivery, n.00000342297

2016-09-20 Thread FedEx International Economy 
Dear Customer,

Courier was unable to deliver the parcel to you.
Please, open email attachment to print shipment label.

Warm regards,
Frederick Workman,
Sr. Support Agent.

___
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: binutils 2.27 [not working for powerpc64 (and powerpc?)]

2016-09-20 Thread Mark Millard 

On 2016-Sep-20, at 1:59 PM, Dimitry Andric  wrote:

> Has anyone succeeded in bisecting upstream binutils, to see where this 
> problem was introduced?
> 
> -Dimitry

Apparently not from what I've seen in the lists. It will be a couple/few weeks 
before I again have powerpc64 or powerpc access. I've just been monitoring 
powerpc64 & powerpc things in hopes of things working once I have access again 
--or at least my knowing what to do to sidestep issues and what sequence to 
progress in from what I had in very early 2016-June when I lost access 
temporarily.

May be someone will have the time & knowledge to bisect the upstream binutils 
materials. I may figure how to sometime after I get access again. But it is not 
the only FreeBSD powerpc64 (PowerMac) thing that I'd likely be investigating. 
(Example: because of problems with sprg0-value handling for FreeBSD vs. 
OpenFirmware on PowerMac powerpc64's: testing usefdt=1 mode for Nathan 
Whitehorn in hopes of future changes avoiding OpenFirmware use from FreeBSD. 
Nathan put the hooks in place for testing somewhat after I'd already lost 
access.)

I wonder if the various(?) binutil port(s) that are 2.27 based now and can be 
built to target powerpc64/powerpc should be marked broken for powerpc64/powerpc 
until this is figured out. Any ports that are only for targeting powerpc64 or 
powerpc probably should not be at 2.27 at this point.

I've submited a bugzilla report 212868 for devel/binutils with the text of the 
list reports that I've quoted.


> On 20 Sep 2016, at 22:56, Mark Millard  wrote:
>> 
>> The below forward from freebsd-pcc's list confirms that binutils 2.27 not 
>> working for powerpc64 (& powerpc?) contexts.
>> 
>> Note: Krzysztof Parzyszek is one of the two people that have recently been 
>> working on updating clang/llvm for fixing some of the issues that block 
>> FreeBSD from using clang for powerpc and powerpc64 for buildworld and 
>> buildkernel.
>> 
>> ===
>> Mark Millard
>> markmi at dsl-only.net
>> 
>> On 2016-Sep-20, at 11:19 AM, Krzysztof Parzyszek  
>> wrote:
>> 
>>> I've had similar problems after building gcc-4.8.  After reverting back to 
>>> binutils 2.25 and rebuilding, it worked fine.
>>> 
>>> -Krzysztof
>>> 
>>> On 9/9/2016 11:32 AM, Bill Sorenson wrote:
 Everything I've built with the new binutils using either GCC 4.9, 5.4 or
 6.2 instantly dumps when run. This is on an Xserve G5. Is this just me or
 is there something genuinely broken here?
 
 Thanks,
 Bill


===
Mark Millard
markmi at dsl-only.net

___
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: binutils 2.27 [not working for powerpc64 (and powerpc?)]

2016-09-20 Thread Dimitry Andric 
Has anyone succeeded in bisecting upstream binutils, to see where this problem 
was introduced?

-Dimitry

On 20 Sep 2016, at 22:56, Mark Millard  wrote:
> 
> The below forward from freebsd-pcc's list confirms that binutils 2.27 not 
> working for powerpc64 (& powerpc?) contexts.
> 
> Note: Krzysztof Parzyszek is one of the two people that have recently been 
> working on updating clang/llvm for fixing some of the issues that block 
> FreeBSD from using clang for powerpc and powerpc64 for buildworld and 
> buildkernel.
> 
> ===
> Mark Millard
> markmi at dsl-only.net
> 
> On 2016-Sep-20, at 11:19 AM, Krzysztof Parzyszek  
> wrote:
> 
>> I've had similar problems after building gcc-4.8.  After reverting back to 
>> binutils 2.25 and rebuilding, it worked fine.
>> 
>> -Krzysztof
>> 
>> On 9/9/2016 11:32 AM, Bill Sorenson wrote:
>>> Everything I've built with the new binutils using either GCC 4.9, 5.4 or
>>> 6.2 instantly dumps when run. This is on an Xserve G5. Is this just me or
>>> is there something genuinely broken here?
>>> 
>>> Thanks,
>>> Bill



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: binutils 2.27 [not working for powerpc64 (and powerpc?)]

2016-09-20 Thread Mark Millard 
The below forward from freebsd-pcc's list confirms that binutils 2.27 not 
working for powerpc64 (& powerpc?) contexts.

Note: Krzysztof Parzyszek is one of the two people that have recently been 
working on updating clang/llvm for fixing some of the issues that block FreeBSD 
from using clang for powerpc and powerpc64 for buildworld and buildkernel.

===
Mark Millard
markmi at dsl-only.net

On 2016-Sep-20, at 11:19 AM, Krzysztof Parzyszek  
wrote:

> I've had similar problems after building gcc-4.8.  After reverting back to 
> binutils 2.25 and rebuilding, it worked fine.
> 
> -Krzysztof
> 
> On 9/9/2016 11:32 AM, Bill Sorenson wrote:
>> Everything I've built with the new binutils using either GCC 4.9, 5.4 or
>> 6.2 instantly dumps when run. This is on an Xserve G5. Is this just me or
>> is there something genuinely broken here?
>> 
>> Thanks,
>> Bill

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

[CFT][CFH] Uses for PostGis

2016-09-20 Thread L.Bartoletti 

Hello,

As exposed on some postgis bugs. I propose an infrastructure framework 
for this ports.


PostGis is not compatible with all versions of PostGreSQL 
(https://trac.osgeo.org/postgis/wiki/UsersWikiPostgreSQLPostGIS). So 
postgis.mk can check if a version of postgis is already installed and 
compatible, and check if postgresql is compatible too.


What I've done:

- Create the  Uses file (Mk/Uses/postgis.mk)

- Add a default version of postgis (Mk/bsd.default-versions.mk)

- Modify all postgis Makefile. There may a problem with postgis21 which 
require a PGSQL version between 9.1 and 9.4 (Uses= pgsql:9.1+ pgsql:9.4- 
is it correct? Can we have bounded versions?)


- Modify all dependent ports (Qgis, Pgrouting)

All files can be downloaded from 
http://download.tuxfamily.org/bartcoding/postgis.tar.gz. You have 
several patch. The file all.diff contain... all patch.



Can you help me to test this framework?

Thank you in advance.

Regards,

Loïc BARTOLETTI

PS: I can't send this mail to harrison.grundy at astrodoggroup.com 
maintainer of PostGis21



___
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: FreeBSD Port: unifi5-5.0.7 -> 5.2.7

2016-09-20 Thread Kurt Jaeger 
Hi!

> Thank you form maintaining the port!
> Any plans to upgrade to the 5.2.7 version any time soon?

There's a patch at:

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

Please run-test it and comment in the PR if it works.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
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: py34-dnspython

2016-09-20 Thread Ruslan Makhmatkhanov 

Hi Kristof,

Kristof Provost wrote on 09/20/2016 19:40:

Hi,

I found I had a need for dnspython for python 3.4. The port builds only for
python 2.7 at the moment.
Attached is a patch to introduce py34-dnspython.

Regards,
Kristof


Feel free to commit it. Actually people asked about this in past, but I 
wasn't able to do that for some reason.


I'd only change port directory name to dns/py3-dnspython to not tie it 
to particular python version, but to use default python3 version (which 
is 3.4 at the moment). PYTHON_VERSION is better to replace with USES too.


Please see audio/py3-mutagen/Makefile for example.

--
Regards,
Ruslan

T.O.S. Of Reality
___
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 211764 - java/eclipse: Update to 4.6 (Eclipse Neon)

2016-09-20 Thread Michael Zhilin 
Hi,

Could you please take a look at this patch? It's patch from maintainer and
it works for me & others (see discussion).

Thank you!

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

py34-dnspython

2016-09-20 Thread Kristof Provost 
Hi,

I found I had a need for dnspython for python 3.4. The port builds only for
python 2.7 at the moment.
Attached is a patch to introduce py34-dnspython.

Regards,
Kristofdiff --git a/dns/py34-dnspython/Makefile b/dns/py34-dnspython/Makefile
new file mode 100644
index 000..19af934
--- /dev/null
+++ b/dns/py34-dnspython/Makefile
@@ -0,0 +1,7 @@
+# $FreeBSD$
+
+MASTERDIR= ${.CURDIR}/../py-dnspython
+
+PYTHON_VERSION=python3.4
+
+.include "${MASTERDIR}/Makefile"
___
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: Bug 211766 - Update www/uchiwa to 0.18.0

2016-09-20 Thread Kurt Jaeger 
Hi!

> Would it be possible for someone with a commit bit to take a look at this
> bug? No update since early September. The initial issues should be fixed
> now.

It's not fixed, but I'm testing a working solution right now.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
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: linux_base-c6 (....) on amd64 without x86_64 support

2016-09-20 Thread Tijl Coosemans 
On Tue, 20 Sep 2016 13:19:23 +0200 Matthias Apitz  wrote:
> My other poudriere oven is freebsd-r302904-ports-20160716 (r418627)
> so I will use this. What is the correct setting in make.conf for c6 x86_64?

Before r421387:

OVERRIDE_LINUX_BASE_PORT=c6_64
OVERRIDE_LINUX_NONBASE_PORTS=c6_64

After r421387:

DEFAULT_VERSIONS+=linux=c6_64

(OVERRIDE_* still works but produces a warning.)
___
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 211766 - Update www/uchiwa to 0.18.0

2016-09-20 Thread Alexander Holte-Davidsen 
Hi,

Would it be possible for someone with a commit bit to take a look at this
bug? No update since early September. The initial issues should be fixed
now.

Best regards,
Alexander
___
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: linux_base-c6 (....) on amd64 without x86_64 support

2016-09-20 Thread Matthias Apitz 
El día Tuesday, September 20, 2016 a las 11:41:21AM +0200, Tijl Coosemans 
escribió:

> > I have checked out head of ports, but it is unwilling to build it on:
> > 
> > # uname -a
> > FreeBSD c720-r292778-amd64 11.0-CURRENT FreeBSD 11.0-CURRENT #0
> > r292778: Mon Dec 28 05:45:37 CET 2015
> > root@poudriere-amd64:/usr/local/r292778/obj/usr/local/r292778/src/sys/GENERIC
> > amd64
> 
> You need at least r297602, so try a more recent 11-stable or 12-current.

This is fine. My other poudriere oven is freebsd-r302904-ports-20160716 
(r418627)
so I will use this. What is the correct setting in make.conf for c6 x86_64?

matthias
-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Ohne die Mauer hätte es Krieg gegeben" Fritz Streletz u.a.
"Sin el Muro hubiese habido guerra."
___
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"

FreeBSD Port: unifi5-5.0.7 -> 5.2.7

2016-09-20 Thread Ruud Boon 
Hi Mark,

Thank you form maintaining the port!
Any plans to upgrade to the 5.2.7 version any time soon?

Best regards,
Ruud



signature.asc
Description: Message signed with OpenPGP using GPGMail

[Bug 204515] multimedia/xmms: Doesn't show ID3v2.3 tags

2016-09-20 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204515

Christian Weisgerber  changed:

   What|Removed |Added

 CC||na...@freebsd.org
 Status|In Progress |Open

-- 
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: Patch to cmake detect OpenMP

2016-09-20 Thread Otacílio de Araújo Ramos Neto 
Em ter, 20 de set de 2016 04:04, Matthieu Volat 
escreveu:

> On Tue, 20 Sep 2016 00:55:44 -0300
> Otacílio  wrote:
>
> > I'm trying to port flann (http://www.cs.ubc.ca/research/flann/) to
> > FreeBSD, but I need that cmake detects OpenMP. Unhappy, cmake do not
> > detects OpenMP even when devel/openmp is installed,  so I did this patch
> > to cmake port. What you guys think about? Can I open a bug report with
> > patch?
> >
> > []'s
> >
>
> Hi, are you planning to submit this patch for cmake in ports or the
> upstream project?
>
> This is not a really good idea to hardcode /usr/local like that, for there
> can be may more providers for libomp (lang/clangXY ports, if you need a
> specific to workaround bugs for example... or even maybe base in the
> future?). Also, it would break cmake with GCC.
>
> Without changing any upstream code in either cmake or flann, for FreeBSD
> 11+, you can just set :
>
>   USES+=  compiler:openmp
>   CFLAGS+= -I${LOCALBASE}/include
>   LDFLAGS+= -L${LOCALBASE}/lib -lomp -lm
>
> I did not test how this behave on older release yet... And if you need to
> build cmake-based projects outside ports, here's the flags I use:
>
>  -DCMAKE_REQUIRED_INCLUDES="/usr/local/include" \
>  -DCMAKE_REQUIRED_LIBRARIES="-L/usr/local/lib -lomp -lm" \
>  -DCMAKE_EXE_LINKER_FLAGS="-L/usr/local/lib -lomp -lm" \
>  -DCMAKE_MODULE_LINKER_FLAGS="-L/usr/local/lib -lomp -lm" \
>  -DCMAKE_SHARED_LINKER_FLAGS="-L/usr/local/lib -lomp -lm"
>
> -- Matthieu Volat 
>

Hi Matthieu.

I was planning to submit this patch in ports but, after yours appointments,
I have declined from the idea. My motivation was  that if cmake proposes
find OpenMP it must find OpenMP. But, my patch is not the right procedure
to do it.

[]'s
-Otacilio

>
___
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: linux_base-c6 (....) on amd64 without x86_64 support

2016-09-20 Thread Tijl Coosemans 
On Tue, 20 Sep 2016 10:34:11 +0200 Matthias Apitz  wrote:
> El día Monday, September 19, 2016 a las 01:51:19PM +0200, Tijl Coosemans 
> escribió:
>> On Mon, 19 Sep 2016 12:50:17 +0200 Matthias Apitz  wrote:  
>>> I have compiled my ports with poudriere on amd64, based on ports r414411
>>> at the moment, and learned that the linux*c6 packages does not have
>>> x86_64 support; I recompiled as test emulators/linux_base-c6 and only if
>>> I set in /etc/make.conf:
>>> 
>>> OVERRIDE_LINUX_BASE_PORT=c6_64
>>> 
>>> the package is built as linux_base-c6_64-6.7_1.txz and has 64-bit
>>> support (and 32-bit too). Why do I have to set this extra variable
>>> OVERRIDE_LINUX_BASE_PORT?  
>> 
>> Because it is new and experimental.  I plan to enable it by default in
>> January 2017, after FreeBSD 9, 10.1 and 10.2 EoL.  
> 
> I have checked out head of ports, but it is unwilling to build it on:
> 
> # uname -a
> FreeBSD c720-r292778-amd64 11.0-CURRENT FreeBSD 11.0-CURRENT #0
> r292778: Mon Dec 28 05:45:37 CET 2015
> root@poudriere-amd64:/usr/local/r292778/obj/usr/local/r292778/src/sys/GENERIC
> amd64

You need at least r297602, so try a more recent 11-stable or 12-current.
___
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: linux_base-c6 (....) on amd64 without x86_64 support

2016-09-20 Thread Matthias Apitz 
El día Monday, September 19, 2016 a las 01:51:19PM +0200, Tijl Coosemans 
escribió:

> On Mon, 19 Sep 2016 12:50:17 +0200 Matthias Apitz  wrote:
> > I have compiled my ports with poudriere on amd64, based on ports r414411
> > at the moment, and learned that the linux*c6 packages does not have
> > x86_64 support; I recompiled as test emulators/linux_base-c6 and only if
> > I set in /etc/make.conf:
> > 
> > OVERRIDE_LINUX_BASE_PORT=c6_64
> > 
> > the package is built as linux_base-c6_64-6.7_1.txz and has 64-bit
> > support (and 32-bit too). Why do I have to set this extra variable
> > OVERRIDE_LINUX_BASE_PORT?
> 
> Because it is new and experimental.  I plan to enable it by default in
> January 2017, after FreeBSD 9, 10.1 and 10.2 EoL.

I have checked out head of ports, but it is unwilling to build it on:

# uname -a
FreeBSD c720-r292778-amd64 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r292778: Mon 
Dec 28 05:45:37 CET 2015 
root@poudriere-amd64:/usr/local/r292778/obj/usr/local/r292778/src/sys/GENERIC  
amd64


# svn info
Path: .
Working Copy Root Path: /usr/home/guru/ports
URL: svn://svn.freebsd.org/ports/head/emulators/linux_base-c6
Relative URL: ^/head/emulators/linux_base-c6
Repository Root: svn://svn.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 422483
Node Kind: directory
Schedule: normal
Last Changed Author: tijl
Last Changed Rev: 421387
Last Changed Date: 2016-09-05 21:23:42 +0200 (Mon, 05 Sep 2016)

# make
===>  linux_base-c6-6.8_1 Linux c6_64 only supported on FreeBSD/amd64 10.3
or higher.
*** Error code 1

What do I miss?

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Ohne die Mauer hätte es Krieg gegeben" Fritz Streletz u.a.
"Sin el Muro hubiese habido guerra."
___
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"

FreeBSD ports you maintain which are out of date

2016-09-20 Thread portscout 
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 can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
benchmarks/flowgrind| 0.7.5   | 
flowgrind-0.8.0
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
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: Problems with fetching from GitHub using GH_TAGNAME= hash

2016-09-20 Thread Mathieu Arnold 
Le 18/09/2016 à 07:40, Kevin Oberman a écrit :
> I an attempting to write a port for multimedia/mp4vs which has moved from
> Google Code to GitHub. I tried specifying GH_TAGNAME= 6fda22f, but instead
> of fetching mp4v2-Release-MP4v2-3.0.1.1.tar.gz, it tries to fetch
> mp4v2-Release-MP4v2-3.0.1.1_GH0.tar.gz. (Note added "_GH0".)
> I have no idea where this is coming from an have no experience with porting
> where GitHub is the distfile repo.

The framework adds _GH0 so that when (not if) github updates their
download scheme again, we can bump it to _GH1 and not have everything
conflicting.

> My Makefile contains:
> USE_GITHUB= yes
> GH_ACCOUNT= TechSmith
> GH_PROJECT= mp4v2
> GH_TAGNAME= 6fda22f
>
> Any idea what I need to change?

You can remove the GH_PROJECT line, it should be the default.

-- 
Mathieu Arnold




signature.asc
Description: OpenPGP digital signature

Re: Patch to cmake detect OpenMP

2016-09-20 Thread Matthieu Volat 
On Tue, 20 Sep 2016 00:55:44 -0300
Otacílio  wrote:

> I'm trying to port flann (http://www.cs.ubc.ca/research/flann/) to 
> FreeBSD, but I need that cmake detects OpenMP. Unhappy, cmake do not 
> detects OpenMP even when devel/openmp is installed,  so I did this patch 
> to cmake port. What you guys think about? Can I open a bug report with 
> patch?
> 
> []'s
> 

Hi, are you planning to submit this patch for cmake in ports or the upstream 
project?

This is not a really good idea to hardcode /usr/local like that, for there can 
be may more providers for libomp (lang/clangXY ports, if you need a specific to 
workaround bugs for example... or even maybe base in the future?). Also, it 
would break cmake with GCC.

Without changing any upstream code in either cmake or flann, for FreeBSD 11+, 
you can just set :

  USES+=  compiler:openmp 
  CFLAGS+= -I${LOCALBASE}/include
  LDFLAGS+= -L${LOCALBASE}/lib -lomp -lm

I did not test how this behave on older release yet... And if you need to build 
cmake-based projects outside ports, here's the flags I use:

 -DCMAKE_REQUIRED_INCLUDES="/usr/local/include" \
 -DCMAKE_REQUIRED_LIBRARIES="-L/usr/local/lib -lomp -lm" \
 -DCMAKE_EXE_LINKER_FLAGS="-L/usr/local/lib -lomp -lm" \
 -DCMAKE_MODULE_LINKER_FLAGS="-L/usr/local/lib -lomp -lm" \
 -DCMAKE_SHARED_LINKER_FLAGS="-L/usr/local/lib -lomp -lm"

-- Matthieu Volat 


pgpPnOxTm0Xcz.pgp
Description: OpenPGP digital signature