Re: [uClinux-dev] Porting Linux programs to uClinux and other

2007-10-30 Thread Mike Frysinger
On Tuesday 30 October 2007, Michael Schnell wrote: > I'm new to this, too, but one of the main differences is that in µCLinux > you don't have fork(). You need to use vfork() instead that works > somewhat different. If course this is only a point with multithreaded > programs. err, not really ...

Re: [uClinux-dev] Porting Linux programs to uClinux and other

2007-10-30 Thread Michael Schnell
I'm new to this, too, but one of the main differences is that in µCLinux you don't have fork(). You need to use vfork() instead that works somewhat different. If course this is only a point with multithreaded programs. -Michael ___ uClinux-dev mailin

RE: [uClinux-dev] Porting Linux programs to uClinux and other

2007-10-29 Thread Gavin Lambert
Quoth Greg Ungerer: > For applications there is no difference in the way you allocate > memory. Use malloc as you normally would. Although once you've done so you may need to be careful about issues like the power-of-two allocator and memory fragmentation. Especially on systems with limited RAM.

Re: [uClinux-dev] Porting Linux programs to uClinux and other

2007-10-29 Thread Greg Ungerer
Hi Felipe, Felipe Uderman wrote: I am getting started with uClinux, and I will try to build it to the ARM7 architecture today. I am waiting for the dist and arm-linux tools to be downloaded. I would like to know how does the process of writing applications for uClinux differ from doing it fo

[uClinux-dev] Porting Linux programs to uClinux and other

2007-10-29 Thread Felipe Uderman
Hello, I am getting started with uClinux, and I will try to build it to the ARM7 architecture today. I am waiting for the dist and arm-linux tools to be downloaded. I would like to know how does the process of writing applications for uClinux differ from doing it for Linux. Is this just compiling