Hello,
Thanks for your quick reply.
"Jonathan S. Shapiro" <[email protected]> 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.
> 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.
I was able to run the hello world demo of capros (built with capros tools) but
coyotos fails linking any native binaries.
The first problem is that the coyotos binaries have unresolved symbols to the
kernel and other binaries which the linker does not like.
I tried adding the -r flag like this:
$(BUILDDIR)/Constructor: $(OBJECTS)
- $(GCC) -small-space $(GPLUSFLAGS) $(OBJECTS) $(LIBS) $(STDLIBDIRS) -o $@
+ $(GCC) -small-space $(GPLUSFLAGS) $(OBJECTS) $(LIBS) $(STDLIBDIRS) -r
-o $@
The other problem is that the image builder does not like the image
descriptions which is something I cannot work around because I have no idea
about these. Maybe looking at the spec in more detail would help. Anyway, the
error:
make[6]: Entering directory `/home/kg/coyotos/src/base/test/bring-up/Handler'
/home/kg/coyotos/host/bin/mkimage -t i386 -o
BUILD/i386-unknown-coyotos/Handler.img -I. -LBUILD/i386-unknown-coyotos --MD
--MF BUILD/i386-unknown-coyotos/.Handler.img.m -f Handler.mki
/home/kg/coyotos/usr/include/mki/coyotos/Util.mki:54:8 Inappropriate capability
type to get_l2g()
get_l2g(0x8558e40) at /home/kg/coyotos/usr/include/mki/coyotos/Util.mki:54:8
==(...) at /home/kg/coyotos/usr/include/mki/coyotos/Util.mki:54:29
load_small_image(0x853afd0, 0x85383f0, 0x853b160) at Handler.mki:28:22
make_ironman_process(0x853afd0, 0x85383f0, 0x853b160) at Handler.mki:36:17
Cheers
kg
-----------------------------------------------------
Mail.be, WebMail and Virtual Office
http://www.mail.be
"Jonathan S. Shapiro" <[email protected]> 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.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.
Jonathan
On Wed, Sep 5, 2012 at 3:57 AM, Kitty Guy <[email protected]> wrote:
Hello,
I tried building capros but the current cross-tools won't build.
I applied some patches to get the tools built:
https://bitbucket.org/kittyguy/ccs-xenv/changesets
There are still some problems. Once the configure in coytools would fail all
tests with sed complaining it cannot open conftest.c. After poking around to
find what the problem was it went away and I cannot reproduce it anymore.
Another issue is that the coyotos linker scripts are installed in a wrong place
and ld does not link any of the capros binaries because it would not find them.
Needed some symlinks to make the script usable:
$ readlink /capros/host/lib/ldscripts/elf_i386_coyotos_small.xc
../../i386-unknown-capros/lib/ldscripts/elf_i386_coyotos_small.xc
Finally it is quite stupid that the coyotos and capros build systems insist on
having each a copy of the same tools under a different name. I tried to use
tools build with the default coyotos prefix but the SSL binary would not build.
Settling on one name would save quite a bit of disk space.
Cheers
kg
-----------------------------------------------------
Mail.be, WebMail and Virtual Office
http://www.mail.be
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/capros-devel
------=_Part_58350_7430103.1346853357346
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<HTML><HEAD></HEAD><BODY>"Jonathan S. Shapiro"
<[email protected]> wrote:<BLOCKQUOTE type="cite"
cite="<CAAP=3qmwnhck-srhjcv1qlz9ouvfjjdqk8-kzqg30-vxweg...@mail.gmail.com>"><DIV
class="gmail_quote">Kitty:</DIV><DIV class="gmail_quote"><BR></DIV><DIV
class="gmail_quote">1. The process for building these tools is delicate, and
(at this time) really only works if you proceed by rebuilding the RPMs.</DIV>
<DIV class="gmail_quote">2. The coyotos and capros tool chains really are not
the same. The coyotos tools implement compilation models that the capros tools
do not.</DIV><DIV class="gmail_quote">3. Trying to build capros using the
coyotos tool chain won't work.</DIV>
<DIV class="gmail_quote"><BR></DIV><DIV class="gmail_quote"><BR></DIV><DIV
class="gmail_quote">Jonathan</DIV><DIV class="gmail_quote"><BR></DIV><DIV
class="gmail_quote">On Wed, Sep 5, 2012 at 3:57 AM, Kitty Guy <SPAN
dir="ltr"><<A href="mailto:[email protected]";
target="_blank">[email protected]</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>
I tried building capros but the current cross-tools won't build.<BR>
<BR>
I applied some patches to get the tools built: <A
href="https://bitbucket.org/kittyguy/ccs-xenv/changesets";
target="_blank">https://bitbucket.org/kittyguy/ccs-xenv/changesets</A><BR>
<BR>
There are still some problems. Once the configure in coytools would fail all
tests with sed complaining it cannot open conftest.c. After poking around to
find what the problem was it went away and I cannot reproduce it anymore.<BR>
<BR>
Another issue is that the coyotos linker scripts are installed in a wrong place
and ld does not link any of the capros binaries because it would not find them.
Needed some symlinks to make the script usable:<BR>
<BR>
$ readlink /capros/host/lib/ldscripts/elf_i386_coyotos_small.xc<BR>
../../i386-unknown-capros/lib/ldscripts/elf_i386_coyotos_small.xc<BR>
<BR>
Finally it is quite stupid that the coyotos and capros build systems insist on
having each a copy of the same tools under a different name. I tried to use
tools build with the default coyotos prefix but the SSL binary would not build.
Settling on one name would save quite a bit of disk space.<BR>
<BR>
Cheers<BR>
<BR>
kg<BR>
-----------------------------------------------------<BR>
Mail.be, WebMail and Virtual Office<BR>
<A href="http://www.mail.be"; target="_blank">http://www.mail.be</A><BR>
<BR>
------------------------------------------------------------------------------<BR>
Live Security Virtual Conference<BR>
Exclusive live event will cover all the ways today's security and<BR>
threat landscape has changed and how IT managers can respond. Discussions<BR>
will include endpoint security, mobile security and the latest in malware<BR>
threats. <A href="http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/";
target="_blank">http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/</A><BR>
_______________________________________________<BR>
CapROS-devel mailing list<BR>
<A
href="mailto:[email protected]";>[email protected]</A><BR>
<A href="https://lists.sourceforge.net/lists/listinfo/capros-devel";
target="_blank">https://lists.sourceforge.net/lists/listinfo/capros-devel</A><BR>
<BR>
</BLOCKQUOTE></DIV><BR>
</BLOCKQUOTE></BODY></HTML>
------=_Part_58350_7430103.1346853357346--
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/capros-devel
