@jpabartholomew @won3d @w23ru ... but in Windows, it is trivial to compile against kernel32.lib and have GetProcAddress everywhere.
-
-
Replying to @cmuratori
@jpabartholomew@won3d@w23ru Like, all the way back to Windows95.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@jpabartholomew@won3d@w23ru In Linux, this is _much more complicated_. The same procedure doesn't work, because dlsym is in glibc.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@jpabartholomew@won3d@w23ru You must then install multiple versions of GLibC just to link against dlsym that will work on older systems.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@jpabartholomew@won3d@w23ru Because if you use the dlsym that comes with _your_ GLibC, your exe fails to load on _older_ GlibCs...1 reply 0 retweets 0 likes -
Replying to @cmuratori
@jpabartholomew@won3d@w23ru ...before you even get dlsym to load the newer symbols you were trying to load to avoid requiring a new GLibC!1 reply 0 retweets 0 likes -
This Tweet is unavailable.
-
Replying to @jtwxtr
@jpabartholomew@won3d@w23ru Nobody on Linux thinks about these things because they generally don't ship to consumers.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@jpabartholomew@won3d@w23ru So "oh just sync to all the latest packages from everyone and then rebuild from source" is an OK distrib.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@jpabartholomew@won3d@w23ru But once you're in consumerland, you really need to be able to ship a binary that "just runs".3 replies 0 retweets 0 likes
@jpabartholomew @won3d @w23ru And Linux seems to be very bad at that, even at the architecture level :(
-
-
This Tweet is unavailable.
-
This Tweet is unavailable.
- Show replies
-
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.