<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 8/22/2012 12:36 PM, Claas Ziemke
wrote:<br>
</div>
<blockquote cite="mid:DUB115-W1283E04611D2DCA9C153BC3BEBF0@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}</style>i have a little problem here... the master branch of rtems
moved on to<br>
<div dir="ltr">
autoconf 2.69 which means i can only build rtems after i rebuild
the whole<br>
toolchain. and that is only a couple of days before deadline.<br>
</div>
</blockquote>
<br>
Yeah, your GitHub fork is probably out of sync with git.rtems.org.
Let me guess, your origin fetch URL is git.rtems.org/rtems.git but
the origin push URL is your github.com/class/rtems.git remote repo?
I've had that bite me in the ass several times. ;)<br>
<br>
If you're using the CentOS image, just update all your packages with
PackageKit (gpk-application) or YUM. I think all you really need is
the rtems-4.11-autoconf and rtems-4.11-automake packages and maybe
the libtool package too. I just updated everything anyway for good
measure and the plethora of error message disappeared.<br>
<br>
I brought up the exact same thing a while ago and I'm pretty sure
Joel said he's working on updating the CentOS image so that Autoconf
doesn't kick anybody out from under their feet anymore.<br>
<br>
<div class="moz-signature">-- <br>
- Kevin Polulak (soh_cah_toa) <br>
- <a href="http://cybercrud.net">http://cybercrud.net</a></div>
</body>
</html>