On 30/12/2009 11:38, Dave Korn wrote:
Nevermind; I figured it out. I have a local patch in my binutils (which I'm about to send upstream) that accounts for the difference. I'll upload libelf without libgcc1 in the requires: line, since the DLL that I build won't have the import. (DLLs built using unpatched binutils will continue to pull in this redundant dependency, but that's not a problem for me, only for anyone who for whatever reason decides they want to repackage it themselves.)
Why is a dependency on libgcc1 redundant? Yaakov
