Create a VM under VMWare with a limited RAM space, then run CoLinux =20
under that ;)
C
On Feb 7, 2006, at 2:12 PM, Erik D. Rodriguez wrote:
> Dave, you have any clue if they fixed the instability issue when users
> had > 1gb memory? This is the one thing that shot me down =20
> consistently.
> It would cause the system to blue screen. After extensive digging =20
> on the
> web sites, I found that not only was I not alone, but the cause had
> something to do with CoLinux not coping properly with a large memory
> pool.
>
> Erik
>
> -----Original Message-----
> From: gumstix-users-admin@...
> [mailto:gumstix-users-admin@...] On Behalf Of Dave
> Hylands
> Sent: Tuesday, February 07, 2006 9:33 AM
> To: gumstix-users@...
> Subject: Re: [Gumstix-users] gumstix compiler on win32
>
> Hi Ernest,
>
>> Does anyone have/know of a compiler for the gumstix that runs =20
>> natively
> under
>> windows (without a linux environment etc)? The amount of information
> on the
>> web is dizzying but most of it is *almost* really useful. I would be
> shocked
>> if no one has done this before for the gumstix. I am new to
> cross-compiling
>> and compiling the toolchain myself seems somewhat daunting.Ernest,
>>
>> according to the discussion and shared wisdom of the mailing list, =20=
>> the
>> allegedly simplest way to get the build stuff working under =20
>> windows is
> to
>> actually install Linux under windows using something called CoLinux
> (where
>> linux basically runs in a virtual machine under windows), and then
> create
>> the build stuff there under linux. People I think have had limited
> success
>> with using cygwin, but my own experience of cygwin is that it never
> quite
>> works the way you want it to. Is CoLinux an option for you?
>
> I highly recommend coLinux. A new release, 0.6.3 was just released a
> couple of days ago, and it wasn't too difficult to setup. The hardest
> part is the networking,
>
> I use coLinux almost exclusively for building my gumstix stuff. It
> isn't as fast as a dedicated linux machine, but it's faster than
> cygwin would be, if you could get it to work.
>
> Part of the problem (assuming you can get a toolchain up and running)
> has to do with case sensitivity on filenames. Linux is case senstive,
> windows isn't. Linux contains files which differ only by case (look in
> the netfilter directory). Not too difficult to work around, but it's
> just once small example of the hurdles that you face trying to get
> stuff working under cygwin.
>
> I've tried a few times to get the build to work under cygwin, and each
> time I've given up in frustration. coLinux rules!
>
> --
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.com/
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD =20
> SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through =20
> log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD =20
> SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=103432&bid#0486&dat=121642=
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
|