Re: [CFT] Unicode collation string and reworked locale definitions

[Baptiste Daroussin]

On Mon, Nov 02, 2015 at 06:59:15PM -0500, Pedro Giffuni wrote:
> First of all, congratulations to Baptiste and Marino for succeeding where
> I failed many moons ago. Also huge thanks to Nexenta and Garret D’Amore
> for relicensing localedef for us.
> 
> Concerning regex;
> 
> Gabor@ did a lot of work on libtre but according to him it was not up to the
> task performancewise. We would also lose features if we move to libtre.
> 
> I think our regex code actually has most of what is needed for multibyte
> already. I have a patch that turns on the functionality but I haven’t found
> any brave soul that will do the testing:
> 
> https://people.freebsd.org/~pfg/patches/regex-multibyte.diff
> 
I think it this can be tested once the collation branch is merged. Note that
dragonfly and musl libc both uses a patched version of libtre for the regex
implementation.

From my non scientific testing libtre was more reliable and performant then our
current regex. Anyway it will be relatively "easy" to test using the AT&T
testsuite the reliability and performance of both implementations: ours + your
patch and patched libtre.

Best regards,
Bapt


signature.asc
Description: PGP signature

Re: Tunnelling IPv4 over IPv6 for GitHub access?

[Craig Rodrigues]

On Mon, Nov 2, 2015 at 3:50 PM, Michael Gmelin  wrote:
>
>
>
> On Mon, 2 Nov 2015 14:04:18 -0800
>
> ikvjwd.com once offered a service using haproxy, you can find their
> configuration here:
>
>
https://github.com/rcsheets/ikvjwd/commit/58979dcaf42fbbd9203067a6ba4629ba01469120
>

We were using ikvjwd.com, but that service did not seem to be very reliable.


>
> Another way to tunnel all IPv4 traffic is set up an OpenVPN server on
> a dual stack machine and route your client IPv4 traffic over it (that
> approach is actually very easy to accomplish, stable and will work
> with any service).
>

Can you point me to some docs for how to do this?  This could work for me.

I have two separate networks that are connected:

+--+   +--+
|  |   |  |
|  |   |  |
|Dual  +-> |   IPv6   |
|stack |   |   only   |
|  |   |  |
+--+   +--+


My machine is in the IPv6 only network, but it has access to
a dual stack network.  I still need to run my stuff which accesses
GitHub in the IPv6 only network.

--
Craig
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Tunnelling IPv4 over IPv6 for GitHub access?

[Michael Gmelin]

On Mon, 2 Nov 2015 14:04:18 -0800
Craig Rodrigues  wrote:

> Hi,
> 
> I have some machines which are on an IPv6 only network.
> It works great and I can access most things on the IPv6 Internet
> that I need like Google ( [2607:f8b0:4004:808::1014]) , Facebook
> ([2a03:2880:1010:df05:face:b00c:0:2]), CNN ( [2620:100:e000::8001]),
> etc.
> 
> However, the one thing I cannot access is GitHub, which does not
> support IPv6 ().
> 
> Is there a way that I can tunnel IPv4 over an IPv6 network?
> 
> I read this blog post:
> http://www.aisecure.net/2013/02/03/tunneling-ipv4-over-ipv6-vpn/
> and wasn't sure if this was an approach that I could use.

ikvjwd.com once offered a service using haproxy, you can find their
configuration here:

https://github.com/rcsheets/ikvjwd/commit/58979dcaf42fbbd9203067a6ba4629ba01469120

Another way to tunnel all IPv4 traffic is set up an OpenVPN server on
a dual stack machine and route your client IPv4 traffic over it (that
approach is actually very easy to accomplish, stable and will work
with any service).

- Michael

> 
> --
> Craig
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to
> "freebsd-current-unsubscr...@freebsd.org"



-- 
Michael Gmelin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [CFT] Unicode collation string and reworked locale definitions

[Pedro Giffuni]

First of all, congratulations to Baptiste and Marino for succeeding where
I failed many moons ago. Also huge thanks to Nexenta and Garret D’Amore
for relicensing localedef for us.

Concerning regex;

Gabor@ did a lot of work on libtre but according to him it was not up to the
task performancewise. We would also lose features if we move to libtre.

