Re: Problem building cparos tools.
Kitty Guy <kittyguy <at> mail.be>
2012-09-05 15:12:27 GMT
"Jonathan S. Shapiro" <shap <at> eros-os.org> wrote:
> On Wed, Sep 5, 2012 at 7:16 AM, Kitty Guy <kittyguy <at> mail.be> wrote:
>
> Hello,
>
> Thanks for your quick reply.
>
> "Jonathan S. Shapiro" <shap <at> eros-os.org> wrote:
> > Kitty:
> > 1. The process for building these tools is delicate, and (at this time) really only works if you proceed by
rebuilding the RPMs.
>
> That could take care of the symlinks. The build errors will obviously remain even when built as RPM.
>
> The right solution, really, is to refresh the entire cross-tool chain. That is likely a week-long effort,
and I don't have the time to do it.
I expect some of the issues would be fixed by updating to current versions of binutils and gdb.
> I was able to run the hello world demo of capros (built with capros tools) but coyotos fails linking any
native binaries.
>
> There could be two reasons for this. It sounds like your build of the tool chain may not have been as
intended. But even if there were no tool chain problems, you would hit a problem with your first use of the
coyotos capidl tool. I was in the middle of a rework of capidl when the project was mothballed. The changes
to capidl were never completed.
>
> The first problem is that the coyotos binaries have unresolved symbols to the kernel and other binaries
which the linker does not like.
>
> They can't have unresolved symbols to the kernel or other binaries. I believe the unresolved symbols are
the ones that would have been the output from capidl. Adding the '-r' flag is definitely not what you want.
Yes, I expected that there would be some library to provide the symbols but did not find any.
> Concerning the image builder, I would need to look at the specific input case.
> The coyotos project has been mothballed. There is nobody working on it at this time, and the tool chains
have not been brought forward to run on current versions of Fedora. I don't have the time to bring them
forward, so I'm afraid you may be out of luck here.
The files are what is in the tree.
Since capidl is broken the input is bogus. I am not surprised building the image fails.
Cheers
kg
-----------------------------------------------------
Mail.be, WebMail and Virtual Office
http://www.mail.be
"Jonathan S. Shapiro" <shap <at> eros-os.org> wrote:On Wed, Sep 5, 2012 at 7:16 AM, Kitty Guy
<kittyguy <at> mail.be> wrote:
Hello,
Thanks for your quick reply.
"Jonathan S. Shapiro" <shap <at> eros-os.org> wrote:
> Kitty:
> 1. The process for building these tools is delicate, and (at this time) really only works if you proceed by
rebuilding the RPMs.
That could take care of the symlinks. The build errors will obviously remain even when built as RPM.
The right solution, really, is to refresh the entire cross-tool chain. That is likely a week-long effort,
and I don't have the time to do it. > 2. The coyotos and capros tool chains really are not the same. The
coyotos tools implement compilation models that the capros tools do not.
> 3. Trying to build capros using the coyotos tool chain won't work.
Then hardcoding the tool prefix is not that much of an issue I guess.
There were reasons to do so. It turns out that building GCC with a relocatable prefix is not
straightforward. Or at least it wasn't straightforward on those versions of GCC.
It actually is possible to build with a different prefix. The problem you are running into is that the
"build your own" option in ccs-xenv was only briefly used by a few people running BSD, and was not actively
maintained. I was able to run the hello world demo of capros (built with capros tools) but coyotos fails
linking any native binaries.
There could be two reasons for this. It sounds like your build of the tool chain may not have been as intended.
But even if there were no tool chain problems, you would hit a problem with your first use of the coyotos
capidl tool. I was in the middle of a rework of capidl when the project was mothballed. The changes to capidl
were never completed.
The first problem is that the coyotos binaries have unresolved symbols to the kernel and other binaries
which the linker does not like.
They can't have unresolved symbols to the kernel or other binaries. I believe the unresolved symbols are
the ones that would have been the output from capidl. Adding the '-r' flag is definitely not what you want.
Concerning the image builder, I would need to look at the specific input case.
The coyotos project has been mothballed. There is nobody working on it at this time, and the tool chains have
not been brought forward to run on current versions of Fedora. I don't have the time to bring them forward,
so I'm afraid you may be out of luck here.
Jonathan
------=_Part_59855_15862498.1346857334726
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<HTML><HEAD></HEAD><BODY>"Jonathan S. Shapiro" <shap <at> eros-os.org>
wrote:<BLOCKQUOTE type="cite"
cite="<CAAP=3QPMpxvhnB44YTWXoyJYM5rV8tK5O-h4FMkBkCRU0BX3-w <at> mail.gmail.com>"><DIV><DIV
class="gmail_quote">On Wed, Sep 5, 2012 at 7:16 AM, Kitty Guy <SPAN dir="ltr"><<A
href="mailto:kittyguy <at> mail.be" target="_blank">kittyguy <at> mail.be</A>></SPAN>
wrote:<BR><BLOCKQUOTE class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<BR>
<BR>
Thanks for your quick reply.<BR>
<DIV class="im"><BR>
"Jonathan S. Shapiro" <<A href="mailto:shap <at> eros-os.org">shap <at> eros-os.org</A>> wrote:<BR>
> Kitty:<BR>
> 1. The process for building these tools is delicate, and (at this time) really only works if you proceed
by rebuilding the RPMs.<BR>
<BR>
</DIV>That could take care of the symlinks. The build errors will obviously remain even when built as
RPM.<BR></BLOCKQUOTE><DIV><BR></DIV><DIV>The right solution, really, is to refresh the entire
cross-tool chain. That is likely a week-long effort, and I don't have the time to do it.</DIV>
<DIV> </DIV><BLOCKQUOTE class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<DIV class="im">> 2. The coyotos and capros tool chains really are not the same. The coyotos tools
implement compilation models that the capros tools do not.<BR>
> 3. Trying to build capros using the coyotos tool chain won't work.<BR>
<BR>
</DIV>Then hardcoding the tool prefix is not that much of an issue I
guess.<BR></BLOCKQUOTE><DIV><BR></DIV><DIV>There were reasons to do so. It turns out that building
GCC with a relocatable prefix is not straightforward. Or at least it wasn't straightforward on those
versions of GCC.</DIV>
<DIV><BR></DIV><DIV>It actually <I>is</I> possible to build with a different prefix. The
problem you are running into is that the "build your own" option in ccs-xenv was only briefly
used by a few people running BSD, and was not actively maintained.</DIV>
<DIV> </DIV><BLOCKQUOTE class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">I was able to run the hello world demo of capros (built with capros tools) but
coyotos fails linking any native binaries.<BR>
</BLOCKQUOTE><DIV><BR></DIV><DIV>There could be two reasons for this. It sounds like your build of the
tool chain may not have been as intended. But even if there were no tool chain problems, you would hit a
problem with your first use of the coyotos capidl tool. I was in the middle of a rework of capidl when the
project was mothballed. The changes to capidl were never completed.</DIV>
<DIV><BR></DIV><BLOCKQUOTE class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">The first problem is that the coyotos binaries have unresolved symbols to the
kernel and other binaries which the linker does not like.<BR>
</BLOCKQUOTE><DIV><BR></DIV><DIV>They <I>can't</I> have unresolved symbols to the
kernel or other binaries. I believe the unresolved symbols are the ones that would have been the output
from capidl. Adding the '-r' flag is definitely not what you want.</DIV>
<DIV><BR></DIV><DIV>Concerning the image builder, I would need to look at the specific input
case.</DIV><DIV><BR></DIV><DIV><BR></DIV><DIV>The coyotos project has been mothballed. There is
nobody working on it at this time, and the tool chains have not been brought forward to run on current
versions of Fedora. I don't have the time to bring them forward, so I'm afraid you may be out of luck here.</DIV>
<DIV><BR></DIV><DIV><BR></DIV><DIV>Jonathan</DIV></DIV><BR></DIV>
</BLOCKQUOTE></BODY></HTML>
------=_Part_59855_15862498.1346857334726--
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
CapROS-devel mailing list
CapROS-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/capros-devel
RSS Feed