Error while building gcc for toolset for RTEMS

[manish jain]

Hi Joel,
I am able to compile with sparc-rtems-4.11 and I think my PATH variable is
also working.
But I dunno why configuration file for  *"{Build-Dir}/sparc-rtems4.11/c/sis/"
*is not showing "/opt/rtems-4.11/bin"in it's PATH variables.
I am attaching this config(in which errors are coming) with this mail for
your reference.

But the surprised thing is that the same PATH values are recognizable in *
"{Build-Dir}/sparc-rtems4.11/config.log"*  which is generating the above
log.

On Fri, Feb 8, 2013 at 10:17 PM, Joel Sherrill <Joel.Sherrill at oarcorp.com>wrote:

>  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 at gmail.com> wrote:
>
>
> Hi,
> My $PATH is
> /opt/rtems-4.11/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
>
>
>
> And I do have various binaries in /opt/rtems-4.11/bin like:
> sparc-rtems4.11-gcc
> sparc-rtems4.11-gcc-4.7.2
> sparc-rtems4.11-gcc-ar
> sparc-rtems4.11-gcc-nm
> sparc-rtems4.11-gcc-ranlib
>
>
> On Fri, Feb 8, 2013 at 9:54 PM, Gedare Bloom <gedare at rtems.org> wrote:
>
>> What do you get to from:
>> echo $PATH
>> which sparc-rtems4.11-gcc
>>  On Feb 8, 2013 9:41 PM, "manish jain" <manish8886 at gmail.com> wrote:
>>
>>> No that didn't also work
>>>
>>>
>>> *checking for style of include used by make... GNU
>>> checking for sparc-rtems4.11-gcc... no
>>> configure: error: no acceptable cc found in $PATH
>>> make[2]: *** [sis] Error 1
>>> make[2]: Leaving directory `/home/manish/tools/b-rtems/sparc-rtems4.11/c'
>>> make[1]: *** [all-recursive] Error 1
>>> make[1]: Leaving directory `/home/manish/tools/b-rtems/sparc-rtems4.11/c'
>>> *
>>> I checked the path /opt/rtem-4.11 has sparc-rtems4.11-gcc.
>>>
>>> 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.
>>>
>>> Thanks
>>> Manish
>>>
>>> On Fri, Feb 8, 2013 at 10:16 AM, Gedare Bloom <gedare at rtems.org> wrote:
>>>
>>>> 4.11 currently refers to the development head, or master. There is no
>>>> 4.11 branch at the moment. Try the master branch.
>>>>
>>>> The tools are specific to rtems version, so 4.11 tools will not build
>>>> rtems 4.10.x
>>>> -Gedare
>>>>  On Feb 8, 2013 4:57 AM, "manish jain" <manish8886 at gmail.com> wrote:
>>>>
>>>>> Hi All,
>>>>> 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.
>>>>> But now I am facing problem in building the RTEMS itself.
>>>>> 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.
>>>>>
>>>>>  I am configuring the rtems with following command:
>>>>>
>>>>> * ../rtems-4.10.2/configure --target=sparc-rtems4.11
>>>>> --enable-rtemsbsp=sis --disable-posix --disable-networking --disable-cxx
>>>>> --prefix=/opt/rtems-4.11
>>>>> *
>>>>> And the error I got when I do make all is following:
>>>>>
>>>>> *configure: error: no acceptable cc found in $PATH
>>>>> make[2]: *** [sis] Error 1
>>>>> *
>>>>> Actually after getting the error I saw  "*
>>>>> {build-dir/sparc-rtems4.11/c/sis/config.log}*" and problem was that
>>>>> in PATH: it is not including "/opt/rtems-4.11/bin"  but in *
>>>>> "{build-dir/sparc-rtems4.11/c/config.log}*" the PATH variable is
>>>>> proper.
>>>>>
>>>>> And my PATH variable is set to : *
>>>>> /opt/rtems-4.11/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
>>>>> *
>>>>>
>>>>> 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?
>>>>>
>>>>> Thanks
>>>>> Manish
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Feb 7, 2013 at 10:19 AM, Steven Grunza <sgrunza at ctdi.com>wrote:
>>>>>
>>>>>>
>>>>>> > -----Original Message-----
>>>>>> > From: rtems-users-bounces at rtems.org [mailto:rtems-users-
>>>>>> > bounces at rtems.org] On Behalf Of Gedare Bloom
>>>>>> > Sent: Thursday, February 07, 2013 9:52 AM
>>>>>> > To: manish jain
>>>>>> > Cc: RTEMS
>>>>>> > Subject: Re: Error while building gcc for toolset for RTEMS
>>>>>> >
>>>>>> > Aside from the (relatively useful) advice that you may want to try
>>>>>> > the prepackaged solutions, if you continue with building your own
>>>>>> > tools you may want to check that mpc/gmp/mpfr are being found. If
>>>>>> > you built/installed them separately from GCC then you need to add
>>>>>> > the install point to your library path, e.g. export
>>>>>> > LD_LIBRARY_PATH=${PREFIX}/lib:${LD_LIBRARY_PATH} for PREFIX equal
>>>>>> > to where you installed those libraries. If you are using a single-
>>>>>>  > tree build where you link the source for those libraries, then gcc
>>>>>> > should find them itself. The error you sent is indicative of a
>>>>>> > missing library.
>>>>>> >
>>>>>>
>>>>>>  If you continue on the path of building your own tools, the command
>>>>>> "ldconfig -p" is your friend.  This command will show you all the
>>>>>> libraries known and cached.  If you installed a library from source
>>>>>> and
>>>>>> don't see it listed, you may need to run "ldconfig" as root to update
>>>>>> the cache.  I've mostly seen this out-of-date ld.so cache problem on
>>>>>> Fedora/CentOS systems but it can't hurt to check.
>>>>>>
>>>>>
>>>>>
>>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20130208/1798b10e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.log
Type: application/octet-stream
Size: 8751 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/users/attachments/20130208/1798b10e/attachment-0001.obj>