I think our regex code actually has most of what is needed for multibyte
already. I have a patch that turns on the functionality but I haven’t found
any brave soul that will do the testing:

https://people.freebsd.org/~pfg/patches/regex-multibyte.diff

Thanks again,

Pedro.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: KLD: (nvidia.ko) is missing dependencies (boot message)

[Kris Moore]

Grub does not automatically load module deps, you need to manually specify 
linux_common or other deps of the nvidia driver. Take a look at what is loaded 
with kldstat after boot. 
--
Kris Moore



On Nov 2, 2015, 6:46 PM, at 6:46 PM, Kostya Berger  
wrote:
>Hi everyone.
>I'm on 11.0-CURRENT #0 r289580
>I didn't find this in any archives, so I'm posting it here. Mine is a
>ZFS based system and I'm booting using GRUB2, not the FreeBSD
>loader.However, this works just fine on FreeBSD 10.2 etc.
>But on 11.0-CURRENT this appears in boot message:...
>KLD file linux.ko is missing dependencies
>KLD file nvidia.ko is missing dependencies
>...Accordingly, nvidia.ko is not loaded on boot. But when I afterwards
>manually `kldload nvidia`, it works just fine and the driver gets
>loaded.
>Not sure if this is related, but on shutdown/reboot I also have some
>ZFS related debug output, of which I can only send a photo. Not
>attaching it now as I'm not sure how the mailing list software will
>react to this, but I'm ready to send it on demand.
> With kindest regards,
>Kostya Berger
> 
>___
>freebsd-current@freebsd.org mailing list
>https://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to
>"freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

KLD: (nvidia.ko) is missing dependencies (boot message)

[Kostya Berger]

Hi everyone.
I'm on 11.0-CURRENT #0 r289580
I didn't find this in any archives, so I'm posting it here. Mine is a ZFS based 
system and I'm booting using GRUB2, not the FreeBSD loader.However, this works 
just fine on FreeBSD 10.2 etc.
But on 11.0-CURRENT this appears in boot message:...
KLD file linux.ko is missing dependencies
KLD file nvidia.ko is missing dependencies
...Accordingly, nvidia.ko is not loaded on boot. But when I afterwards manually 
`kldload nvidia`, it works just fine and the driver gets loaded.
Not sure if this is related, but on shutdown/reboot I also have some ZFS 
related debug output, of which I can only send a photo. Not attaching it now as 
I'm not sure how the mailing list software will react to this, but I'm ready to 
send it on demand.
 With kindest regards,
Kostya Berger
 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: pf NAT and VNET Jails

[Kristof Provost]

> On 02 Nov 2015, at 15:07, Shawn Webb  wrote:
> 
> On Monday, 02 November 2015 02:59:03 PM Kristof Provost wrote:
>> 
>> Can you add your pf.conf too?
>> 
>> I’ll try upgrading my machine to something beyond 290228 to see if I can
>> reproduce it. It’s on r289635 now, and seems to be fine. My VNET jails
>> certainly get their traffic NATed.
> 
> Sorry about that! I should've included it. It's pasted here: http://ix.io/lLI
> 
> It's probably not the most concise. This is a laptop that can have one of 
> three interfaces online: re0 (ethernet on the laptop), wlan0 (you can guess 
> what that is), or ue0 (usb tethering from my phone). I used to be able to 
> specify NATing like that and pf would automatically figure out which outgoing 
> device to use. Seems like that's broken now.
> 
I’ve updated my machine and things still seem to be working.
As you said, it’s probably related to the multiple nat entries.

I’ll have to make a test setup, which’ll take a bit of time, especially 
since I’m messing with  the host machine at the moment.

Regards,
Kristof

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Tunnelling IPv4 over IPv6 for GitHub access?

[Mark Martinec]

Craig Rodrigues wrote:


I have some machines which are on an IPv6 only network.
It works great and I can access most things on the IPv6 Internet
that I need like Google ( [2607:f8b0:4004:808::1014]) , Facebook
([2a03:2880:1010:df05:face:b00c:0:2]), CNN ( [2620:100:e000::8001]), 
etc.


However, the one thing I cannot access is GitHub, which does not
support IPv6 ().

Is there a way that I can tunnel IPv4 over an IPv6 network?

I read this blog post:
http://www.aisecure.net/2013/02/03/tunneling-ipv4-over-ipv6-vpn/
and wasn't sure if this was an approach that I could use.


I don't see how a tunnel encapsulation would help here - you need to
translate between protocol families, as your client side is IPv6-only.

If all the traffic is HTTP then a web proxy like squid running
on a dual-stacked host would suffice. Otherwise a NAT64 (with DNS64)
is needed, like implemented in OpenBSD's pf (but not available
in FreeBSD's pf).

  Mark
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Tunnelling IPv4 over IPv6 for GitHub access?

[Yonas Yanfa]

On 11/02/2015 17:04, Craig Rodrigues wrote:

Hi,

I have some machines which are on an IPv6 only network.
It works great and I can access most things on the IPv6 Internet
that I need like Google ( [2607:f8b0:4004:808::1014]) , Facebook
([2a03:2880:1010:df05:face:b00c:0:2]), CNN ( [2620:100:e000::8001]), etc.

However, the one thing I cannot access is GitHub, which does not
support IPv6 ().

Is there a way that I can tunnel IPv4 over an IPv6 network?

I read this blog post:
http://www.aisecure.net/2013/02/03/tunneling-ipv4-over-ipv6-vpn/
and wasn't sure if this was an approach that I could use.

--
Craig
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Weird how such a geek central place like GitHub doesn't support IPv6 o_O.

I'm unfamiliarity with tunnelling IPv4 over IPv6, but I'm curious if the 
guide you found on aisecure.net worked for you? I would give it a shot 
if you haven't tried them yet. It was written only a few years ago 
(2013), so it could still work.


Cheers,
Yonas

--

Yonas Yanfa
In Love With Open Source
Drupal  :: GitHub 
 :: Mozilla 
 :: iPhone 


fizk.net | yo...@fizk.net

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Tunnelling IPv4 over IPv6 for GitHub access?

[Craig Rodrigues]

Hi,

I have some machines which are on an IPv6 only network.
It works great and I can access most things on the IPv6 Internet
that I need like Google ( [2607:f8b0:4004:808::1014]) , Facebook
([2a03:2880:1010:df05:face:b00c:0:2]), CNN ( [2620:100:e000::8001]), etc.

However, the one thing I cannot access is GitHub, which does not
support IPv6 ().

Is there a way that I can tunnel IPv4 over an IPv6 network?

I read this blog post:
http://www.aisecure.net/2013/02/03/tunneling-ipv4-over-ipv6-vpn/
and wasn't sure if this was an approach that I could use.

--
Craig
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

FreeBSD_HEAD-tests - Build #1639 - Fixed

[jenkins-admin]

FreeBSD_HEAD-tests - Build #1639 - Fixed:

Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1639/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1639/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1639/console

Change summaries:

No changes
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

FreeBSD_HEAD-tests - Build #1638 - Still Unstable

[jenkins-admin]

FreeBSD_HEAD-tests - Build #1638 - Still Unstable:

Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1638/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1638/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1638/console

Change summaries:

No changes


The failed test cases:

4 tests failed.
FAILED:  lib.libc.stdio.fmemopen2_test.test_data_length

Error Message:
/builds/FreeBSD_HEAD/lib/libc/tests/stdio/fmemopen2_test.c:203: pos == 0 not met

FAILED:  lib.libc.stdio.fmemopen_test.test09

Error Message:
3956 checks failed; see output for more details

FAILED:  lib.libc.stdio.fmemopen_test.test11

Error Message:
6020 checks failed; see output for more details

FAILED:  lib.libc.stdio.fmemopen_test.test14

Error Message:
1806 checks failed; see output for more details

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Per-process PS_STRINGS, USRSTACK, shared_obj_base, and sigcode_base

[Shawn Webb]

Hey All,

I've updated this patch to the latest HEAD. This patch is a preparatory patch 
for ASLR. It makes it so that PS_STRINGS, USRSTACK, the VDSO, and the signal 
trampolining code pointers are all stored per-process. Going forward, with 
HardenedBSD's ASLR patch, these values will be modified to introduce 
randomness/entropy. The goal with this patch is to allow randomization of the 
stack base address and the VDSO.

You can find the patch here: https://reviews.freebsd.org/D3565

Thanks,

-- 
Shawn Webb
HardenedBSD

GPG Key ID:0x6A84658F52456EEE
GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89  3D9E 6A84 658F 5245 6EEE

signature.asc
Description: This is a digitally signed message part.

Re: pf NAT and VNET Jails

[Shawn Webb]

On Monday, 02 November 2015 02:59:03 PM Kristof Provost wrote:
> > On 02 Nov 2015, at 14:47, Shawn Webb  wrote:
> > 
> > On Sunday, 01 November 2015 07:16:34 AM Julian Elischer wrote:
> >> On 11/1/15 2:50 AM, Shawn Webb wrote:
> >>> I'm at r290228 on amd64. I'm not sure which revision I was on last when
> >>> it
> >>> last worked, but it seems VNET jails aren't working anymore.
> >>> 
> >>> I've got a bridge, bridge1, with an IP of 192.168.7.1. The VNET jails
> >>> set
> >>> their default route to 192.168.7.1. The host simply NATs outbound from
> >>> 192.168.7.0/24 to the rest of the world. The various epairs get added to
> >>> bridge1 and assigned to each jail. Pretty simple setup. That worked
> >>> until
> >>> today. When I do tcpdump on my public-facing NIC, I see that NAT isn't
> >>> applied. When I run `ping 8.8.8.8` from the jail, the jail's
> >>> 192.168.7.0/24
> >>> address gets sent on the wire.
> >>> 
> >>> Let me know what I can do to help debug this further.
> >> 
> >> send the list your setup script/settings?
> > 
> > I'm using iocage to start up the jails. Here's a pasted output of `iocage
> > get all mutt-hardenedbsd`: http://ix.io/lLG
> 
> Can you add your pf.conf too?
> 
> I’ll try upgrading my machine to something beyond 290228 to see if I can
> reproduce it. It’s on r289635 now, and seems to be fine. My VNET jails
> certainly get their traffic NATed.

Sorry about that! I should've included it. It's pasted here: http://ix.io/lLI

It's probably not the most concise. This is a laptop that can have one of 
three interfaces online: re0 (ethernet on the laptop), wlan0 (you can guess 
what that is), or ue0 (usb tethering from my phone). I used to be able to 
specify NATing like that and pf would automatically figure out which outgoing 
device to use. Seems like that's broken now.

Thanks,

-- 
Shawn Webb
HardenedBSD

GPG Key ID:0x6A84658F52456EEE
GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89  3D9E 6A84 658F 5245 6EEE

signature.asc
Description: This is a digitally signed message part.

Re: pf NAT and VNET Jails

[Kristof Provost]

> On 02 Nov 2015, at 14:47, Shawn Webb  wrote:
> 
> On Sunday, 01 November 2015 07:16:34 AM Julian Elischer wrote:
>> On 11/1/15 2:50 AM, Shawn Webb wrote:
>>> I'm at r290228 on amd64. I'm not sure which revision I was on last when it
>>> last worked, but it seems VNET jails aren't working anymore.
>>> 
>>> I've got a bridge, bridge1, with an IP of 192.168.7.1. The VNET jails set
>>> their default route to 192.168.7.1. The host simply NATs outbound from
>>> 192.168.7.0/24 to the rest of the world. The various epairs get added to
>>> bridge1 and assigned to each jail. Pretty simple setup. That worked until
>>> today. When I do tcpdump on my public-facing NIC, I see that NAT isn't
>>> applied. When I run `ping 8.8.8.8` from the jail, the jail's
>>> 192.168.7.0/24
>>> address gets sent on the wire.
>>> 
>>> Let me know what I can do to help debug this further.
>> 
>> send the list your setup script/settings?
> 
> I'm using iocage to start up the jails. Here's a pasted output of `iocage get 
> all mutt-hardenedbsd`: http://ix.io/lLG

Can you add your pf.conf too?

I’ll try upgrading my machine to something beyond 290228 to see if I can 
reproduce it.
It’s on r289635 now, and seems to be fine. My VNET jails certainly get their 
traffic NATed.

