| 1 |
On ons, 2005-11-23 at 10:54 +0000, Mike Frysinger wrote: |
| 2 |
> On Wed, Nov 23, 2005 at 07:32:18AM -0200, Douglas Campos wrote: |
| 3 |
> > In the old days, we started with a static toolchain to build the uclibc |
| 4 |
> > (a la buildroot), then re-bootstraps everything with the new uclibc as libc |
| 5 |
> > |
| 6 |
> > I ask: in the case of uclibc-0.9.28 (aka 2006.0) what will be done? |
| 7 |
> > google doesn't helped a lot. |
| 8 |
> > I know that uclibc-0.9.28 breaks binary compatibility. |
| 9 |
> > How to do the major update in a gentoo-way? |
| 10 |
> > catalyst breaks, /usr/portage/scripts/bootstrap.sh breaks, emerge -e |
| 11 |
> > system breaks.... |
| 12 |
> |
| 13 |
> emerge 0.9.28 with USE=uclibc-compat and it should be binary compat |
| 14 |
> with 0.9.27 ... then just re-emerge all your packages and you can |
| 15 |
> drop the uclibc-compat from USE and rebuild 0.9.28 |
| 16 |
|
| 17 |
The emerge fails on hardened. |
| 18 |
https://bugs.gentoo.org/show_bug.cgi?id=113343 |
| 19 |
|
| 20 |
-- |
| 21 |
Natanael Copa |
| 22 |
|
| 23 |
-- |
| 24 |
gentoo-embedded@g.o mailing list |
Archives