| 1 |
I don't have access to my archive right now, but I remember that Achim said |
| 2 |
you need to update the compiler before trying to update glibc. |
| 3 |
|
| 4 |
-- |
| 5 |
Collins Richey |
| 6 |
Denver area |
| 7 |
|
| 8 |
----- Original Message ----- |
| 9 |
From: "Mathijs Kwik (-=TRoXX=-)" <troxx@××××××××.nl> |
| 10 |
To: <gentoo-dev@××××××××××.org> |
| 11 |
Sent: Tuesday, June 05, 2001 7:20 AM |
| 12 |
Subject: [gentoo-dev] GlibC |
| 13 |
|
| 14 |
|
| 15 |
> Safe upgrading? :) |
| 16 |
> |
| 17 |
> I tried 2 things which both fail... |
| 18 |
> using build-tarball: |
| 19 |
> changing the bootstrap-file to use glibc-2.2.3-r1 instead of 2.2.3 |
| 20 |
> the build-tarball has 2.2.3-r1 allready installed so installing 2.2.3 |
| 21 |
would |
| 22 |
> be stupid(but it's still in the bootstrap-file). |
| 23 |
> |
| 24 |
> and i also tried installing 2.2.3-r1 on a system with system=tarball |
| 25 |
> extracted... which also has 2.2.3-r1 in it. |
| 26 |
> |
| 27 |
> |
| 28 |
> so in both those cases I 'upgrade' a package to itself. |
| 29 |
> and in both cases it breaks everything on the system... |
| 30 |
> I don't know what exactly happens on the build-system. |
| 31 |
> but on the system-system(wow:) I end up having a 0-byte libc-2.2.3.so |
| 32 |
> |
| 33 |
> so I don't know why this is... it's very easy to regenerate te error (did |
| 34 |
it |
| 35 |
> a few times, I thought it was just me:) |
| 36 |
> |
| 37 |
> so either portage has a buggy, or glibc 2.2.3-r1.ebuild is buggy (because |
| 38 |
I |
| 39 |
> never got it to build+installed using portage). |
| 40 |
> |
| 41 |
> please fix this or help me :) |
| 42 |
> |
| 43 |
> |
| 44 |
> --- |
| 45 |
> |
| 46 |
> |
| 47 |
> another small thing I don't like (and I'm not the only one, I spoke some |
| 48 |
> guys on #gentoo who think the same) |
| 49 |
> the portage-tree is TOOOO big :) |
| 50 |
> there are things in it like diffs(some quite big) and even the |
| 51 |
> logo-header-file(almost 2M). |
| 52 |
> can't we just put all files/* stuff in a separate place on ibiblio/cvs and |
| 53 |
> put them in ebuild-files? (or let portage check if there are any |
| 54 |
> diffs/patches/additions) |
| 55 |
> I mean the portage-tree should just contain enough info to download+build |
| 56 |
> everything... |
| 57 |
> having diff's in there for packages that I'm not gonna install anyway |
| 58 |
seems |
| 59 |
> useless to me. |
| 60 |
> |
| 61 |
> It's about 20M now... should be possible to reduce it to 2Mb :) |
| 62 |
> not because of bandwith, just for clean design. |
| 63 |
> Some others DO care about bandwith, which I can understand also. |
| 64 |
> |
| 65 |
> |
| 66 |
> Greetings |
| 67 |
> /Mathijs |
| 68 |
> |
| 69 |
> |
| 70 |
> |
| 71 |
> _______________________________________________ |
| 72 |
> gentoo-dev mailing list |
| 73 |
> gentoo-dev@××××××××××.org |
| 74 |
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev |
Archives