>>>>> "Ansgar" == Ansgar <ans...@debian.org> writes:
Ansgar> As far as I understand this approach will break any consumer
Ansgar> on a library whose ABI changes to to the ABI changes
Ansgar> introduced here unless the consumer is built with the flags
Ansgar> from `dpkg-buildflags` (which would now define the ABI).
Ansgar> Do we want this?
I'm fairly sure we do not. Elsewhere in the thread, I saw one of the
toolchain maintainers talking about what is involved in getting gcc to
support the new flags. My suspicion is that handling things with
dpkg-flags is more about moving quickly with the transition than a
desired end state.
Personally I'd consider it a release blocker if we don't get the
compilers updated prior to the release.
I think it would be reasonable to open a bug on the toolchain packages
now talking about this.
I think logistically it would not be desirable for those bugs to be RC
at this time.
Yes, if not fixed they will eventually need to be, but for example I
don't think it would be desirable to block toolchain testing migrations
on this issue at this time. And obviously we're not going to remove the
toolchain from the release.
--Sam
Speaking with my armchair I have no hat in this non-hat on.