Thanks,
Kristof

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: pf NAT and VNET Jails

[Shawn Webb]

On Sunday, 01 November 2015 07:16:34 AM Julian Elischer wrote:
> On 11/1/15 2:50 AM, Shawn Webb wrote:
> > I'm at r290228 on amd64. I'm not sure which revision I was on last when it
> > last worked, but it seems VNET jails aren't working anymore.
> > 
> > I've got a bridge, bridge1, with an IP of 192.168.7.1. The VNET jails set
> > their default route to 192.168.7.1. The host simply NATs outbound from
> > 192.168.7.0/24 to the rest of the world. The various epairs get added to
> > bridge1 and assigned to each jail. Pretty simple setup. That worked until
> > today. When I do tcpdump on my public-facing NIC, I see that NAT isn't
> > applied. When I run `ping 8.8.8.8` from the jail, the jail's
> > 192.168.7.0/24
> > address gets sent on the wire.
> > 
> > Let me know what I can do to help debug this further.
> 
> send the list your setup script/settings?

I'm using iocage to start up the jails. Here's a pasted output of `iocage get 
all mutt-hardenedbsd`: http://ix.io/lLG

Thanks,

-- 
Shawn Webb
HardenedBSD

GPG Key ID:0x6A84658F52456EEE
GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89  3D9E 6A84 658F 5245 6EEE

signature.asc
Description: This is a digitally signed message part.

FreeBSD_HEAD-tests - Build #1637 - Still Unstable

[jenkins-admin]

FreeBSD_HEAD-tests - Build #1637 - Still Unstable:

Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1637/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1637/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1637/console

Change summaries:

No changes


The failed test cases:

4 tests failed.
FAILED:  lib.libc.stdio.fmemopen2_test.test_data_length

Error Message:
/builds/FreeBSD_HEAD/lib/libc/tests/stdio/fmemopen2_test.c:203: pos == 0 not met

FAILED:  lib.libc.stdio.fmemopen_test.test09

Error Message:
3956 checks failed; see output for more details

FAILED:  lib.libc.stdio.fmemopen_test.test11

Error Message:
6020 checks failed; see output for more details

FAILED:  lib.libc.stdio.fmemopen_test.test14

Error Message:
1806 checks failed; see output for more details

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: FreeBSD_HEAD-tests - Build #1636 - Still Unstable

[Andrey Chernov]

On 02.11.2015 11:36, jenkins-ad...@freebsd.org wrote:
> FreeBSD_HEAD-tests - Build #1636 - Still Unstable:
> 
> Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1636/
> Full change log: 
> https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1636/changes
> Full build log: 
> https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1636/console
> 
> Change summaries:
> 
> No changes
> 
> 
> The failed test cases:
> 
> 4 tests failed.
> FAILED:  lib.libc.stdio.fmemopen2_test.test_data_length
> 
> Error Message:
> /builds/FreeBSD_HEAD/lib/libc/tests/stdio/fmemopen2_test.c:203: pos == 0 not 
> met
> 
> FAILED:  lib.libc.stdio.fmemopen_test.test09
> 
> Error Message:
> 3956 checks failed; see output for more details
> 
> FAILED:  lib.libc.stdio.fmemopen_test.test11
> 
> Error Message:
> 6020 checks failed; see output for more details
> 
> FAILED:  lib.libc.stdio.fmemopen_test.test14
> 
> Error Message:
> 1806 checks failed; see output for more details

It is already fixed in -current a day ago, i.e. runtime is outdated.

-- 
http://ache.vniz.net/
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [CFT] Unicode collation string and reworked locale definitions

[Garrett Cooper]

> On Nov 2, 2015, at 02:17, Baptiste Daroussin  wrote:
> 
>> On Mon, Nov 02, 2015 at 10:04:11AM +, David Chisnall wrote:
>>> On 1 Nov 2015, at 21:30, Baptiste Daroussin  wrote:
>>> 
>>> All issues reported has been fixed, except if more issues are reported, this
>>> will be merged into head next saturday: November 7th
>> 
>> That’s really excellent news!  Thanks for doing this.  Are there any good 
>> potential sources for the regex stuff?  I think std::regex in libc++ 
>> supports multibyte character sets, but is very full of templates and not 
>> very easy to translate into C.
> For te regex tools, it will be another step. I was planning to incorporate
> libtre + apple's patches like dragonfly did, it would need a lot of tests, but
> from my current testing performances are better than our current 
> implementation.
> And it makes libc's regrex passing way more entries in the AT&T regex test 
> suite
> 
> If anyone else want to work on bringing in that I would be very glad as I have
> already too much things in my plate :)

