RE: [rtl] Can't use unistd.h in C++ realtime modules?

Ivan, The rtl headers should but don't have #ifdef __cplusplus extern C #endif at the top. Therefore you have to make the extern C declaration yourself. I just use the example header (from examples/cpp) rtl_cpp.h and added #define unistd.h to it. Note: I moved the new and delete functions to

[rtl] Error with sem_getvalue function

This is a bug report for fsmlabs regarding RTLinux3.1 (at least) The semaphore function .. int sem_getvalue(sem_t* sem, int* sval) is supposed to write the semaphore value to the int pointed to by sval, and return an error code. Instead, it doesn't write anything to sval, and returns the

RE: [rtl] Maximum cycling frequency of 200Hz?

but it seems to be less than 10% on the PMMX-233. What do you have your thread doing? Norm - Original Message - From: David Hamilton [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, October 15, 2001 5:44 AM Subject: [rtl] Maximum cycling frequency of 200Hz? I'm running RTLinux 3.1

RE: [rtl] create thread from thread?

and that thread creates all of our other threads. If you can send me a simple example that crashes maybe I can help. John Jacques [EMAIL PROTECTED] Chunky Kibbles wrote: On Fri, Oct 12, 2001 at 04:17:39PM +0100, David Hamilton wrote: Is it allowed to create a thread from within a thread

RE: [rtl] Crashing when deleting C++ objects!

] Crashing when deleting C++ objects! On Monday 15 October 2001 12:59, David Hamilton wrote: Hmmm! I've got a simple C++ program running under rtlinux. When I stop it with rmmod, my systems locks up. I've narrowed this down to a delete call in one of my destructors. Actually this is my only delete

RE: [rtl] Maximum cycling frequency of 200Hz?

Stephen, Norman, et al. After an exhaustive search, I've finally isolated my cycling frequency problem, but I don't fully understand it yet. In order to post the problem on the mailing list, I tried to reproduce the fault in a single file of simple code, and then found that I was able to get

RE: [rtl] unresolved symbol _GLOBAL_OFFSET_TABLE_

Maxime, If you haven't deleted the original RedHat 7.1 compiler (gcc/g++ 2.96), then you might get results with this. I am compiling C++ code with 2.96, and although I get a lot of warnings about #undef's, it seems to hang together. I'm still waiting, however, for someone to write in with the gcc

[rtl] Maximum cycling frequency of 200Hz?

I'm running RTLinux 3.1 on a PC with an AMD K6 500Mhz processor (RedHat7.1). I seem to be only able to run a real-time loop at a maximum frequency of 200Hz. Trying to set a lower period in pthread_make_period... or a shorter sleep in nanosleep has no effect beyond 200Hz (5msec)! I've read in

RE: [rtl] C++ compiling problem

2001 19:26 To: [EMAIL PROTECTED] Subject: Re: [rtl] C++ compiling problem On Wednesday 10 October 2001 19:22, David Hamilton wrote: I tried writing some simple apps in C++, and the compiler produces errors. This can be re-produced by simply renaming the hello.c example hello.cpp and trying

RE: [rtl] C++ compiling problem

PROTECTED]] Sent: 10 October 2001 19:26 To: [EMAIL PROTECTED] Subject: Re: [rtl] C++ compiling problem On Wednesday 10 October 2001 19:22, David Hamilton wrote: I tried writing some simple apps in C++, and the compiler produces errors. This can be re-produced by simply renaming the hello.c example

RE: [rtl] C++ makefiles and compiling

Maxime, I've just succeeded in getting a two source file program linked. Initially, both .cpp files had the rtl_cpp.h file included and I was getting link errors due to the new, new[] etc routines existing twice. I have now divided the rtl_cpp.h file into two files. one with the

[rtl] C++ compiling problem

I tried writing some simple apps in C++, and the compiler produces errors. This can be re-produced by simply renaming the hello.c example hello.cpp and trying to compile. There is something about conflict between C and C++ linkage in linux kernel headers. Anybody got any ideas. Is there a general

RE: [rtl] Redhat 7.1 and v3.1?

Tony, I also have the Redhat 7.1 linux installation. I downloaded the prepatched RTLinux3.0 (file rtlinux_kernel-2.4.tar.gz) and had problems compiling the kernel. There were many warnings about #undefs and finally errors with the Checksum.S file. I downloaded and compiled gcc-2.95.3 from

[rtl] Any sample code for RTLinux3.0

I've installed the RTLinux3.0 kernel under my red hat 7.1! (used gcc 2.95.3 as red hat's gcc 2.96 wouldn't compile the RTLinux kernel) It seems to be working, but there are no examples or test programs to run in the RTLinux3.0 download. Has anyone got some simple sample code to demonstrate the

[rtl] Problem compiling RTLinux kernel

Hello, I've downloaded several versions of RTLinux (2.2 and 3.0) and followed the installations carefully. However, the 'make bzImage' compilation always breaks down at file checksum.S error message checksum.S:231: badly punctuated parameter list in #define checksum.S:237: badly punctuated

[rtl] Embedded PPC application

Hi, Does anyone use RTLinux on an embedded PowerPC 603e or 750 target? Are there particular issues with not having a local disk? Is it recommended to load RTLinux on a DiskOnChip or is it ok to load and run over a network connection? Is there a gnu cross-compiler from Intel development PC to