From: Robert C. <rw...@al...> - 2004-04-19 07:37:57
|
Hello all, How does one build coLinux from source on Windows? I've been reading through the wiki page: http://colinux.org/wiki/index.php/CygwinToolchain It seems as though these instructions are for building coLinux on Linux. Regards, - Robert |
From: Matt B. <ma...@zi...> - 2004-04-19 10:45:43
|
On Mon, Apr 19, 2004 at 02:37:25AM -0500, Robert Citek wrote: > How does one build coLinux from source on Windows? >=20 > I've been reading through the wiki page: > http://colinux.org/wiki/index.php/CygwinToolchain > It seems as though these instructions are for building coLinux on Linux. Unless something has changed that I've missed, you can't yet build on Windows. |
From: Daniel R. S. <dan...@ya...> - 2004-04-19 14:11:29
|
Actually, I did successfully build colinux under windows once. Instead of building a gcc cross-compiler, I built a native gcc compiler, then renamed the tools ( like gcc, ar, ld, etc ) to their cross-compiler versions ( i.e. i686-cygwin-gcc, etc). However, since you need a linux kernel source tree and a built vmlinux, it seemed a little pointless - you will still need a working linux (colinux works fine) to build the kernel and then you would need to copy all the linux stuff over to windows. The only real reason I can see for wanting to build under windows is if you wanted to try and use Visual Studio and the Microsoft DDK to build. However, this would involve a considerable number of changes as the compiler switches are different, the source tree layout for device drivers is different, and finally, the inline assembly syntax is different (Intel syntax vs. AT&T). On the other hand, if linux.sys were built with the Microsoft DDK, you could source debug it with the Microsoft tools. Currently I don't believe there is any way to source debug linux.sys since WinDbg doesn't know how to read gcc symbols and there are no GNU tools for kernel debugging Windows. -----Original Message----- From: col...@li... [mailto:col...@li...] On Behalf Of Matt Behrens Sent: Monday, April 19, 2004 6:48 AM To: Robert Citek Cc: col...@li... Subject: Re: [coLinux-devel] build environment on Windows On Mon, Apr 19, 2004 at 02:37:25AM -0500, Robert Citek wrote: > How does one build coLinux from source on Windows? > > I've been reading through the wiki page: > http://colinux.org/wiki/index.php/CygwinToolchain > It seems as though these instructions are for building coLinux on Linux. Unless something has changed that I've missed, you can't yet build on Windows. |
From: Dan A. <da...@co...> - 2004-04-20 04:59:10
|
On Mon, Apr 19, 2004 at 10:11:18AM -0400, Daniel R. Slater wrote: > The only real reason I can see for wanting to build under windows is if you > wanted to try and use Visual Studio and the Microsoft DDK to build. However, > this would involve a considerable number of changes as the compiler switches > are different, the source tree layout for device drivers is different, and > finally, the inline assembly syntax is different (Intel syntax vs. AT&T). > > On the other hand, if linux.sys were built with the Microsoft DDK, you could > source debug it with the Microsoft tools. Currently I don't believe there > is any way to source debug linux.sys since WinDbg doesn't know how to read > gcc symbols and there are no GNU tools for kernel debugging Windows. It seems that microsoft has recently released their compilers as Free Software, probably to promote Windows programmers. http://msdn.microsoft.com/visualc/vctoolkit2003/ I haven't read their EULA yet, but if it doesn't mean problems with GPL software, coLinux's binaries can be built with it. BTW, we only need their linker in order to build linux.sys along with a corresponding linux.pdb file. -- Dan Aloni da...@co... |
From: Daniel R. S. <dan...@ya...> - 2004-04-20 12:00:41
|
How can the linker generate a .pdb file from objects generated by gcc? As far as I know, the Microsoft linker doesn't understand the stabs format, and the -gcoff option doesn't work, you get errors from the assembler. -----Original Message----- From: col...@li... [mailto:col...@li...] On Behalf Of Dan Aloni Sent: Tuesday, April 20, 2004 1:00 AM To: Daniel R. Slater Cc: col...@li... Subject: Re: [coLinux-devel] build environment on Windows BTW, we only need their linker in order to build linux.sys along with a corresponding linux.pdb file. -- Dan Aloni da...@co... ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ coLinux-devel mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-devel |
From: Dan A. <da...@co...> - 2004-04-21 04:14:00
|
On Tue, Apr 20, 2004 at 08:00:30AM -0400, Daniel R. Slater wrote: > How can the linker generate a .pdb file from objects generated by gcc? As > far as I know, the Microsoft linker doesn't understand the stabs format, and > the -gcoff option doesn't work, you get errors from the assembler. Mingw32 generates COFF files by default. And we actually used the MS linker back in February in order to link linux.sys. -- Dan Aloni da...@co... |
From: Robert P. <rob...@ho...> - 2004-05-07 06:46:06
|
Hi folks coLinux is great and I have been using the 0.6.0 release for a while. I guess I am not adventurous enough to try the snapshots. If you guys have the time to respond, I am just curious when we will expect the next release and what will we expect in it. Thanks much. Rob |
From: Dan A. <da...@co...> - 2004-05-07 06:54:48
|
On Thu, May 06, 2004 at 07:59:39PM -0700, Robert Pang wrote: > Hi folks > > coLinux is great and I have been using the 0.6.0 release for a while. I > guess I am not adventurous enough to try the snapshots. If you guys have the > time to respond, I am just curious when we will expect the next release and > what will we expect in it. Hopefully, in a few days -- after service/driver installation confusion/problems are gone. List of changes: * Some small bugfixes. * Added the ability to send Ctrl-Alt-Del to the Linux machine. * Linux patch updated to 2.4.26 * Linux port (for systems running kernel 2.6.x) * Fixed a crash that could happen on swapoff(). * Initmem is freed (no more 'missing implementation') * The number of maximum cobd block devices was increased to 32. * The daemon process is pinned to the first processor until we get the SMP stability issue fixed. * Time is not going backward for gettimeofday() users anymore. * Support for running more than one instance of coLinux is now functional. * Windows: * Sizes of raw partition devices are now detected properly. This means that the resierfs problems should be over, plus cat /dev/cobd* would work for you. * Suspension of the host machine won't cause colinux-daemon problems like memory leaks. * The daemon can install itself as a service (Jaroslaw Kowalski). Stopping the service sends Ctrl-Alt-Del to let the Linux VM shutdown cleanly. * The daemon can install the linux.sys driver separately from its run, which can allow you to run coLinux as any user that have access to the installed driver (Daniel R. Slater). * coLinux now builds using MingW32 and no longer depends on cygwin1.dll. * Added scripts for building the MingW32 cross compiler on Linux, plus scripts that download, compile, and install the libraries coLinux depends on. * The name of the TAP device to use can be specified with the 'name' attribute in the XML. NOTICE: The name is matched against the string that appears in Network Connections (e.g., 'Local Area Connection') and not the device name assigned by Windows (e.g., 'TAP-Win32 Adapter') * Linux port: * Sending SIGHUP to the daemon causes it to issue Ctrl-Alt-Del on the Linux VM. * Consoles: * Fixed a bug in the clear operation: let it clear with the right video erase character so that ncurses apps would appear properly. * Fixed virtual console switching (alt-f1, alt-f2, etc.) so it will save/redraw the screen like it should. * FLTK: The cursor is visible again. * If keyboard focus is taken away from the consoles, it will release any pressed key in the VM. -- Dan Aloni da...@co... |
From: A. A. A. <alp...@tt...> - 2004-05-08 14:52:27
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, May 07, 2004 at 09:55:45AM +0300, Dan Aloni wrote: > On Thu, May 06, 2004 at 07:59:39PM -0700, Robert Pang wrote: > > Hi folks > > > > coLinux is great and I have been using the 0.6.0 release for a while. I > > guess I am not adventurous enough to try the snapshots. If you guys have the > > time to respond, I am just curious when we will expect the next release and > > what will we expect in it. > > Hopefully, in a few days -- after service/driver installation > confusion/problems are gone. > FWIW, I've noticed lazy_unload is PFALSE during that problem. Having glimpsed at the sources, my initial observation revealed the lack of LockServiceDatabase(), absence of which may lead to peculiar behaviour sometimes. Not sure if that problem relates to this, though. regards, -----BEGIN PGP SIGNATURE----- Comment: A. Alper ATICI OpenPGP KeyID: 0xB824F550 iQCVAwUBQJz0JCxW86+4JPVQAQK/4wQAlwIn9Y5KLVHJufJaN2YlP0jpMZanTbkN DlF549TXm32qQuJvIDy3kFlItZm3lBjoShEgm13tbZY3Zyp79Eiyu32Vv1xlZU+P 566ZOGtOz0vAl5I3FDxZ/tu/Dqzu6Zyngy2KOObWgN2nG6VEtmGMq0Gd/kxNvlco 4/j9O28Q3W4= =wQEH -----END PGP SIGNATURE----- |
From: Robert P. <rob...@ho...> - 2004-09-17 20:16:22
|
Hi everyone I have been using 0.6.1 release (2.4 kernel) for quite a few months and it has been very stable. When can we expect a stable release based on 2.6 kernel? I understand that the development has moved to 2.6 codeline and active development is underway in the framebuffer front. Shall we have a release on 2.6 kernel without the framebuffer? Thank you guys for your great work. Rob |
From: Henry N. <Henry.Ne@Arcor.de> - 2004-09-20 18:50:39
|
Robert Pang wrote: > Hi everyone > > I have been using 0.6.1 release (2.4 kernel) for quite a few months and it > has been very stable. When can we expect a stable release based on 2.6 > kernel? I understand that the development has moved to 2.6 codeline and > active development is underway in the framebuffer front. Shall we have a > release on 2.6 kernel without the framebuffer? > > Thank you guys for your great work. Framebuffer is absolutly under cunstruction. We can not give it to a user. Many small tested things must be cunstruct to a running system. Framebuffer is not easy to implement. I thank developers to give out the last snapshoot. This corrected many errors. Other site it is better to test this kernel without FB. So we can say errors comes from FB or comes not. Framebuffer make enouth errors :-( -- Henry Nestler |
From: Steven E. <ste...@ya...> - 2004-04-19 19:39:46
|
Hello, --- Matt Behrens <ma...@zi...> wrote: > Unless something has changed that I've missed, you can't yet build > on Windows. You currently cant build vmlinux but you should be able to build everything else. I think one of the ReactOS developers tested this. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash |
From: peter g. <plu...@p1...> - 2004-04-19 13:35:37
|
you use colinux of course ;) -----Original Message----- From: col...@li... [mailto:col...@li...]On Behalf Of Robert Citek Sent: 19 April 2004 08:37 To: col...@li... Subject: [coLinux-devel] build environment on Windows Hello all, How does one build coLinux from source on Windows? I've been reading through the wiki page: http://colinux.org/wiki/index.php/CygwinToolchain It seems as though these instructions are for building coLinux on Linux. Regards, - Robert ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ coLinux-devel mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-devel --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.659 / Virus Database: 423 - Release Date: 15/04/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.659 / Virus Database: 423 - Release Date: 15/04/2004 |
From: Robert C. <rw...@al...> - 2004-04-19 20:22:01
|
On Monday, April 19, 2004, at 02:37 AM, Robert Citek wrote: > It seems as though these instructions are for building coLinux on > Linux. I hope to first figure out how to build it on Linux and then (maybe, eventually) on Windows. See the example I've put on the wiki page with how I've setup my build environment: http://colinux.org/wiki/index.php/CygwinToolchain It's not complete, but it is a start. My machine is slow and is still compiling. Thanks to all who've replied. Regards, - Robert |
From: Robert C. <rw...@al...> - 2004-04-19 22:11:34
|
On Monday, April 19, 2004, at 03:21 PM, Robert Citek wrote: > I hope to first figure out how to build it on Linux and then (maybe, > eventually) on Windows. See the example I've put on the wiki page > with how I've setup my build environment: > http://colinux.org/wiki/index.php/CygwinToolchain Finished creating the build environment and put my notes on the wiki. It contains a few tree drawings of the directory structure and a script that sets up the build environment on Linux. The next question is, how do I build colinux? That is, where should I put the colinux source code? Couldn't find any info on the wiki. Thanks in advance for any guidance. Regards, - Robert |