1 |
On Sunday 21 December 2008 21:09:33 Jeff Cranmer wrote: |
2 |
> On Sunday 21 December 2008 01:49:41 pm Justin wrote: |
3 |
> > Jeff Cranmer schrieb: |
4 |
> > >> Hmm, if you have a separate machine with the same architecture, you |
5 |
> > >> can build those binary packages yourself, just man emerge and take a |
6 |
> > >> look at the buildpkg section. Alternatively, you can cross compile |
7 |
> > >> binary packages[1]. |
8 |
> > >> |
9 |
> > >> Or, why not just use a stage tarball? |
10 |
> > >> |
11 |
> > >> HTH. |
12 |
> > >> |
13 |
> > >> Joe |
14 |
> > >> |
15 |
> > >> [1] http://www.gentoo.org/proj/en/base/embedded/cross-development.xml |
16 |
> > > |
17 |
> > > I'm not an expert, and I don't have a second amd64 machine. My laptop |
18 |
> > > runs a different PC processor type. How would I go about |
19 |
> > > cross-compiling an amd64 binary on my laptop, and creating the |
20 |
> > > necessary .tbz2 tarball. If I could do that, I would probably be able |
21 |
> > > to test out the theory that this would fix my broken system. |
22 |
> > > |
23 |
> > > Thanks |
24 |
> > > |
25 |
> > > Jeff |
26 |
> > |
27 |
> > Perhaps you should go back to a lower glib version. Latest versions of |
28 |
> > such important packages might always have issues. |
29 |
> |
30 |
> What is the approved way to do this? |
31 |
|
32 |
There is no approved way to downgrade glibc. The output message from the error |
33 |
you posted tells you why the devs will not provide you with a method to do |
34 |
it. If you *really* want to do it, your could comment out the "if" statement |
35 |
between lines 159 and 163 of the latest glibc ebuild. |
36 |
|
37 |
The only correct way I know of is to perform a reinstall. It'll probable be |
38 |
quicker, easier and far less painful than trying to recover from ripping the |
39 |
foundation out from under your OS... |
40 |
|
41 |
|
42 |
However, did you notice that the parent poster mentioned glib and you have |
43 |
attempted to downgrade glibc? |
44 |
|
45 |
|
46 |
-- |
47 |
Alan McKinnon |
48 |
Systems Engineer |
49 |
Infrastructure Services |
50 |
Internet Solutions |
51 |
|
52 |
+27 11 575 7585 |
53 |
|
54 |
|
55 |
> |
56 |
> When I tried to install an old version of glibc from a binary, I got the |
57 |
> error: |
58 |
> |
59 |
> The error was |
60 |
> * Sanity check to keep you from breaking your system: |
61 |
> * Downgrading glibc is not supported and a sure way to destruction |
62 |
> * |
63 |
> * ERROR: sys-libs/glibc-2.6.1 failed. |
64 |
> * Call stack: |
65 |
> * ebuild.sh, line 49: Called pkg_setup |
66 |
> * environment, line 3275: Called die |
67 |
> * The specific snippet of code: |
68 |
> * die "aborting to save your system"; |
69 |
> * The die message: |
70 |
> * aborting to save your system |
71 |
> * |
72 |
> * If you need support, post the topmost build error, and the call stack if |
73 |
> relevant. |
74 |
> * A complete build log is located |
75 |
> at '/var/tmp/portage/sys-libs/glibc-2.6.1/temp/build.log'. |
76 |
> * The ebuild environment file is located |
77 |
> at '/var/tmp/portage/sys-libs/glibc-2.6.1/temp/environment'. |
78 |
> |
79 |
> The error message |
80 |
> "Downgrading glibc is not supported and is a sure way to destruction" |
81 |
> makes me think that going back would not be such a good idea. |
82 |
> |
83 |
> Jeff |
84 |
-- |
85 |
alan dot mckinnon at gmail dot com |