Re: 4 new p5- ports

2017-10-02 Thread Stuart Henderson
On 2017/10/02 14:19, wen heping wrote:
> Hi,
> 
> 
> Here I attach a file which include 4 new p5- ports. These ports
> 
> should be keeped in devel category and are required by the future
> 
> update of devel/p5-Moose.
> 
>It all build and test well on my amd64 machine.
> 
>Any comments ? OK ?
> 
> 
> 
> Regards,
> 
> wen

We are in lock for 6.2. Also there is a bogus PKG_ARCH=* in there.



Re: [wip] Firefox 57.0b4

2017-10-02 Thread David CARLIER
>From source with base from 2/3 days ago, works just fine since couple of
hours doing youtube and other javascript consumers ... smoothly.

On 2 October 2017 at 13:31, Landry Breuil  wrote:

> Hi,
>
> of course not targeted for the upcoming 6.2 release, but firefox 57 will
> be quite a big change from 56, so testing is more than welcome.
>
> https://www.mozilla.org/en-US/firefox/57.0beta/releasenotes/
> https://www.mozilla.org/en-US/firefox/quantum/
> https://hacks.mozilla.org/2017/09/firefox-quantum-
> developer-edition-fastest-firefox-ever/
>
> etc etc - to note: non-webextensions addons (which are labelled
> 'legacy' in about:addons) will stop working with this version, you've
> been warned. A separate content process should be enabled by default,
> and thanks to semarie@'s help we managed to build and enable the new
> 'stylo' css rendering engine, written in rust.
>
> So as usual, pull/update/rebuild from
> https://cgit.rhaalovely.net/mozilla-firefox/log/?h=beta
>
> Or try the packages from https://packages.rhaalovely.net/
>
> Landry
>
>


4 new p5- ports

2017-10-02 Thread wen heping
Hi,


Here I attach a file which include 4 new p5- ports. These ports

should be keeped in devel category and are required by the future

update of devel/p5-Moose.

   It all build and test well on my amd64 machine.

   Any comments ? OK ?



Regards,

wen


Moose2006.tar.gz
Description: Moose2006.tar.gz


Re: linking error when compiling zdoom

2017-10-02 Thread Timo Myyrä
David Coppa  writes:

> On Mon, Oct 2, 2017 at 8:17 AM, Timo Myyrä  wrote:
>
>> Hi,
>>
>> I'm trying to make port of zdoom but I can't get it to link.
>>
>> The error I got was:
>> CMakeFiles/zdoom.dir/scripting/vm/vmexec.cpp.o: In function 
>> `__cxx_global_var_init':
>> /home/tmy/tmp/gzdoom-g3.1.0/src/scripting/vm/vmexec.cpp:(.text+0x42): 
>> undefined reference to `__cxa_thread_atexit'
>> c++: error: linker command failed with exit code 1 (use -v to see invocation)
>> *** Error 1 in . (src/CMakeFiles/zdoom.dir/build.make:10917 'gzdoom')
>>
>> I got a bit of help in this and added following to Makefile:
>> CONFIGURE_ARGS+= -DCMAKE_EXE_LINKER_FLAGS="-lc++abi"
>>
>> That changed the above linking error to:
>> usr/bin/../lib/libc++abi.so.0.0: undefined reference to 
>> `pthread_rwlock_rdlock'
>> /usr/bin/../lib/libc++abi.so.0.0: undefined reference to 
>> `pthread_rwlock_unlock'
>> /usr/bin/../lib/libc++abi.so.0.0: undefined reference to 
>> `pthread_rwlock_wrlock'
>>
>>
>> I tried to change CONFIGURE_ARGS as follows:
>> CONFIGURE_ARGS+= -DCMAKE_EXE_LINKER_FLAGS="-lpthread -lc++abi"
>>
>> After compiling the linking failed with "undefined reference to
>> `__cxa_thread_atexit'" which seems odd as it should be in the c++abi library.
>>
>> Any idea whats going on?
>
> Unfortunately, our libc lacks __cxa_thread_atexit().
> It is required for C++ TLS, for registering cleanups to be run when a
> thread exits.
>
> Mark Kettenis posted a diff on tech@ some time ago[1] but, afaik, it
> has not yet been committed.
>
> [1] https://marc.info/?l=openbsd-tech&m=150246192013629
>
> Ciao!
> David

