Compiling newlib

Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
Post Reply
asdftyui
Posts: 3
Joined: Tue Feb 21, 2012 7:41 am

Compiling newlib

Post by asdftyui »

I followed the gcc cross-compiler tutorial and went to the porting newlib. Everything worked fine till I tried compiling it by issuing

Code: Select all

make all install 
when I got the following error:

Code: Select all

WARNING: `makeinfo' is missing on your system.  You should only need it if
         you modified a `.texi' or `.texinfo' file, or any other file
         indirectly affecting the aspect of the manual.  The spurious
         call might also be the consequence of using a buggy `make' (AIX,
         DU, IRIX).  You might want to install the `Texinfo' package or
         the `GNU make' package.  Grab either from any GNU archive site.
and the compilation stops.
I am using Ubuntu 11.10.
I have tried:
-using different gcc, binutils and newlib versions (about 5 different combinations)
-installing Texinfo
-correcting makeinfo path
My cross-compiler works perfectly without the newlib just that it of course cannot include the libraries.
User avatar
Solar
Member
Member
Posts: 7615
Joined: Thu Nov 16, 2006 12:01 pm
Location: Germany
Contact:

Re: Compiling newlib

Post by Solar »

This might help.
Every good solution is obvious once you've found it.
asdftyui
Posts: 3
Joined: Tue Feb 21, 2012 7:41 am

Re: Compiling newlib

Post by asdftyui »

What do I need to do with the PDClib?
And thank you for making the effort to reply to my post.
Please do help me more as I have been struggling with this for a long time.
User avatar
Solar
Member
Member
Posts: 7615
Joined: Thu Nov 16, 2006 12:01 pm
Location: Germany
Contact:

Re: Compiling newlib

Post by Solar »

asdftyui wrote:What do I need to do with the PDClib?
  • Go to website.
  • Find and use download link (or SVN link if you prefer trunk over v0.5).
  • Unpack.
  • Read "README.txt".
It's all in there. Really.
Every good solution is obvious once you've found it.
Post Reply