Hey,
I found some inconsistent behavior with dd(1) when it comes to specifying
arguments in -CURRENT.
[ worr on terra ] ( ~ ) % dd if=/dev/zero of=/dev/null
count=18446744073709551616
dd: count: Result too large
[ worr on terra ] ( ~ ) % dd if=/dev/zero of=/dev/null
Hello.
I just stumped on the following gcc bug -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=15992 (std::locale is not
working for non-C locales).
It seems to affect all non-glibc platforms (reproducible on FreeBSD and
illumos). Tried the same test with clang - no difference (as affected
On 08/15/2014 12:31, Alexander Pyhalov wrote:
Hello.
I just stumped on the following gcc bug -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=15992 (std::locale is not
working for non-C locales).
Related libstdc++ bug - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41495
--
Best regards,
Started recently (within the last day or so).
--
Kernel build for LINT started on Fri Aug 15 11:08:29 UTC 2014
--
=== LINT
On Thu, Aug 14, 2014 at 11:55 PM, William Orr w...@worrbase.com wrote:
Hey,
I found some inconsistent behavior with dd(1) when it comes to specifying
arguments in -CURRENT.
[ worr on terra ] ( ~ ) % dd if=/dev/zero of=/dev/null
count=18446744073709551616
dd: count: Result too large
[
On Wed, Aug 13, 2014 at 6:34 PM, Russell L. Carter rcar...@pinyon.org wrote:
I love this idea. I recently moved back to FreeBSD after 14 years on
debian, and was shocked at how great poudriere + pkg is for
maintaining a consistent set of packages for a cluster of systems. (I
know it's
On Tue, 12 Aug 2014 23:28:07 +0200
Carlos Jacobo Puga Medina c...@fbsd.es wrote:
I believe it's still broken. There's a related PR at
http://bugs.freebsd.org/192452 and, I suspect, 192456. Aleksandr, would
you mind reverting this reversion? It seems to have created a lot of
problems.
keep in mind that the vt_vga code will be used for new VGA bring-up on
hardware that exposes legacy VGA bits and pieces, at least until EFI
booting is guaranteed everywhere. Trying to do development on the
console of something using the current vt_vga in order to bring up
things like an ethernet
It also has bad effects on boot time. My desktop takes something like 3
times as long to boot after r269471. If it can't be fixed quickly, it
needs to be reverted.
-Nathan
On 08/15/14 15:27, Adrian Chadd wrote:
keep in mind that the vt_vga code will be used for new VGA bring-up on
hardware
On 2014-08-13 10:38, Bryan Drewery wrote:
On 6/24/2014 4:28 PM, Craig Rodrigues wrote:
Hi,
I have a system running CURRENT at r266925 from May 31.
While doing some software builds using poudriere, the system
panicked. Unfortunately this system was not configured with
swap space, so I cannot
10 matches
Mail list logo