Well that explains the problems then. I'll look out for TLS support to land
then. Rooting for 6.3.

Timo



Re: linking error when compiling zdoom

2017-10-02 Thread David Coppa
On Mon, Oct 2, 2017 at 8:17 AM, Timo Myyrä  wrote:
> Hi,
>
> I'm trying to make port of zdoom but I can't get it to link.
>
> The error I got was:
> CMakeFiles/zdoom.dir/scripting/vm/vmexec.cpp.o: In function 
> `__cxx_global_var_init':
> /home/tmy/tmp/gzdoom-g3.1.0/src/scripting/vm/vmexec.cpp:(.text+0x42): 
> undefined reference to `__cxa_thread_atexit'
> c++: error: linker command failed with exit code 1 (use -v to see invocation)
> *** Error 1 in . (src/CMakeFiles/zdoom.dir/build.make:10917 'gzdoom')
>
> I got a bit of help in this and added following to Makefile:
> CONFIGURE_ARGS+= -DCMAKE_EXE_LINKER_FLAGS="-lc++abi"
>
> That changed the above linking error to:
> usr/bin/../lib/libc++abi.so.0.0: undefined reference to 
> `pthread_rwlock_rdlock'
> /usr/bin/../lib/libc++abi.so.0.0: undefined reference to 
> `pthread_rwlock_unlock'
> /usr/bin/../lib/libc++abi.so.0.0: undefined reference to 
> `pthread_rwlock_wrlock'
>
>
> I tried to change CONFIGURE_ARGS as follows:
> CONFIGURE_ARGS+= -DCMAKE_EXE_LINKER_FLAGS="-lpthread -lc++abi"
>
> After compiling the linking failed with "undefined reference to
> `__cxa_thread_atexit'" which seems odd as it should be in the c++abi library.
>
> Any idea whats going on?

Unfortunately, our libc lacks __cxa_thread_atexit().
It is required for C++ TLS, for registering cleanups to be run when a
thread exits.

Mark Kettenis posted a diff on tech@ some time ago[1] but, afaik, it
has not yet been committed.

[1] https://marc.info/?l=openbsd-tech&m=150246192013629

Ciao!
David



Re: [UPDATE] www/sblg to 0.4.6

2017-10-02 Thread Bryan Vyhmeister
On Mon, Oct 02, 2017 at 09:19:07PM +0100, Stuart Henderson wrote:
> On 2017/10/02 13:07, Bryan Vyhmeister wrote:
> > This is another simple update of sblg from 0.4.5 to 0.4.6. Not sure if
> > this can make 6.2 but perhaps it could.
> 
> Much too late for 6.2.

No problem. When the lock is over it's ready.

Bryan



Re: [UPDATE] www/sblg to 0.4.6

2017-10-02 Thread Stuart Henderson
On 2017/10/02 13:07, Bryan Vyhmeister wrote:
> This is another simple update of sblg from 0.4.5 to 0.4.6. Not sure if
> this can make 6.2 but perhaps it could.

Much too late for 6.2.



Re: [UPDATE] www/sblg to 0.4.6

2017-10-02 Thread Bryan Vyhmeister
On Mon, Oct 02, 2017 at 01:07:35PM -0700, Bryan Vyhmeister wrote:
> This is another simple update of sblg from 0.4.5 to 0.4.6. Not sure if
> this can make 6.2 but perhaps it could. The changes listed by the author
> are:
> 
> "Allow for data-sblg-navsort attribute to override the search order set
> by -s. Also add the rdate search order (reverse date)"
> 
> I did testing on amd64 with no issues. I expect it should work fine
> everywhere. CC maintainer also.

It would help if I included the diff.

Bryan


