On Mon, 2010-07-12 at 14:59 -0400, Pavel Pavlov wrote:
> After checking some files I noticed that VERSIONS file and checked out
> octorer 17 2009 version of binutils. I merged all the changes into
> latest version of binutils. Also, I noticed that versions of binutils
> in cegcc svn has some strange changes, which look to me more likely
> like incorrect merge from previous versions of binutils. Plus, there
> are a bunch of files that simply do not exist in that 0ct17,2009
> version of binutils.
> The reason I wanted to merge binutils is because I have that strange
> problem that dlls produced with cegcc-4.4.0; dlls are almost twice
> bigger compared to builds with cegcc 4.1.0 (because half of the
> produced dll is filled with zeros). I checked object files that go
> into the dll and all of them are normal and have no zeros, but the
> final dll is full of shi...., I mean zeros. So, it looked as if it was
> a linker problem and the linker is part of binutils package. I thought
> that if I take latest binutils I'll probably get it fixed. 
> Still, after I merged changes into latest binutils I got the
> same results and the binaries produced are almost bitexact (at least
> that's a good sign that I didn't screw up with the merge).

The "twice as big" and "zeroes" issue might be a consequence of my
incomplete work on supporting WinCE 6.1+ DLLs. Incomplete because I got
zero support and then when I was loosing courage, I got the Android
device ...

You can take out the WinCE 6.* changes and you'll probably see that that
issue is gone.

        Danny

-- 
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info


------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Cegcc-devel mailing list
Cegcc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cegcc-devel

Reply via email to