| 1 |
On Sat, Feb 18, 2017 at 09:59:56AM -0500, Anthony G. Basile wrote |
| 2 |
|
| 3 |
> You need to be careful because obstack support has been dropped in |
| 4 |
> uclibc-ng-1.0.22. This means that if you directly upgrade to 1.0.22 |
| 5 |
> without first rebuilding your systems (including the toolchain) without |
| 6 |
> obstack support, you will have a severely broken system. The news item |
| 7 |
> specifies the steps by which you can rebuild @world without depending on |
| 8 |
> uclibc-ng to provide obstack, and then upgrading uclibc-ng. |
| 9 |
> |
| 10 |
> I've still got things masked because I'm giving people some time. I'm |
| 11 |
> going to stabilize 1.0.20 today-ish and then 1.0.22 later this month. |
| 12 |
|
| 13 |
OK, I see. You didn't want people on unstable to break their systems. |
| 14 |
Some ideas for sanity checking before you go ahead with 1.0.22. Can an |
| 15 |
ebuild script execute system commands? Possibilities... |
| 16 |
|
| 17 |
* if =sys-libs/uclibc-ng-1.0.20 is not installed and running, have the |
| 18 |
1.0.22 ebuild die, and point to https://www.gentoo.org/support/news-items/2017-02-10-upgrade-to-sys-libs_uclibc-ng-1.0.22.html |
| 19 |
If they tried upgrading this way, they may have missed the news item |
| 20 |
and purged it. |
| 21 |
|
| 22 |
* If "find /usr/include/ -name obstack.h" succeeds, die and point to |
| 23 |
https://www.gentoo.org/support/news-items/2017-02-10-upgrade-to-sys-libs_uclibc-ng-1.0.22.html |
| 24 |
|
| 25 |
* If /usr/include/bits/uClibc_config.h has the wrong value for |
| 26 |
__UCLIBC_HAS_OBSTACK__ die with error and point to |
| 27 |
https://www.gentoo.org/support/news-items/2017-02-10-upgrade-to-sys-libs_uclibc-ng-1.0.22.html |
| 28 |
|
| 29 |
I followed the instructions, finished the basic install, and it boots. |
| 30 |
Now to install X and some apps. |
| 31 |
|
| 32 |
-- |
| 33 |
Walter Dnes <waltdnes@××××××××.org> |
Archives