On 20 Dec 2008, at 03:51, Mike Stump wrote:
Yes, libgcc_s is carefully built with carefully controlled exports.
They are controlled by:
gcc/libgcc-std.ver
when someone wants to export one of the symbols, they can just add
it to the list.
OK, my question was phrased poorly;
I understand the mechanism - what I don't understand is the rationale.
What is the benefit of splitting the publicly exported symbols
between libgcc_s.1.dylib and libgcc.a?
This forces us to -lgcc, even in a hypothetical newly-released case,
where the libgcc_s.1.dylib is completely up-to-date.
Iain
