Hi folks,
I detected a minor problem while compiling 2.6.14.2 with the most recent
xenomai code from svn. The Compilation would quit at linking if one
tries to build the posix skin as built-in module. Abort message:
ipc/built-in.o: In function `sem_init':
: multiple definition of `sem_init'
Philippe Gerum wrote:
Jan Kiszka wrote:
Philippe Gerum wrote:
Jan Kiszka wrote:
Jan Kiszka wrote:
...
A patch says more than thousand words. ;)
As a first approach, I picked the second variant and implemented a new
function called rt_pipe_setpool. I also had to extend rt_pipe_alloc
Jan Kiszka wrote:
Hi there,
yea, I also want to join this endless pipe discussion! ;)
We ran into troubles here due to large messages that should be sent via
native pipes. Large means larger than the default message heap, the
system heap, of the pipe subsystem so far. That raised the
Jan Kiszka wrote:
...
A patch says more than thousand words. ;)
As a first approach, I picked the second variant and implemented a new
function called rt_pipe_setpool. I also had to extend rt_pipe_alloc and
rt_pipe_free so that the right pool is used by them.
I thought about this variant
[EMAIL PROTECTED] wrote on 22.11.2005 11:21:09:
Jan Kiszka wrote:
...
A patch says more than thousand words. ;)
As a first approach, I picked the second variant and implemented a new
function called rt_pipe_setpool. I also had to extend rt_pipe_alloc and
rt_pipe_free so that the
Hi folks,
I detected a minor problem while compiling 2.6.14.2 with the most recent
xenomai code from svn. The Compilation would quit at linking if one
tries to build the posix skin as built-in module. Abort message:
ipc/built-in.o: In function `sem_init':
: multiple definition of `sem_init'
Philippe Gerum wrote:
Jan Kiszka wrote:
Philippe Gerum wrote:
Jan Kiszka wrote:
Jan Kiszka wrote:
...
A patch says more than thousand words. ;)
As a first approach, I picked the second variant and implemented a new
function called rt_pipe_setpool. I also had to extend rt_pipe_alloc
