Closedjeremybennett opened this issue almost 15 years ago
jeremybennett commented almost 15 years ago
<p>
The standard tool installation script has an include directory for all the headers for the GNU tool chain.
</p>
<p>
However the script also builds Or1ksim, which includes a header for those using it in library form, which goes into the same include directory.
</p>
<p>
This then causes serious problems when trying to use the Or1ksim library, since specifying this as an include directory will cause all the standard C library function headers to also be picked up from there.
</p>
<p>
However these are the headers to match GCC 4.2.2 from the Or1ksim tools distribution, and will not generally be identical to the host workstation's headers.
</p>
<p>
The solution is that the Or1ksim application should be installed in a <em>separate</em> directory to that used for the tool chain.
</p>
<p>
Jeremy
</p>
<p>
-- <br />
Tel: +44 (1590) 610184<br />
Cell: +44 (7970) 676050<br />
SkypeID: jeremybennett<br />
Email: <a href="mailto:jeremy.bennett@embecosm.com">jeremy.bennett@embecosm.com</a><br />
Web: <a href="http://www.embecosm.com">www.embecosm.com</a>
</p>
julius was assigned almost 15 years ago
julius commented almost 15 years ago
Ok, script has been updated so that or1ksim is installed in its own path parallel to the or32-elf path in the chosen install directory. A directory with the version suffix is symlinked to a directory just called or1ksim.