Index: www/sblg/Makefile
===
RCS file: /cvs/ports/www/sblg/Makefile,v
retrieving revision 1.8
diff -u -p -u -r1.8 Makefile
--- www/sblg/Makefile   25 Jul 2017 06:44:45 -  1.8
+++ www/sblg/Makefile   2 Oct 2017 20:09:32 -
@@ -2,7 +2,7 @@
 
 COMMENT =  simple off-line blog utility
 
-DISTNAME = sblg-0.4.5
+DISTNAME = sblg-0.4.6
 
 CATEGORIES =   www
 
Index: www/sblg/distinfo
===
RCS file: /cvs/ports/www/sblg/distinfo,v
retrieving revision 1.8
diff -u -p -u -r1.8 distinfo
--- www/sblg/distinfo   25 Jul 2017 06:44:45 -  1.8
+++ www/sblg/distinfo   2 Oct 2017 20:09:32 -
@@ -1,2 +1,2 @@
-SHA256 (sblg-0.4.5.tar.gz) = BoNNhKqQFvA7dS5EQmeo0yCpKFXrJrUFgwNU95mI5TA=
-SIZE (sblg-0.4.5.tar.gz) = 50385
+SHA256 (sblg-0.4.6.tar.gz) = +Vu/PFpC/pPRAPn5WzfXE4pfpKWXoLJvJZhw/04aeg0=
+SIZE (sblg-0.4.6.tar.gz) = 50768



[UPDATE] www/sblg to 0.4.6

2017-10-02 Thread Bryan Vyhmeister
This is another simple update of sblg from 0.4.5 to 0.4.6. Not sure if
this can make 6.2 but perhaps it could. The changes listed by the author
are:

"Allow for data-sblg-navsort attribute to override the search order set
by -s. Also add the rdate search order (reverse date)"

I did testing on amd64 with no issues. I expect it should work fine
everywhere. CC maintainer also.
 
Bryan



Re: [wip] Firefox 57.0b4

2017-10-02 Thread Jiri B
On Mon, Oct 02, 2017 at 02:31:49PM +0200, Landry Breuil wrote:
> Hi,
> 
> of course not targeted for the upcoming 6.2 release, but firefox 57 will
> be quite a big change from 56, so testing is more than welcome.
> 
> https://www.mozilla.org/en-US/firefox/57.0beta/releasenotes/
> https://www.mozilla.org/en-US/firefox/quantum/
> https://hacks.mozilla.org/2017/09/firefox-quantum-developer-edition-fastest-firefox-ever/
> 
> etc etc - to note: non-webextensions addons (which are labelled
> 'legacy' in about:addons) will stop working with this version, you've
> been warned. A separate content process should be enabled by default,
> and thanks to semarie@'s help we managed to build and enable the new
> 'stylo' css rendering engine, written in rust.
> 
> So as usual, pull/update/rebuild from
> https://cgit.rhaalovely.net/mozilla-firefox/log/?h=beta
> 
> Or try the packages from https://packages.rhaalovely.net/
> 
> Landry

Wow, I can't now use silly bluejeans.com webrtc conference in
Firefox! Great work, thank you very much. It will decrease rebooting
my laptop to Linux now :-)

Jiri



Re: [security] libidn & libidn2 fixes for CVE-2017-14061 and CVE-2017-14062