I was about to say... The regex tests on FreeBSD in tools/regression/lib/libc 
are quite broken ;(.. (Bug 191354). I'd like to fix/salvage those test cases if 
at all possible -- this might be a good motivator for that.
Thanks,
-NGie
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [CFT] Unicode collation string and reworked locale definitions

[Baptiste Daroussin]

On Mon, Nov 02, 2015 at 10:04:11AM +, David Chisnall wrote:
> On 1 Nov 2015, at 21:30, Baptiste Daroussin  wrote:
> > 
> > All issues reported has been fixed, except if more issues are reported, this
> > will be merged into head next saturday: November 7th
> 
> That’s really excellent news!  Thanks for doing this.  Are there any good 
> potential sources for the regex stuff?  I think std::regex in libc++ supports 
> multibyte character sets, but is very full of templates and not very easy to 
> translate into C.
> 
For te regex tools, it will be another step. I was planning to incorporate
libtre + apple's patches like dragonfly did, it would need a lot of tests, but
from my current testing performances are better than our current implementation.
And it makes libc's regrex passing way more entries in the AT&T regex test suite

If anyone else want to work on bringing in that I would be very glad as I have
already too much things in my plate :)

Best regards,
Bapt


signature.asc
Description: PGP signature

Re: [CFT] Unicode collation string and reworked locale definitions

[David Chisnall]

On 1 Nov 2015, at 21:30, Baptiste Daroussin  wrote:
> 
> All issues reported has been fixed, except if more issues are reported, this
> will be merged into head next saturday: November 7th

That’s really excellent news!  Thanks for doing this.  Are there any good 
potential sources for the regex stuff?  I think std::regex in libc++ supports 
multibyte character sets, but is very full of templates and not very easy to 
translate into C.

David

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [HEADSUP] OpenSSL updated to 1.0.2d

[Boris Samorodov]

02.11.2015 06:05, Jason Unovitch пишет:
> On Nov 1, 2015 10:06 AM, "Boris Samorodov"  wrote:
>> 30.10.2015 23:57, Jung-uk Kim пишет:
>>
>>> OpenSSL on head has been updated to 1.0.2d.  Please make sure to
>>> recompile all binaries depending on libcrypto.so.7 or libssl.so.7.
>>
>> Great, thanks!
>>
>> How do those who use FreeBSD official packages supposed to upgrade
>> packages?
> 
> This is on head so it should be the same process as any other source based
> upgrade per the handbook.
> 
> https:// 
> www.freebsd.org 
> /doc/handbook/ 
> makeworld.html 
> 
> The 'make delete-old-libs' step would have to wait until after the official
> 11-CURRENT package builders have been updated to a revision after this
> change and a 'pkg upgrade' installs everything from that build.

Jason, thanks. Seems that "pkg upgrade -f" should DTRT.

-- 
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

FreeBSD_HEAD-tests - Build #1636 - Still Unstable

[jenkins-admin]

FreeBSD_HEAD-tests - Build #1636 - Still Unstable:

Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1636/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1636/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1636/console

Change summaries:

No changes


The failed test cases:

4 tests failed.
FAILED:  lib.libc.stdio.fmemopen2_test.test_data_length

Error Message:
/builds/FreeBSD_HEAD/lib/libc/tests/stdio/fmemopen2_test.c:203: pos == 0 not met

FAILED:  lib.libc.stdio.fmemopen_test.test09

Error Message:
3956 checks failed; see output for more details

FAILED:  lib.libc.stdio.fmemopen_test.test11

Error Message:
6020 checks failed; see output for more details

FAILED:  lib.libc.stdio.fmemopen_test.test14

Error Message:
1806 checks failed; see output for more details

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"