[coyotos-dev] New binutils, gcc, crtfiles, newlib

[Jonathan S. Shapiro]

Sam:

I think I know what is happening, but I'm not going to be able to
address this tonight. The server rotation needs to be completed by
tomorrow AM, and until the domain name changes propagate at verio there
won't be a reliable way to get an update into the tree that you can
retrieve.

shap


On Fri, 2008-04-11 at 23:44 +0100, Sam Mason wrote:
> On Tue, Apr 08, 2008 at 04:16:11AM -0400, Jonathan S. Shapiro wrote:
> > I have just pushed a major update to the cross tools, primarily for
> > coldfire, but I updated newlib and gcc as well.
> > 
> > Those of you who are building by hand will need to rebuild your ccs-xenv
> > cross tools tree more or less completely. I *think* that I updated the
> > hand-build makefile correctly, but I have not tested that.
> 
> I've just tried rebuilding everything and the xenv build all went very
> smoothly.  I'm just having trouble building the test images now, I get a
> strange error from coymerge that I don't understand.  The errors seem to
> be caused by the build process doing something like:
> 
>   cd base/test/testTextConsole
>   make BUILD/i386-unknown-coyotos/testTextConsole.merge
> 
> from which I get this back:
> 
>   /home/sam/build/coyotos/coyotos/host/bin/mkimage -t i386 -o BUILD/i386-unknown-coyotos/testTextConsole.img -I. -LBUILD/i386-unknown-coyotos --MD --MF BUILD/i386-unknown-coyotos/.testTextConsole.img.m -f testTextConsole.mki
>   ../../../build/bin/coymerge BUILD/i386-unknown-coyotos/testTextConsole.img BUILD/i386-unknown-coyotos/testTextConsole.merge
>   /coyotos/host/libexec/gcc/i386-unknown-coyotos/4.2.3/ld: section mkimage [0012a000 -> 00191a77] overlaps section .data.cachealign [0012a000 -> 0012a7ff]
>   /coyotos/host/libexec/gcc/i386-unknown-coyotos/4.2.3/ld: section .data [0012a800 -> 0012b9f7] overlaps section mkimage [0012a000 -> 00191a77]
>   collect2: ld returned 1 exit status
>   /coyotos/host/bin/i386-unknown-coyotos-size: 'BUILD/i386-unknown-coyotos/testTextConsole.merge': No such file
> 
> I'm sorry to say that I don't know objcopy well enough to know what it
> should be doing.  While attempting to figure out what was going on I
> noticed that coymerge wasn't removing its temporary files properly.  It
> seems to be caused by the following minor typo:
> 
>   diff -r e1eea879f057 src/build/bin/coymerge
>   --- a/src/build/bin/coymerge    Fri Apr 11 12:28:57 2008 -0400
>   +++ b/src/build/bin/coymerge    Fri Apr 11 23:36:56 2008 +0100
>   @@ -29,7 +29,7 @@ DECOMPRESSED_IMAGE=/tmp/$$.img
>    DECOMPRESSED_IMAGE=/tmp/$$.img
>    
>    function cleanup() {
>   -    rm -f ${TMPMKIMAGE}
>   +    rm -f ${TMPMKIMAGE_OBJ}
>        rm -f ${DECOMPRESSED_IMAGE}
>    }
> 
> Just in case they're helpful I've included the results from running:
> 
>   make -k nodepend clean > ../clean.log 2>&1
>   make -k pristine       > ../pristine.log 2>&1
>   make -k install        > ../install.log 2>&1
> 
> under:
> 
>   http://xen.samason.me.uk/~sam/tmp/
> 
> Hum, I've just realised that I left -x set in the coymerge script for
> the log of the isntall.  That could be useful for you, so I won't run it
> again without.
> 
> 
>   Sam
> _______________________________________________
> coyotos-dev mailing list
> coyotos-dev at smtp.coyotos.org
> http://www.coyotos.org/mailman/listinfo/coyotos-dev