Porting GCC to your OS: Difference between revisions

← Older edit

Porting GCC to your OS (view source)

Revision as of 20:22, 10 July 2023

200 bytes added , 11 months ago

no edit summary

[unchecked revision]

VisualWikitext

Anonymous user

osdev>Khaledhammouda

Revision as of 03:49, 3 March 2007 (view source) osdev>Jhawthorn No edit summary		Latest revision as of 20:22, 10 July 2023 (view source) osdev>Khaledhammouda No edit summary
(10 intermediate revisions by 6 users not shown)
Line 1: {{~~Convert~~Rating\|4}} {{In Progress}} * Read ~~''Note that the~~ [[GCC Cross-Compiler] ~~page is intended to include the~~]. * Make a [[OS Specific Toolchain]]. ~~information below (as well as filling in the To-Dos) once it is finished.~~ * Read [[Hosted GCC Cross-Compiler]]. ~~Unless someone else does it first, I'll do so once my PDCLib is finished.''%%%-- MartinBaute~~ * Have a sufficient [[C Library]]. GCC is fairly portable and needs the C standard library, and some extensions from POSIX. It needs fork and exec, for instance, to run the assembler and linker. You will need a C++ standard library (such as libstdc++) as GCC is now written in [[C++]]. * Cross-compile libgmp, libmpc, libmpfr and other dependencies with instructions in [[Cross-Porting Software]]. * Likewise cross-compile [[Binutils]] and [[GCC]], but pass the special configure options <tt>--with-build-sysroot=/your/sysroot</tt> and <tt>--with-sysroot=/</tt>. The option <tt>--with-build-sysroot</tt> option uses that [[sysroot]] for the duration of the build, but the final program does not remember it. <tt>--with-sysroot=/</tt> should not be needed or should be set to the empty string, but some binutils/gcc versions are buggy and require it, which has the disadvantage the final toolchain might use <tt>//foo</tt> instead of <tt>/foo</tt>. You should ''only'' pass these options to the Binutils and GCC builds, some other packages also have a <tt>--with-sysroot</tt> option, but it instead means a libtool feature you should ''not'' use. * Become self-hosting and complete [[Bare_Bones#Bare_Bones_II\|Bare Bones II]]. Congratulations. == See Also == First, you should understand [How kernel, compiler, and C library work together]. If any of the next steps gives you trouble, the information given in that document should give you an idea of what is missing. * [[Binutils]] * [[Cross-Porting Software]] * [[GCC]] * [[GCC Cross-Compiler]] * [[Hosted GCC Cross-Compiler]] * [[OS Specific Toolchain]] * [[Sysroot]] [[Category:Porting]] ~~Next, you should build a [GCC Cross-Compiler] for your platform.~~ [[Category:Compilers]] ~~''ToDo: elaborate on [GCC]'s platform description, and how to set up your own if you don't want to use an existing one.''~~ ~~Then, you need a C standard library for your platform - at least those parts required by GCC.~~ ~~''ToDo: elaborate on the requirements of GCC on the library.''~~ ~~Finally, you would use the cross-compiler to compile [GCC] ''to run on your platform''.~~ Just to be sure, you would use that "native" [GCC] to compile itself (to be sure it could, and for weeding out any issues that might arise from cross-compilation). Congratulations, you are now what people call "self-hosted", i.e. you no longer need some other OS to do development work. (Provided you have a working editor for your platform.) ~~''External Links''~~ [Scratch Box \| http://www.scratchbox.org] [LibOSDK Wiki \| http://libosdk.berlios.de/wiki/index.php/Binutils]