"Shawn Walker" <[EMAIL PROTECTED]> writes:
> This seems rather tedious to do for every change. What do you folks do
> when making changes to ONNV? Do you work / build nightlies out of your
> mercurial directory? Do you commit them to a local mercurial
> repository? If so, can you tell me what setu
Greetings,
I have been trying to figure out what the best way to work with ONNV
when making changes.
Right now, I have a workspace directory with the tarballs for b72
extracted within.
My process looks like this:
1) change / add the files relevant to what I'm doing
2) copy the changed / added f
Greetings,
For a lint warning such as the following regarding fclose:
warning: function returns value which is always ignored: fclose
(E_FUNC_RET_ALWAYS_IGNOR2)
..where the code is something like:
fclose(fp);
I have seen two "solutions" to this, one which strikes me as the
"quick solution":
h
On 05/09/2007, Peter Memishian <[EMAIL PROTECTED]> wrote:
>1. Create a librpcsvc/common/llib-lrpcsvc file that has #includes for
> all of the header files that comprise its public interfaces, e.g.:
As an example of the quandary I have in determining public interfaces
( I hate to reply tw
On 05/09/2007, Peter Memishian <[EMAIL PROTECTED]> wrote:
>
> > I was expecting a llib-lrpcsvc file for librpcsvc, but didn't find one.
>
> I presume you meant llib-lrpcsvc.ln
>
> > Is it just missing or has it not yet been created?
>
> It appears to have not been created.
>
> > If it hasn't bee
Dear all:
in systm.h, there's:
#define LOADABLE_SYSCALL(s) (s->sy_flags & SE_LOADABLE)
A syscall is LOADABLE if its sy_flags is set as SE_LOADABLE.
err... Then what does LOADABLE mean? What are the differences between normal
syscalls (e.g. read, write, exec) and LOADABLE syscalls (e.g. syscall 6
To reply to myself, I managed to solve the problem; I have described it
relatively detailed here:
http://zvrba.net/tips/c++_dtrace.html
This message posted from opensolaris.org
___
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http:/
I had a situation like this:
namespace my {
void f()
{
DTRACE_PROBE(my, f_probe);
}
}
After postprocessing with dtrace -G as shown in the manual, I get linker errors
showing undefined symbols of mangled C++ names. Looking into sys/sdt.h, it
turns out that the function declaration in the macr
