<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 08/02/2012 10:59 PM, Kevin Polulak wrote:
<blockquote
cite="mid:CAHRX3kyvcmx0A+R-W5SrAS=z_kwrdp75fiYThaJ5GH2hQcqCMQ@mail.gmail.com"
type="cite">While using the <a moz-do-not-send="true"
href="http://sourceforge.net/projects/rtems-vms/">RTEMS CentOS
image</a> to setup a new development environment on my laptop, I
ran into the missing libmpc dependency error again. I've
encountered this error before and it occurs while trying to
install some of the *-rtems4.11-gcc packages. On my desktop
machine, I had to try and find a copy of libmpc and compile it
from source. If I remember correctly, I think I even had to modify
a few environment variables as well (it might've been <span
style="font-family:courier new,monospace">$LD_LIBRARY_PATH</span>).
Now, on my laptop, I used the <span style="font-family:courier
new,monospace">--skip-broken</span> switch to yum instead and
just hoped it doesn't cause any problems in the future. This kinda
confuses me since the MPC library was included starting with GCC
4.5 and the *-rtems4.11-gcc packages are 4.6.<br>
<br>
</blockquote>
As I mentioned in a private email, recent updates to the RTEMS GCC
binaries <br>
imposed the requirement of libmpc.so.2 which is NOT available in the
CentOS<br>
Repositories installed by default. <br>
<br>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Install the EPEL Repository (<a class="moz-txt-link-freetext" href="http://fedoraproject.org/wiki/EPEL">http://fedoraproject.org/wiki/EPEL</a>) and
when you<br>
do a yum upgrade, it will pick up the libmpc.so.2 RPM dependency and
<br>
magically load it for you.<br>
<br>
FWIW there was no formal announcement about this on the mailing
list.<br>
This dependency was added after I built the last CentOS virtual
machine.<br>
<br>
<blockquote
cite="mid:CAHRX3kyvcmx0A+R-W5SrAS=z_kwrdp75fiYThaJ5GH2hQcqCMQ@mail.gmail.com"
type="cite">What I'm getting at though is, shouldn't stuff like
this be included with the image from the start? That is, shouldn't
the image already have things like libmpc installed? After all,
the description for the image reads "provides preconfigured
Virtual Machines which include an RTEMS Development Environment"
yet there are several things you still need to install.<br>
</blockquote>
Everything was OK in February when that VM was built. The addition
of the<br>
libmpc.so.2 dependency was after that. <br>
<blockquote
cite="mid:CAHRX3kyvcmx0A+R-W5SrAS=z_kwrdp75fiYThaJ5GH2hQcqCMQ@mail.gmail.com"
type="cite">
<br>
For that matter, is there anything wrong with just having <i>all</i>
the RTEMS build tools installed? Sure that's a lot of packages but
after adding up the size of every package containing the word
"rtems", it's only ~1.04 GB. Other than an old copy of the RTEMS
source code and having yum configured to search the RTEMS repos,
there's really not much that makes this an "RTEMS development
environment". Unless I've misunderstood the purpose of the CentOS
image, shouldn't users be able to just boot up the image and be
able to build from source right away for <i>any</i> BSP?<br>
<br>
</blockquote>
It wouldn't have solved this problem. You still wouldn't have been
able to update because<br>
libmpc.so.2 was needed by the newer gcc rpms.<br>
<br>
Also it is easy to add all the tools but not many people will want
them. The VMs are intended<br>
to be useful to get started with. Most people probably will never
want more than 1-3 targets.<br>
We have always recommended some combination of SPARC, x86, PowerPC,
and MIPS for<br>
testing.<br>
<br>
+ SPARC/sis - simulator in gdb, easy to use, matches ERC32<br>
+ pc386 - on qemu, matches PC, has networking and graphics<br>
+ powerpc/psim - standard easy to use PowerPC, in gdb<br>
+ mips/jm43904 - easy to use gdb simulator, no valid memory <
0x88000000 so faults on NULLs<br>
<br>
Those four cover most testing situations which don't require
specific target or HW.<br>
<br>
<blockquote
cite="mid:CAHRX3kyvcmx0A+R-W5SrAS=z_kwrdp75fiYThaJ5GH2hQcqCMQ@mail.gmail.com"
type="cite">As a side note, the bootstrap script fails until a
newer version of autotools in installed. Perhaps it's time the
CentOS image got an update overhaul?<br>
<br>
</blockquote>
I am doing that. But if you added EPEL and did a yum upgrade, it
would just work. That's<br>
all I did. :)<br>
<blockquote
cite="mid:CAHRX3kyvcmx0A+R-W5SrAS=z_kwrdp75fiYThaJ5GH2hQcqCMQ@mail.gmail.com"
type="cite">-- <br>
- Kevin Polulak (soh_cah_toa)<br>
- <a moz-do-not-send="true" href="http://cybercrud.net"
target="_blank">http://cybercrud.net</a><br>
<br>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Joel Sherrill, Ph.D. Director of Research& Development
<a class="moz-txt-link-abbreviated" href="mailto:joel.sherrill@OARcorp.com">joel.sherrill@OARcorp.com</a> On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
</pre>
</body>
</html>