<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
<pre>> env | grep RTEMS
>
> will show all the environment variables related to RTEMS that are set.
> There may be conflicts.
<big>I have no global env vars set other than the addition of RTEMS to my PATH -
all env vars are exported during the make process. (I haven't found any env
vars I'm suppose to be setting documented anywhere.) Even so, env vars
wouldn't - <i>couldn't</i> - correct the problem of the .cfg file locations
being inconsistent - some being in /opt/4.10 and some being in /opt/4.11.
The make process includes most(all?) .cfg files with a path of RTEMS_ROOT.
BTW: my cvs checkout was this " cvs -d :pserver:... co -P rtems ")
</big>
</pre>
<pre>
> On 07/27/2010 12:55 PM, Lisa A. Day wrote:
>> Okay - I thought something like that was going on. However, when I
>> try to copy and compile, for example, examples-v2 in my own dev dir,
>> make is including *.cfg files within RTEMS_ROOT, which is set to
>> /opt/rtems-4.11. But not all the *.cfg files are located there; some
>> are located in /opt/rtems-4.10. I don't understand how I am able to
>> compile the samples in the CVS co directory but not in my own dev dir.
>>
>> For example, tracing 'make:
>>
>> rtems-4.11/make/custom/leon3.cfg includes
>> $(RTEMS_ROOT)/make/custom/default.cfg
>> but default.cfg is in /opt/rtems-4.10/ and it includes
>> $(RTEMS_ROOT)/make/main.cfg
>> where main.cfg is in /opt/rtems-4.11...
>>
> Sounds like more than RTEMS_MAKEFILE_PATH is set in your environment.
>>
>> ??
>> As for the project, I'm finally on it 1/2 time, have a dev board with
>> a vertex-4 FPGA configured as a leon3, and have downloaded and ran a
>> few of your sample apps and also a straight C helloworld app. In the
>> past, I've been focused on embedded app dev for large projects and
>> haven't been exposed to much of the system level stuff, so this
>> project is a great opportunity and I'm learning soooo much - so
>> cool!! thanks for asking :O)
> It is fun to get to do low level things. :)
>
> --joel
>>
>> Joel Sherrill wrote:
>>> On 07/27/2010 11:06 AM, Lisa A. Day wrote:
>>>> Hate to keep bugging you, but I'm desperate...
>>>>
>>>> I found this puzzling: - when I attempted to configure again, I
>>>> looked closer at these lines of output, particularly the
>>>> "configure: running".... on line 14 - it sets the prefix to
>>>> rtems-4.11 -- does this seem
>>> If this is the CVS head, that makes perfect sense. 4.10 has been
>>> branched.
>>>
>>> The CVS head will become 4.11 so we follow the naming that it will
>>> eventually
>>> take. 4.10.99.0 gives us a number > 4.10 but < 4.11 since this
>>> isn't the "real"
>>> 4.11 yet.
>>>
>>> You should be using 4.11 tools with this
>>>
>>> cvs -d :pserver:... co -P rtems
>>>
>>> or 4.10 tools with this:
>>>
>>> cvs -d :pserver:... co -r rtems-4-10-branch -P rtems
>>>
>>> How is the project going otherwise? If you need some consulting
>>> help, that's what I am here for. :)
>>>
>>> --joel
>>>>
>>>> > export PATH=/opt/rtems-4.10/bin:$PATH
>>>> > (I ran ./bootstrap)
>>>> > ../configure --target=sparc-rtems4.10 --enable-rtemsbsp=leon3
>>>> --disable-rtems-inline --disable-itron --enable-tests=samples
>>>> checking for gmake... gmake
>>>> checking for RTEMS Version... 4.10.99.0
>>>> checking build system type... i686-pc-linux-gnu
>>>> checking host system type... i686-pc-linux-gnu
>>>> checking target system type... sparc-unknown-rtems4.10
>>>> checking for a BSD-compatible install... /usr/bin/install -c
>>>> checking whether build environment is sane... yes
>>>> checking for a thread-safe mkdir -p... /bin/mkdir -p
>>>> checking for gawk... gawk
>>>> checking whether gmake sets $(MAKE)... yes
>>>> checking whether to enable maintainer-specific portions of
>>>> Makefiles... no
>>>> configure: creating ./config.status
>>>> configure: configuring in ./tools/build
>>>> configure: running /bin/sh '../../../tools/build/configure'
>>>> '--prefix=/opt/rtems-4.11' '--host=i686-pc-linux-gnu'
>>>> '--build=i686-pc-linux-gnu' '--enable-rtemsbsp=leon3'
>>>> '--disable-rtems-inline' '--disable-itron'
>>>> '--enable-tests=samples' '--target=sparc-rtems4.10'
>>>> '--cache-file=/dev/null' '--srcdir=../../../tools/build'
>>>> checking for gmake... gmake
>>>> checking for RTEMS Version... 4.10.99.0
>>>>
>>>>
>>>> Daron Chabot wrote:
>>>>> Something sure doesn't sound right!
>>>>>
>>>>> Is there a chance that you've set the --prefix=/opt/rtems-4.xx
>>>>> incorrectly when configuring, and some files are installed in the
>>>>> wrong place ?
>>>>>
>>>>> You should never need to touch RTEMS_ROOT; setting
>>>>> RTEMS_MAKEFILE_PATH to /opt/rtems-4.11/sparc-rtems/someBSP is all
>>>>> you need.
>>>>>
>>>>> Since you've built both 4.10 and 4.11, you can switch between
>>>>> building apps for either of the two by appropriately setting
>>>>> RTEMS_MAKEFILE_PATH...
>>>>>
>>>>> HTH.
>>>>>
>>>>> On Mon, Jul 26, 2010 at 5:15 PM, Lisa A. Day <a class="moz-txt-link-rfc2396E" href="mailto:day@lanl.gov"><day@lanl.gov
></a>>>>> <a class="moz-txt-link-rfc2396E" href="mailto:day@lanl.gov"><mailto:day@lanl.gov></a>> wrote:
>>>>>
>>>>> I found at least part of the problem compiling example-v2/hello.
>>>>> My cvs checkout of rtems 4.10 built both /opt/rtems-4.10 and
>>>>> /opt/rtems-4.11directories. FYI, I did a fresh check sometime
>>>>> soon after 4.10 was released and 4.11 became the CVS Mainline; I
>>>>> also checked the CVS build status when I checked it out, and the
>>>>> SPARC was building successfully.
>>>>>
>>>>> However, 'make' in examples-v2/hello is looking for *.cfg files
>>>>> in RTEMS_ROOT, which, based on the make/README file I should set
>>>>> to /opt/rtems-4.11. But some of the necessary .cfg files are
>>>>> located there while others are located in /opt/rtems-4.10. For
>>>>> example, $(RTEMS_ROOT)/make/custom/default.cfg can be found when
>>>>> RTEMS_ROOT is set to /opt/rtems-4.10/ --- but default.cfg
>>>>> includes main.cfg which in /opt/rtems-4.11...
>>>>>
>>>>> Am I describing this clearly? Do I need to do yet another cvs
>>>>> checkout (I attempted a few before I finally got it all right)
>>>>>
>>>>>
>>>>>> Setting RTEMS_ROOT should not be necessary.
>>>>>>
>>>>>> On Mon, Jul 26, 2010 at 11:12 AM, Gedare Bloom
>>>>>> <<a class="moz-txt-link-abbreviated" href="mailto:gedare@gwmail.gwu.edu">gedare@gwmail.gwu.edu</a> <a class="moz-txt-link-rfc2396E" href="mailto:gedare@gwmail.gwu.edu"><mailto:gedare@gwmail.gwu.edu></a>> wrote:
>>>>>>
>>>>>> Are you talking about building standalone apps? If so, you
>>>>>> might try
>>>>>> looking at the examples-v2 CVS repository, which has some
>>>>>> sample
>>>>>> applications that build outside of RTEMS. You still have to
>>>>>> point the
>>>>>> Makefile to the installed/built rtems, by setting the
>>>>>> RTEMS_MAKEFILE_PATH and RTEMS_ROOT environment variables.
>>>>>>
>>>>>> If you build and install RTEMS to
>>>>>> /opt/rtems-4.10/sparc-rtems4.10 then
>>>>>> I think you want:
>>>>>> RTEMS_MAKEFILE_PATH=/opt/rtems-4.10/sparc-rtems4.10/leon3
>>>>>> RTEMS_ROOT=/opt/rtems-4.10
>>>>>>
>>>>>> If you are talking about building the sptests/psxtests etc,
>>>>>> then check
>>>>>> how you configure RTEMS, if you have --enable-tests=samples,
>>>>>> then
>>>>>> configure won't setup the build for the other test
>>>>>> executables.
>>>>>> Instead you just want --enable-tests, which I believe is the
>>>>>> default
>>>>>> option.
>>>>>>
>>>>>> -Gedare
>>>>>>
>>>>>> On Mon, Jul 26, 2010 at 10:57 AM, Lisa A. Day <a class="moz-txt-link-rfc2396E" href="mailto:day@lanl.gov"><day@lanl.gov
></a>>>>>> <a class="moz-txt-link-rfc2396E" href="mailto:day@lanl.gov"><mailto:day@lanl.gov></a>> wrote:
>>>>>> > I'm learning RTEMS (4.10) and have successfully been able
>>>>>> to build, load,
>>>>>> > and run the testsuites/samples programs on my leon3 dev
>>>>>> board without
>>>>>> > problem. However, outside this samples directory, I have
>>>>>> not been able to
>>>>>> > build any of the apps. I don't know if its a Makefile
>>>>>> issue or not... My
>>>>>> > thought is if I could get my hands on one of the
>>>>>> testsuites/samples
>>>>>> > makefiles that is not dependent on the installation dir, I
>>>>>> can make sense of
>>>>>> > where I'm going astray -- CONFIG, environment, or path
>>>>>> issues, etc.
>>>>>> >
>>>>>> > Does anyone have such an example?
>>>>>> >
>>>>>> > --
>>>>>> > ===============================
>>>>>> > Lisa A. Day
>>>>>> > ISR-3: Space Data Systems
>>>>>> > MS D440
>>>>>> > Los Alamos, NM 87545
>>>>>> > (505) 665-4780
>>>>>> >
>>>>>> > _______________________________________________
>>>>>> > rtems-users mailing list
>>>>>> > <a class="moz-txt-link-abbreviated" href="mailto:rtems-users@rtems.org">rtems-users@rtems.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:rtems-users@rtems.org"><mailto:rtems-users@rtems.org></a>
>>>>>> > <a class="moz-txt-link-freetext" href="http://www.rtems.org/mailman/listinfo/rtems-users">http://www.rtems.org/mailman/listinfo/rtems-users</a>
>>>>>> >
>>>>>>
>>>>>> _______________________________________________
>>>>>> rtems-users mailing list
>>>>>> <a class="moz-txt-link-abbreviated" href="mailto:rtems-users@rtems.org">rtems-users@rtems.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:rtems-users@rtems.org"><mailto:rtems-users@rtems.org></a>
>>>>>> <a class="moz-txt-link-freetext" href="http://www.rtems.org/mailman/listinfo/rtems-users">http://www.rtems.org/mailman/listinfo/rtems-users</a>
>>>>>>
>>>>>>
>>>>>
>>>>> -- ===============================
>>>>> Lisa A. Day
>>>>> ISR-3: Space Data Systems
>>>>> MS D440
>>>>> Los Alamos, NM 87545
>>>>> (505) 665-4780
>>>>>
>>>>>
>>>>
>>>> --
>>>> ===============================
>>>> Lisa A. Day
>>>> ISR-3: Space Data Systems
>>>> MS D440
>>>> Los Alamos, NM 87545
>>>> (505) 665-4780
>>>
>>>
>>
>> --
>> ===============================
>> Lisa A. Day
>> ISR-3: Space Data Systems
>> MS D440
>> Los Alamos, NM 87545
>> (505) 665-4780
>>
>
>
--
===============================
Lisa A. Day
ISR-3: Space Data Systems
MS D440
Los Alamos, NM 87545
(505) 665-4780
</pre>
<br>
<pre class="moz-signature" cols="72">--
===============================
Lisa A. Day
ISR-3: Space Data Systems
MS D440
Los Alamos, NM 87545
(505) 665-4780
</pre>
</body>
</html>