On Wed, 10 Mar 1999, Chuck Robey wrote:
You know, guys, for programmers, wanting immediate panics on stuff like
this is great, but there isn't one user in a thousand that wants this.
If you make this kinda stuff default on a version *other than* current
(current being by definition, for
On Wed, 10 Mar 1999, Matthew Dillon wrote:
: :
: :This means that invariants need to add relatively little overhead.
: :
: :Peter
:
: which they do.
:
:You know, guys, for programmers, wanting immediate panics on stuff like
:this is great, but there isn't one user in a thousand
Chuck Robey wrote:
That's completely true, but nearly all users simply couldn't care less.
They don't see the long view, they only see what's happening right now.
With that I will agree... :)
It's the reason that your attitude is totally correct healthy for a
developer ... but the only
I want to make this change to printf so that it treats format codes like
'%llx' as 64bit formats (i.e. the same as '%qx'). This convention is the
same as that used by glibc.
I needed this change to make an i386-alpha cross debugger which worked
properly but I think that it is a good idea to be
I've put the bmake contrib framework for EGCS at
ftp://ftp.nuxi.com/pub/FreeBSD/egcs
(ftp://ftp.nuxi.com/pub/FreeBSD/egcs/cvs is all you really need)
This is very rough work, but should help us towards our goal.
In there you will find a CVS tree under ``cvs''. This CVS tree
corresponds
I want to make this change to printf so that it treats format codes like
'%llx' as 64bit formats (i.e. the same as '%qx'). This convention is the
same as that used by glibc.
%llx is actually for unsigned long longs, and %qx is actually for
u_quad_t's. These types are different for FreeBSD on
Karl Pielorz wrote:
It's the reason that your attitude is totally correct healthy for a
developer ... but the only thing that most users will see is the fact
that FreeBSD panics more often. They won't even bother to make of note
of why a panic occurred, all they will ever note is that
How's this going?
Everything now builds, and I can pass the C++ STL tests supplied with
EGCS.
There is at least one case w/in gnu/usr.bin/cc that ``make cleandir
make cleandir make obj make depend make make clean make''
will file to build. But I haven't worried too much about that yet.
On Thu, 11 Mar 1999, Chuck Robey wrote:
On Wed, 10 Mar 1999, Matthew Dillon wrote:
: :
: :This means that invariants need to add relatively little overhead.
: :
: :Peter
:
: which they do.
:
:You know, guys, for programmers, wanting immediate panics on stuff like
I've run into a small snag with the acd drivers.
Normal (store bought) CDs appear to function fine.
Recordables have some troubles. First off, 50% of the disks mount properly.
50% complain with the error Invalid Argument when doing a: 'mount -t
cd9660 /dev/acd0a /mnt/cdrom'
I can cat
On Thu, 11 Mar 1999, Bruce Evans wrote:
I want to make this change to printf so that it treats format codes like
'%llx' as 64bit formats (i.e. the same as '%qx'). This convention is the
same as that used by glibc.
%llx is actually for unsigned long longs, and %qx is actually for
@@ -1016,7 +1019,10 @@
flags |= SHORTINT;
goto rflag;
case 'l':
- flags |= LONGINT;
+ if (flags LONGINT)
+ flags |= QUADINT;
+ else
+
On Fri, 12 Mar 1999, Bruce Evans wrote:
@@ -1016,7 +1019,10 @@
flags |= SHORTINT;
goto rflag;
case 'l':
- flags |= LONGINT;
+ if (flags LONGINT)
+ flags |= QUADINT;
+
On Fri, 12 Mar 1999, Bruce Evans wrote:
@@ -1016,7 +1019,10 @@
flags |= SHORTINT;
goto rflag;
case 'l':
- flags |= LONGINT;
+ if (flags LONGINT)
+ flags |= QUADINT;
+
Hi,
Just an install report from the field
I did a new install of 4.0-19990311-SNAP onto a system that
was previously running 3.0-19991105-SNAP. The 3.0 system was
using the old boot blocks.
The 4.0 install was via ftp, and worked without a problem.
However, upon rebooting
15 matches
Mail list logo
