You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
for example libiberty.a
this may cause build error of other gnu sw using libiberty when they expect another version (the one in their source tree, which only gets build when libiberty is not already installed), and wastes space.
some other things like libatomic can possibly be removed as well.
The text was updated successfully, but these errors were encountered:
@rofl0r:
Is building the first & second pass of gcc with --disable-target-libiberty suitable to fix your libiberty.a concern? I notice that the first pass of gcc does install a libiberty.a but then the second pass seems to update that file.
Is also building the second pass of gcc with --disable-libatomic suitable to fix your libatomic concern? Are the atomic operations provided by musl suitable to make libatomic not needed? (I honestly don't know enough to answer this)
It seems that now, master at 09bb1b9 when building with gcc 4.9.2 that libiberty.a does not get created. libatomic is still there.
Did the GCC devs fix this or am I missing something?
for example libiberty.a
this may cause build error of other gnu sw using libiberty when they expect another version (the one in their source tree, which only gets build when libiberty is not already installed), and wastes space.
some other things like libatomic can possibly be removed as well.
The text was updated successfully, but these errors were encountered: