Talk:Porting Newlib

From OSDev Wiki
Jump to: navigation, search



Really? 'Neutral'? For something to be neutral, I was under the impression that there had to be a disagreement about it. How, by any meaning of the word, is using 'Genesis' not appropriate as a synonym for 'Beginning'? Moreover, in DMA, using Genesis makes the article a little more together due to it's style. I should say it's perfectly acceptable. Such edits seem to cause quite the opposite of the intent. --Alboin

How is using a religious terminology at all related to what we do on this site? I made sure that my choice of words were clear and descriptive. "Genesis" might not be very clear to non-English speaking Wiki browsers. Change it back if you disagree. I personally think the DMA article and any others should not contain such "speculative" information, Audits anyone? ;-) --Brynet-Inc 18:15, 16 September 2007 (CDT)

The DMA article is written like it is a bible story, so it should be Genesis. It fits, and it works. Non-English speakers should have some idea of what Genesis means (the bible is the most read book, after all). I don't see any offence towards non-Christians, either. It's a humourous reference, not like it's being preached. On the other hand, in Porting Newlib, it should be Preparation. It's not Genesis, it doesn't fit, and it's not at the beginning. Yayyak 18:33, 16 September 2007 (CDT)

Preparation does not fit the chapter either, so I took the liberty to change it to "Compiling" (basically, the preparation is done in the support calls section, all you are doing within that chapter is configuring and compiling newlib). - Combuster 15:09, 17 September 2007 (CDT)

should we have like a see also thing? cause I found which has some nice info about porting newlib to a very minimal OS(and how to cope with such things as lack of filesystem) --Earlz 15:17, 1 June 2009 (UTC)

Building newlib with ARM cross-compiler on Fedora 10

To get this to work, I had to apply the patch at, see the attachment to the second message, from Nick Clifton. On Fedora, I couldn't easily get patch to figure out what to do with it, possibly because of my inexperience using patch or my general laziness. It's a simple fix and easy enough to apply by hand. Then newlib built for me.

The rest of the toolchain went together using a procedure modified slightly from the GCC Cross-Compiler page, and appears to have built and installed correctly.

sudo mkdir /usr/local/arm-elf
export PREFIX=/usr/local/arm-elf
export TARGET=arm-elf
cd build-binutils/
../binutils-2.20/configure --target=$TARGET --prefix=$PREFIX --disable-nls
make all
sudo make install
cd ../build-gcc
ls ..
export PATH=$PATH:$PREFIX/bin
../gcc-4.3.2/configure --target=$TARGET --prefix=$PREFIX --disable-nls \
          --enable-languages=c,c++ --without-headers
make all-gcc
sudo make install-gcc

-- Willware 05:31, 1 November 2009 (UTC)

Automake 1.14 ?

Since Cygnus style trees was removed from automake after release 1.12, recommend to use automake 1.14 to build newlib should fail ? At least, it fail on my distro (Fedora 23) with autoconf 2.68 (latest newlib 26/2/16) and automake 1.14.

Hack at end

In the section where it shows making all those symbolic links, wouldn't it make more sense to build a first pass OS toolchain, the port Newlib, and then build a second pass toolchain? That's how I'm doing it. -- Nexos

Personal tools