Build XINU on Windows - Revision history

Akoehler: HOWTO:Build XINU on Windows moved to Build XINU on Windows: No need for HOWTO in the title, its a category.

2008-12-19T03:31:19Z

HOWTO:Build XINU on Windows moved to Build XINU on Windows: No need for HOWTO in the title, its a category.

Akoehler: /* Running on Windows */

2008-12-19T03:30:59Z

Running on Windows

Akoehler at 03:30, 19 December 2008

2008-12-19T03:30:44Z

Akoehler: /* Preparation */

2008-08-22T19:20:58Z

Preparation

Akoehler: HOWTO:Build XINU on Windows XP moved to HOWTO:Build XINU on Windows: The cross compiler created was tested on both Windows XP and Windows Vista.

2008-08-22T19:20:23Z

HOWTO:Build XINU on Windows XP moved to HOWTO:Build XINU on Windows: The cross compiler created was tested on both Windows XP and Windows Vista.

Akoehler: /* Running on Windows */

2008-08-22T19:18:53Z

Running on Windows

Akoehler: /* Running on Windows */

2008-08-22T19:18:13Z

Running on Windows

Amallen: created HOWTO:Build XINU on Windows XP page following notes by Christopher Swiderski

2008-07-31T22:24:21Z

created HOWTO:Build XINU on Windows XP page following notes by Christopher Swiderski

Amallen: added link to Cygwin homepage

2008-07-31T22:22:04Z

added link to Cygwin homepage

Amallen: created HOWTO:Build XINU on Windows XP page following notes by Christopher Swiderski

2008-07-31T22:20:01Z

created HOWTO:Build XINU on Windows XP page following notes by Christopher Swiderski

New page

== Preparation ==

First, make sure that you have all packages in the "''Devel''" category of [[Cygwin]] installed on your Windows machine. This will provide a UNIX-like background for performing gcc compilation and allows the use of other UNIX commands (''ie''. <code> cat</code>, <code> hostname</code>, ''etc'').

Next, you will need to create two directories: <code> /usr/src/build-binutils </code> and <code> /usr/src/build-gcc </code>.

