oi-userland
oi-userland copied to clipboard
OpenIndiana
GCC 10 fixes
@AndWac @Toasterson @pyhalov Work in progress, I'll bump the component revisions when I open pull requests to merge these fixes by batch.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
@alarcher Are there any chances to migrate to 64-bit-by-default gcc till October?
@pyhalov There is not much left, 64-bit-by-default issue were only a small minority. Most leftover work is failure to build for other reasons. https://www.illumos.org/issues/12722
@AndWac From the commit with ConsoleKit onwards I am now pushing fixes to components in library/ if you have time to cherry-pick them, say 10 at a time and merge them. Then I can continue fixing them one by one.
@AndWac Sometimes I have removed the documentation generated by doxygen because the filenames change and it is a pain...
@Toasterson @mtelka @jgmills @balrog-nona I have queued fixes to broken components in this branch... if you feel like you have time to help @AndWac and me to review and integrate them...
@alarcher, what kind of brokenness you fixed here? I looked at few changesets and everything looks related to gcc-10 only (while we do not have gcc-10 set as default yet). Or do I miss something?
@alarcher, what kind of brokenness you fixed here? I looked at few changesets and everything looks related to gcc-10 only (while we do not have gcc-10 set as default yet). Or do I miss something?
A few of them are broken due to gcc-10 but a lot of them needed conversion to the new style of Makefile using common.mk to overcome the issues we discussed in the other PR. I thought I would put the effort to sanitize them since your changeset revealed that a lot of them needed an update.
