Follow-up Comment #5, bug #33392 (project gnustep): What Nicola is saying is perfectly accurate, but I think binary compatibility is only an issue for packagers who want their package to work, e.g., on all i[3-7]86 machines. People who build gnustep from source for their personal machine probably want to utilize the complete feature-set their processor provides.
I don't think it's a big portability issue, though: On most platforms, GCC has code emulating atomic operations in libgcc.a, which will be used when it cannot (or refuses to) emit target specific assembly for that purpose. The trick is to get it to link the static library if required. I have an autoconf thingy in DBusKit that checks whether the atomic ops are provided as builtins or library functions and adjusts the LDFLAGS accordingly. Should I try adding it to -base as well? _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?33392> _______________________________________________ Nachricht geschickt von/durch Savannah http://savannah.gnu.org/ _______________________________________________ Bug-gnustep mailing list Bug-gnustep@gnu.org https://lists.gnu.org/mailman/listinfo/bug-gnustep