2017-10-02 Thread Jeremie Courreges-Anglas
On Mon, Oct 02 2017, Christian Weisgerber  wrote:
> On 2017-10-01, Jeremie Courreges-Anglas  wrote:
>
>> --- /dev/null1 Jan 1970 00:00:00 -
>> +++ devel/libidn/patches/patch-lib_punycode_c1 Oct 2017 22:06:28 
>> -
>> @@ -0,0 +1,27 @@
>> +$OpenBSD$
>> +
>> +commit e9e81b8063b095b02cf104bb992fa9bf9515b9d8
>> +Author: Tim Rühsen 
>> +Date:   Fri Sep 1 10:04:48 2017 +0200
>> +
>> +lib/punycode.c (decode_digit): Fix integer overflow
>> +
>> +This fix is a backport from libidn2 and addresses
>> +CVE-2017-14062.
>> +
>> +Index: lib/punycode.c
>> +--- lib/punycode.c.orig
>>  lib/punycode.c
>> +@@ -88,10 +88,10 @@ enum
>> + /* point (for use in representing integers) in the range 0 to */
>> + /* base-1, or base if cp does not represent a value.  */
>> + 
>> +-static punycode_uint
>> ++static unsigned
>> + decode_digit (punycode_uint cp)
>> + {
>> +-  return cp - 48 < 10 ? cp - 22 : cp - 65 < 26 ? cp - 65 :
>> ++  return (unsigned) cp - 48 < 10 ? cp - 22 : cp - 65 < 26 ? cp - 65 :
>> + cp - 97 < 26 ? cp - 97 : base;
>> + }
>> + 
>
> This is twice wrong.  It's different from the actual change in the
> referenced commit, and both are different from the libidn2 change.

Right, I propabbly applied it by hand (never a good idea...) and missed
the parameter type change, sorry about that.

The difference between libidn and libidn2 looks suspicious indeed.  I'll
try to have a closer look.


Index: devel/libidn/Makefile
===
RCS file: /d/cvs/ports/devel/libidn/Makefile,v
retrieving revision 1.31
diff -u -p -r1.31 Makefile
--- devel/libidn/Makefile   30 Jul 2016 14:22:43 -  1.31
+++ devel/libidn/Makefile   2 Oct 2017 14:57:10 -
@@ -3,6 +3,7 @@
 COMMENT=   internationalized string handling
 
 DISTNAME=  libidn-1.33
+REVISION=  0
 
 SHARED_LIBS +=  idn  17.2 # 17.16
 
@@ -29,5 +30,9 @@ CONFIGURE_ARGS=   --disable-csharp \
 
 post-extract:
rm ${WRKSRC}/contrib/doxygen/*.orig
+
+# hack to avoid regenerating docs
+post-patch:
+   touch -r ${WRKSRC}/lib/punycode.c${PATCHORIG} ${WRKSRC}/lib/punycode.c
 
 .include 
Index: devel/libidn/patches/patch-lib_punycode_c
===
RCS file: devel/libidn/patches/patch-lib_punycode_c
diff -N devel/libidn/patches/patch-lib_punycode_c
--- /dev/null   1 Jan 1970 00:00:00 -
+++ devel/libidn/patches/patch-lib_punycode_c   2 Oct 2017 14:57:48 -
@@ -0,0 +1,28 @@
+$OpenBSD$
+
+commit e9e81b8063b095b02cf104bb992fa9bf9515b9d8
+Author: Tim Rühsen 
+Date:   Fri Sep 1 10:04:48 2017 +0200
+
+lib/punycode.c (decode_digit): Fix integer overflow
+
+This fix is a backport from libidn2 and addresses
+CVE-2017-14062.
+
+Index: lib/punycode.c
+--- lib/punycode.c.orig
 lib/punycode.c
+@@ -88,10 +88,10 @@ enum
+ /* point (for use in representing integers) in the range 0 to */
+ /* base-1, or base if cp does not represent a value.  */
+ 
+-static punycode_uint
+-decode_digit (punycode_uint cp)
++static unsigned
++decode_digit (int cp)
+ {
+-  return cp - 48 < 10 ? cp - 22 : cp - 65 < 26 ? cp - 65 :
++  return (unsigned) cp - 48 < 10 ? cp - 22 : cp - 65 < 26 ? cp - 65 :
+ cp - 97 < 26 ? cp - 97 : base;
+ }
+ 
Index: devel/libidn2/Makefile
===
RCS file: /d/cvs/ports/devel/libidn2/Makefile,v
retrieving revision 1.2
diff -u -p -r1.2 Makefile
--- devel/libidn2/Makefile  18 Apr 2017 21:22:57 -  1.2
+++ devel/libidn2/Makefile  1 Oct 2017 22:06:28 -
@@ -3,6 +3,7 @@
 COMMENT=   implementation of IDNA2008 internationalized domain names
 
 DISTNAME=  libidn2-2.0.0