Then, you will want to download the appropriate binary utilities.
We downloaded [http://www.gnu.org/software/binutils/ binutils] version
[http://ftp.gnu.org/gnu/binutils/binutils-2.17.tar.gz 2.17] and saved it in the directory <code> /usr/src/build-binutils</code>.

Then, download the GNU C Compiler. We downloaded [http://ftp.gnu.org/gnu/gcc/gcc-4.1.1/ GCC] version 4.1.1 and saved it in the directory <code> /usr/src/build-gcc</code>.

Once these are both downloaded, navigate to their respective directories and untar the tar files.

== Build Process ==

==== BINUTILS ====

First, navigate to the directory of the newly untarred files. For us the directory was <code> /usr/src/build-binutils/binutils-2.17</code>. Once there, run the following commands:
<pre>./configure --target=mipsel --prefix=/usr/cross --disable-nls
make all install</pre>

You will want to add these files to the path with the command:
<pre>export PATH=$PATH:/usr/cross/bin</pre>
'''NOTE:''' you can also add the command to your <code> ~/.bashrc </code> file to automatically add that directory to <code> PATH </code> everytime Cygwin is started.

==== GCC ====

Again, navigate to the directory of the newly untarred files. For us the directory was <code> /usr/src/build-gcc/gcc-4.1.1</code>. Once there, run the following commands:
<pre>./configure --target=mipsel --prefix=/usr/cross --disable-nls -enable-languages=c --without-headers
make all-gcc install-gcc

== Running on Windows ==

The previous setup should be sufficient for compiling and running XINU inside of a Cygwin bash shell. However, if you want to run it on regular Windows you will need to prepend the Cygwin paths to the Windows environment because in Windows XP ''hostname'' acts differently than ''hostname'' under UNIX. We solved this problem by adding <code> C:\cygwin\bin </code> and <code> C:\cygwin\usr\cross\bin </code> to the Windows XP environment PATH first, before any other directories. This way, ''hostname'' from the Cygwin installation will be the first occurrence of "hostname" when the XINU code tries to execute the command.

<hr/>
''This work is supported in part by NSF grant DUE-CCLI-0737476.''

@@ Line 35: / Line 35: @@
 The previous setup should be sufficient for compiling and running XINU inside of a Cygwin bash shell. However, if you want to run it on regular Windows you will need to prepend the Cygwin paths to the Windows environment because in Windows XP ''hostname'' acts differently than ''hostname'' under UNIX. We solved this problem by adding <code> C:\cygwin\bin </code> and <code> C:\cygwin\usr\cross\bin </code> to the Windows XP environment PATH first, before any other directories. This way, ''hostname'' from the Cygwin installation will be the first occurrence of "hostname" when the XINU code tries to execute the command.
-Alternatively, if you are setting up one or more frontend clients that use a Windows operating system you could use the Windows tool set to connect to the target pool or resource.  This tool set was initially released in the Spring of 2008 and is entitle [[WinXINU]].
+Alternatively, if you are setting up one or more frontend clients that use a Windows operating system you could use the Windows tool set to connect to the target pool or resource.  This tool set was initially released in the Spring of 2008 and is entitled [[WinXINU]].
 <hr/>
 ''This work is supported in part by NSF grant DUE-CCLI-0737476.''

← Older revision		Revision as of 03:30, 19 December 2008
Line 1:		Line 1:
		+	[[Category:HOWTO]]
	== Preparation ==		== Preparation ==
−
	First, make sure that you have all packages in the "''Devel''" category of [http://www.cygwin.com Cygwin] installed on your Windows machine. This will provide a UNIX-like background for performing gcc compilation and allows the use of other UNIX commands (''ie''. <code> cat</code>, <code> hostname</code>, ''etc'').		First, make sure that you have all packages in the "''Devel''" category of [http://www.cygwin.com Cygwin] installed on your Windows machine. This will provide a UNIX-like background for performing gcc compilation and allows the use of other UNIX commands (''ie''. <code> cat</code>, <code> hostname</code>, ''etc'').

@@ Line 35: / Line 35: @@
 The previous setup should be sufficient for compiling and running XINU inside of a Cygwin bash shell. However, if you want to run it on regular Windows you will need to prepend the Cygwin paths to the Windows environment because in Windows XP ''hostname'' acts differently than ''hostname'' under UNIX. We solved this problem by adding <code> C:\cygwin\bin </code> and <code> C:\cygwin\usr\cross\bin </code> to the Windows XP environment PATH first, before any other directories. This way, ''hostname'' from the Cygwin installation will be the first occurrence of "hostname" when the XINU code tries to execute the command.
-Alternatively, if you are setting up one or more frontend clients that use a Windows operating system you could use the Windows tool set to connect to the target pool.  This tool set was initially released in the Spring of 2008 and is entitle [[WinXINU]].
+Alternatively, if you are setting up one or more frontend clients that use a Windows operating system you could use the Windows tool set to connect to the target pool or resource.  This tool set was initially released in the Spring of 2008 and is entitle [[WinXINU]].
 <hr/>
 ''This work is supported in part by NSF grant DUE-CCLI-0737476.''

← Older revision	Revision as of 03:31, 19 December 2008
(No difference)

@@ Line 1: / Line 1: @@
 == Preparation ==
-First, make sure that you have all packages in the "''Devel''" category of [[Cygwin]] installed on your Windows machine. This will provide a UNIX-like background for performing gcc compilation and allows the use of other UNIX commands (''ie''. <code> cat</code>, <code> hostname</code>, ''etc'').
+First, make sure that you have all packages in the "''Devel''" category of [http://www.cygwin.com Cygwin] installed on your Windows machine. This will provide a UNIX-like background for performing gcc compilation and allows the use of other UNIX commands (''ie''. <code> cat</code>, <code> hostname</code>, ''etc'').
 Next, you will need to create two directories: <code> /usr/src/build-binutils </code> and <code> /usr/src/build-gcc </code>.

← Older revision	Revision as of 19:20, 22 August 2008
(No difference)

@@ Line 1: / Line 1: @@
 == Preparation ==
-First, make sure that you have all packages in the "''Devel''" category of [http://www.cygwin.com/ Cygwin] installed on your Windows machine. This will provide a UNIX-like background for performing gcc compilation and allows the use of other UNIX commands (''ie''. <code> cat</code>, <code> hostname</code>, ''etc'').
+First, make sure that you have all packages in the "''Devel''" category of [[Cygwin]] installed on your Windows machine. This will provide a UNIX-like background for performing gcc compilation and allows the use of other UNIX commands (''ie''. <code> cat</code>, <code> hostname</code>, ''etc'').
 Next, you will need to create two directories: <code> /usr/src/build-binutils </code> and <code> /usr/src/build-gcc </code>.
@@ Line 29: / Line 29: @@
 Again, navigate to the directory of the newly untarred files. For us the directory was <code> /usr/src/build-gcc/gcc-4.1.1</code>. Once there, run the following commands:
 <pre>./configure --target=mipsel --prefix=/usr/cross --disable-nls -enable-languages=c --without-headers
-make all-gcc install-gcc
+make all-gcc install-gcc</pre>
 == Running on Windows ==