<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body>
<pre style="word-wrap:break-word; font-size:10.0pt; font-family:Tahoma; color:black">Stupid questions...
Are you doing the echo $PATH in the same window based the configure?
Can you compile a simple empty main() {} with sparc-rtems4.11-gcc?
Is there a more detailed message on config.log?
--joel
manish jain <manish8886@gmail.com> wrote:
</pre>
<div>Hi,<br>
My $PATH is<br>
/opt/rtems-4.11/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
<br>
<br>
<br>
And I do have various binaries in /opt/rtems-4.11/bin like:<br>
sparc-rtems4.11-gcc <br>
sparc-rtems4.11-gcc-4.7.2<br>
sparc-rtems4.11-gcc-ar<br>
sparc-rtems4.11-gcc-nm<br>
sparc-rtems4.11-gcc-ranlib<br>
<br>
<br>
<div class="gmail_quote">On Fri, Feb 8, 2013 at 9:54 PM, Gedare Bloom <span dir="ltr">
<<a href="mailto:gedare@rtems.org" target="_blank">gedare@rtems.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p>What do you get to from:<br>
echo $PATH<br>
which sparc-rtems4.11-gcc</p>
<div class="HOEnZb">
<div class="h5">
<div class="gmail_quote">On Feb 8, 2013 9:41 PM, "manish jain" <<a href="mailto:manish8886@gmail.com" target="_blank">manish8886@gmail.com</a>> wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
No that didn't also work<br>
<br>
<br>
<b>checking for style of include used by make... GNU<br>
checking for sparc-rtems4.11-gcc... no<br>
configure: error: no acceptable cc found in $PATH<br>
make[2]: *** [sis] Error 1<br>
make[2]: Leaving directory `/home/manish/tools/b-rtems/sparc-rtems4.11/c'<br>
make[1]: *** [all-recursive] Error 1<br>
make[1]: Leaving directory `/home/manish/tools/b-rtems/sparc-rtems4.11/c'<br>
</b><br>
I checked the path /opt/rtem-4.11 has sparc-rtems4.11-gcc.<br>
<br>
Is there might be problem in configuring the rtems project. I first did ./bootstrap from rtems source directory and then configure the rtems and tried to build it.<br>
<br>
Thanks<br>
Manish<br>
<br>
<div class="gmail_quote">On Fri, Feb 8, 2013 at 10:16 AM, Gedare Bloom <span dir="ltr">
<<a href="mailto:gedare@rtems.org" target="_blank">gedare@rtems.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p>4.11 currently refers to the development head, or master. There is no 4.11 branch at the moment. Try the master branch.</p>
<p>The tools are specific to rtems version, so 4.11 tools will not build rtems 4.10.x<span><font color="#888888"><br>
-Gedare</font></span></p>
<div>
<div>
<div class="gmail_quote">On Feb 8, 2013 4:57 AM, "manish jain" <<a href="mailto:manish8886@gmail.com" target="_blank">manish8886@gmail.com</a>> wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi All,<br>
Thanks for all your suggestions. The problem was, library cache was not updated. Now I have successfully built my tool chains for rtems-4.11.
<br>
But now I am facing problem in building the RTEMS itself. <br>
I have built my tool set for rtems-4.11 but I am not able to find RTEMS-4.11 source code in git repository and CVS. All I see is that most current version is rtems.4.10.2. So I downloaded the code for rtems-4.10.2 and tried to build it.<br>
<br>
I am configuring the rtems with following command:<br>
<br>
<b> ../rtems-4.10.2/configure --target=sparc-rtems4.11 --enable-rtemsbsp=sis --disable-posix --disable-networking --disable-cxx --prefix=/opt/rtems-4.11<br>
</b><br>
And the error I got when I do make all is following:<br>
<br>
<b>configure: error: no acceptable cc found in $PATH<br>
make[2]: *** [sis] Error 1<br>
</b><br>
Actually after getting the error I saw "<b>{build-dir/sparc-rtems4.11/c/sis/config.log}</b>" and problem was that in PATH: it is not including "/opt/rtems-4.11/bin" but in
<b>"{build-dir/sparc-rtems4.11/c/config.log}</b>" the PATH variable is proper. <br>
<br>
And my PATH variable is set to : <b>/opt/rtems-4.11/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games</b><br>
<br>
I have looked the previous mails regarding this problem and most common cause of this error was PATH variable but I think my PATH variable is proper. I am not able to figure out why it is happening?<br>
<br>
Thanks<br>
Manish<br>
<br>
<br>
<br>
<br>
<div class="gmail_quote">On Thu, Feb 7, 2013 at 10:19 AM, Steven Grunza <span dir="ltr">
<<a href="mailto:sgrunza@ctdi.com" target="_blank">sgrunza@ctdi.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>
> -----Original Message-----<br>
> From: <a href="mailto:rtems-users-bounces@rtems.org" target="_blank">rtems-users-bounces@rtems.org</a> [mailto:<a href="mailto:rtems-users-" target="_blank">rtems-users-</a><br>
> <a href="mailto:bounces@rtems.org" target="_blank">bounces@rtems.org</a>] On Behalf Of Gedare Bloom<br>
> Sent: Thursday, February 07, 2013 9:52 AM<br>
> To: manish jain<br>
> Cc: RTEMS<br>
> Subject: Re: Error while building gcc for toolset for RTEMS<br>
><br>
> Aside from the (relatively useful) advice that you may want to try<br>
> the prepackaged solutions, if you continue with building your own<br>
> tools you may want to check that mpc/gmp/mpfr are being found. If<br>
> you built/installed them separately from GCC then you need to add<br>
> the install point to your library path, e.g. export<br>
> LD_LIBRARY_PATH=${PREFIX}/lib:${LD_LIBRARY_PATH} for PREFIX equal<br>
> to where you installed those libraries. If you are using a single-<br>
</div>
> tree build where you link the source for those libraries, then gcc<br>
<div>> should find them itself. The error you sent is indicative of a<br>
> missing library.<br>
><br>
<br>
</div>
If you continue on the path of building your own tools, the command<br>
"ldconfig -p" is your friend. This command will show you all the<br>
libraries known and cached. If you installed a library from source and<br>
don't see it listed, you may need to run "ldconfig" as root to update<br>
the cache. I've mostly seen this out-of-date ld.so cache problem on<br>
Fedora/CentOS systems but it can't hurt to check.<br>
</blockquote>
</div>
<br>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>