+REVISION=  0
 CATEGORIES=devel
 HOMEPAGE=  https://www.gnu.org/software/libidn/\#libidn2
 
Index: devel/libidn2/patches/patch-lib_bidi_c
===
RCS file: devel/libidn2/patches/patch-lib_bidi_c
diff -N devel/libidn2/patches/patch-lib_bidi_c
--- /dev/null   1 Jan 1970 00:00:00 -
+++ devel/libidn2/patches/patch-lib_bidi_c  1 Oct 2017 22:06:28 -
@@ -0,0 +1,30 @@
+$OpenBSD$
+
+Fix for CVE-2017-14061
+
+commit 16853b6973a1e72fee2b7cccda85472cb9951305
+Author: Tim Rühsen 
+Date:   Tue Aug 1 11:15:10 2017 +0200
+
+lib/bidi: Fix integer overflow (found by fuzzing)
+
+Index: lib/bidi.c
+--- lib/bidi.c.orig
 lib/bidi.c
+@@ -30,6 +30,7 @@
+ 
+ #include "idn2.h"
+ 
++#include 
+ #include 
+ 
+ #include "bidi.h"
+@@ -39,7 +40,7 @@
+ static bool
+ _isBidi (const uint32_t *label, size_t llen)
+ {
+-  while (llen-- > 0) {
++  for (; (ssize_t) llen > 0; llen--) {
+ int bc = uc_bidi_category (*label++);
+ 
+ if (bc == UC_BIDI_R || bc == UC_BIDI_AL || bc == UC_BIDI_AN)
Index: devel/libidn2/patches/patch-lib_punycode_c
===
RCS file:

Re: [security] libidn & libidn2 fixes for CVE-2017-14061 and CVE-2017-14062

2017-10-02 Thread Christian Weisgerber
On 2017-10-01, Jeremie Courreges-Anglas  wrote:

> --- /dev/null 1 Jan 1970 00:00:00 -
> +++ devel/libidn/patches/patch-lib_punycode_c 1 Oct 2017 22:06:28 -
> @@ -0,0 +1,27 @@
> +$OpenBSD$
> +
> +commit e9e81b8063b095b02cf104bb992fa9bf9515b9d8
> +Author: Tim Rühsen 
> +Date:   Fri Sep 1 10:04:48 2017 +0200
> +
> +lib/punycode.c (decode_digit): Fix integer overflow
> +
> +This fix is a backport from libidn2 and addresses
> +CVE-2017-14062.
> +
> +Index: lib/punycode.c
> +--- lib/punycode.c.orig
>  lib/punycode.c
> +@@ -88,10 +88,10 @@ enum
> + /* point (for use in representing integers) in the range 0 to */
> + /* base-1, or base if cp does not represent a value.  */
> + 
> +-static punycode_uint
> ++static unsigned
> + decode_digit (punycode_uint cp)
> + {
> +-  return cp - 48 < 10 ? cp - 22 : cp - 65 < 26 ? cp - 65 :
> ++  return (unsigned) cp - 48 < 10 ? cp - 22 : cp - 65 < 26 ? cp - 65 :
> + cp - 97 < 26 ? cp - 97 : base;
> + }
> + 

This is twice wrong.  It's different from the actual change in the
referenced commit, and both are different from the libidn2 change.

-- 
Christian "naddy" Weisgerber  na...@mips.inka.de



Re: linking error when compiling zdoom

2017-10-02 Thread Timo Myyrä
Stuart Henderson  writes:

> On 2017/10/02 09:17, Timo Myyrä wrote:
>
>> Hi,
>> 
>> I'm trying to make port of zdoom but I can't get it to link.
>> 
>> The error I got was:
>> CMakeFiles/zdoom.dir/scripting/vm/vmexec.cpp.o: In function 
>> `__cxx_global_var_init':
>> /home/tmy/tmp/gzdoom-g3.1.0/src/scripting/vm/vmexec.cpp:(.text+0x42): 
>> undefined reference to `__cxa_thread_atexit'
>> c++: error: linker command failed with exit code 1 (use -v to see invocation)
>> *** Error 1 in . (src/CMakeFiles/zdoom.dir/build.make:10917 'gzdoom')
>
> is it using (/usr/bin/)c++ to link, or is it using ld directly? it should be 
> using c++.

I guess its using c++ though I'm not sure why its using path within the pobj
directory. Something to do with chroot changes in ports framework I guess.

Any case, the full command before the link error is as follows:

/usr/ports/pobj/zdoom-3.1.0/bin/c++  -std=gnu++14 -Wall -Wextra -Wno-unused
-Wno-unused-parameter -Wno-missing-field-initializers -ffp-contract=off
-Wno-inconsistent-missing-override  -O2 -pipe -ffp-contract=off
-fno-rtti -fomit-frame-pointer -DNDEBUG  -lpthread -lc++abi   -s
src/CMakeFiles/zdoom.dir/__autostart.cpp.o ... 
&& cd /usr/ports/pobj/zdoom-3.1.0/build-amd64/src 
&& chmod +x /usr/ports/pobj/zdoom-3.1.0/build-amd64/src/link-make 
&& /bin/sh -c /usr/ports/pobj/zdoom-3.1.0/build-amd64/src/link-make 
&& cd /usr/ports/pobj/zdoom-3.1.0/build-amd64/src 
&& /usr/local/bin/cmake -E copy_if_different 
/usr/ports/pobj/zdoom-3.1.0/gzdoom-g3.1.0/soundfont/gzdoom.sf2 
/usr/ports/pobj/zdoom-3.1.0/build-amd64

Timo



Re: linking error when compiling zdoom

2017-10-02 Thread Stuart Henderson
On 2017/10/02 09:17, Timo Myyrä wrote:
> Hi,
> 
> I'm trying to make port of zdoom but I can't get it to link.
> 
> The error I got was:
> CMakeFiles/zdoom.dir/scripting/vm/vmexec.cpp.o: In function 
> `__cxx_global_var_init':
> /home/tmy/tmp/gzdoom-g3.1.0/src/scripting/vm/vmexec.cpp:(.text+0x42): 
> undefined reference to `__cxa_thread_atexit'
> c++: error: linker command failed with exit code 1 (use -v to see invocation)
> *** Error 1 in . (src/CMakeFiles/zdoom.dir/build.make:10917 'gzdoom')

is it using (/usr/bin/)c++ to link, or is it using ld directly? it should be 
using c++.



Re: [update] ctwm-4.0.2

2017-10-02 Thread Jeremie Courreges-Anglas
On Mon, Oct 02 2017, timo.my...@wickedbsd.net (Timo Myyrä) wrote:

[...]

> ping

Well, it's lock time, please ping again when the ports tree is fully
unlocked.

-- 
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF  DDCC 0DFA 74AE 1524 E7EE



[wip] Firefox 57.0b4

2017-10-02 Thread Landry Breuil
Hi,

of course not targeted for the upcoming 6.2 release, but firefox 57 will
be quite a big change from 56, so testing is more than welcome.

https://www.mozilla.org/en-US/firefox/57.0beta/releasenotes/
https://www.mozilla.org/en-US/firefox/quantum/
https://hacks.mozilla.org/2017/09/firefox-quantum-developer-edition-fastest-firefox-ever/

etc etc - to note: non-webextensions addons (which are labelled
'legacy' in about:addons) will stop working with this version, you've
been warned. A separate content process should be enabled by default,
and thanks to semarie@'s help we managed to build and enable the new
'stylo' css rendering engine, written in rust.

So as usual, pull/update/rebuild from
https://cgit.rhaalovely.net/mozilla-firefox/log/?h=beta

Or try the packages from https://packages.rhaalovely.net/

Landry