All development tools should work in ELF and just convert to wacky platform formats as the last step of linking.
-
-
Replying to @RichFelker @whitequark
ELF is not capable of accurately representing PE or Mach-O binaries
2 replies 0 retweets 4 likes -
yup. And it's not even that great itself, as the failure of atom linking in lld has shown quite well
1 reply 0 retweets 0 likes -
Replying to @whitequark @RichFelker
It's probably the best of a bad bunch, but that's not saying much. And everything involving the DYNAMIC segment is a disaster
1 reply 0 retweets 1 like -
PT_DYNAMIC is a bit weird but a disaster? I found it rather easy to use while writing my dynamic linker
2 replies 0 retweets 0 likes -
Replying to @whitequark @RichFelker
Everything dynamic linking is asinine. Why are symbols not imported from specific libraries? Why is there one global symbol namespace?
2 replies 0 retweets 0 likes -
Because that's the way C and C++ work.
1 reply 0 retweets 1 like -
Replying to @RichFelker @whitequark
C and C++ do not specify dynamic libraries, so personally IDGAF. The ELF defaults (like "default" visibility) are bad and break things
2 replies 0 retweets 1 like -
Valid reasons for my program exploding do not include that two different libraries link against two different libpng versions
1 reply 0 retweets 3 likes -
"Why is this program crashing in libpng?" "Wait a minute. png_foo from libpng.so.6 is calling png_bar from libpng.so.7"
2 replies 0 retweets 2 likes
Yeah it would be really nice for both ld and ldso to be able to check for that.
-
-
Basically a link option and/or DT_FLAGS flag for "error on any multiple definitions".
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.