[2003-02-08 16:19] Matthew Emmerton said:
| It compiled on -CURRENT and -STABLE using this:
|
| #include
|
| You've got #include in your example below.
Deleting /usr/include/g++ and making installworld, fixes my
"problem". The compiler now gives the expected behavior; it
compiles the code w
[2003-02-08 15:56] Matthew Emmerton said:
| Your working example below compiles without error using gcc 2.95.x (FreeBSD
| 4.x) and gcc 3.2.x (FreeBSD 5.x), which is expected since it's compliant
| C++. (See Stroustrup's The C++ Programming Language, section 9.2.2, which
| indicates that the proper
In trying to compile the most recent native jdk-1.4.1, I noticed
that compiling with the header didn't work.
// ** won't link **
#include
// ** works **
// #include
// ** works **
// #include
// using namespace std;
int main(){
return 1;
}
void xxx (ostream& os) {
os << ' ';
os << "
A nullfs mounted target cannot be umounted if another target is
mounted from the same source. Maybe it has something to do with
the LOR in the first umount... I'll see if I can fix this later
in the week if it hasn't already been fixed.
scratch# uname -a
FreeBSD scratch.rcfile.org 5.0-CURRENT
[2002-12-30 18:53] Kris Kennaway said:
| I just wanted to share the good news that since updating to matt's
| vmspace fix (over a week ago), there have been no panics on the bento
| cluster (21 machines of 3 architectures running 5.0-RC, under constant
| heavy load, and despite the close proximity
[2002-11-18 11:39] Alfred Perlstein said:
| * Kris Kennaway <[EMAIL PROTECTED]> [021118 11:06] wrote:
| > I've just turned witness back on on the bento cluster, and got the
| > following lock order reversals a number of times overnight:
| >
| > Nov 18 07:45:40 gohan11 kernel: 1st 0xc6887200 pipe
[2002-12-04 15:12] Alfred Perlstein said:
| * Lars Eggert <[EMAIL PROTECTED]> [021204 15:04] wrote:
| >
| > FYI, just got a similar one yesterday on an up-to-date -current:
| >
| > lock order reversal
| > 1st 0xc784d700 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465
| > 2nd 0xc05138
On 04 Sep 2001 at 10:36 (+0200), Poul-Henning Kamp wrote:
|
| Assignment:
|
| The v_tag element in struct vnode is a debugging aid, but unfortunately
| it is implemented in a way which means that adding a filesystem means
| modifying the definition in .
|
| Convert the v_tag to an "const char *
