I'll let others deal with your other questions, because they require
some thought and I am not sure if I remember enough of the re-install
process to deal with it. But, a few comments that I hope may be
helpful:
On Sun, Dec 21, 2008 at 04:41:15PM -0500, Jeff Cranmer wrote:
> (4) After editing the
Jeff Cranmer schrieb:
> On Sunday 21 December 2008 03:44:37 pm Justin wrote:
>
>> Jeff Cranmer schrieb:
>>
>>> On Sunday 21 December 2008 03:28:09 pm Justin wrote:
>>>
Jeff Cranmer schrieb:
> I'm afraid you'll need to be a little more specific on the accept
>>>
On Sunday 21 December 2008 22:42:15 Jeff Cranmer wrote:
> On Sunday 21 December 2008 03:28:09 pm Justin wrote:
> > Jeff Cranmer schrieb:
> > > I'm afraid you'll need to be a little more specific on the accept
> > > keywords
> >
> > reinstall and never change this variable. Stick to the many guides
On Sunday 21 December 2008 03:44:37 pm Justin wrote:
> Jeff Cranmer schrieb:
> > On Sunday 21 December 2008 03:28:09 pm Justin wrote:
> >> Jeff Cranmer schrieb:
> >>> I'm afraid you'll need to be a little more specific on the accept
> >>> keywords
> >>
> >> reinstall and never change this variable.
On Sunday 21 December 2008 03:28:09 pm Justin wrote:
> Jeff Cranmer schrieb:
> > I'm afraid you'll need to be a little more specific on the accept
> > keywords
>
> reinstall and never change this variable. Stick to the many guides out
> there. Your system is broken and fixing takes the same effort
Jeff Cranmer schrieb:
> On Sunday 21 December 2008 03:28:09 pm Justin wrote:
>
>> Jeff Cranmer schrieb:
>>
>>> I'm afraid you'll need to be a little more specific on the accept
>>> keywords
>>>
>> reinstall and never change this variable. Stick to the many guides out
>> there. Your s
Jeff Cranmer schrieb:
> I'm afraid you'll need to be a little more specific on the accept keywords
>
>
reinstall and never change this variable. Stick to the many guides out
there. Your system is broken and fixing takes the same effort than
reinstalling.
signature.asc
Description: OpenPGP
On Sunday 21 December 2008 03:15:41 pm Justin wrote:
> Jeff Cranmer schrieb:
> First avoid top posting
>
> > OK - accepting that my system is broken, I've tried emerge -eav system,
> > and it is failing due to several errors. Other than reformatting the
> > hard drive, how do I reinstall everythin
To clarify, when I try to run emerge -eav system, the first package which
fails is sandbox.
It advises me to try
FEATURES=-sandbox emerge sandbox
in response to the cannot run C compiled programs, but I still get the same
error. My research on the web points me back towards gcc not being compi
Jeff Cranmer schrieb:
First avoid top posting
> OK - accepting that my system is broken, I've tried emerge -eav system, and
> it
> is failing due to several errors. Other than reformatting the hard drive,
> how do I reinstall everything?
>
boot livecd, mount the disc as described in the offi
OK - accepting that my system is broken, I've tried emerge -eav system, and it
is failing due to several errors. Other than reformatting the hard drive,
how do I reinstall everything?
Where do I change the accept keywords variable? It isn't in my make.conf, and
if I put an accept keywords lin
Jeff Cranmer schrieb:
> On Sunday 21 December 2008 02:35:56 pm Justin wrote:
>
>>> However, did you notice that the parent poster mentioned glib and you
>>> have attempted to downgrade glibc?
>>>
>> My fault missed the c.
>> @Jeff
>> Please provide a emerge --info so that we can comment o
On Sunday 21 December 2008 02:35:56 pm Justin wrote:
> > However, did you notice that the parent poster mentioned glib and you
> > have attempted to downgrade glibc?
>
> My fault missed the c.
> @Jeff
> Please provide a emerge --info so that we can comment on it. Perhaps
> this will protect you fro
> > >
> > > Perhaps you should go back to a lower glib version. Latest versions of
> > > such important packages might always have issues.
> >
> > What is the approved way to do this?
>
> There is no approved way to downgrade glibc. The output message from the
> error you posted tells you why the
>
> However, did you notice that the parent poster mentioned glib and you have
> attempted to downgrade glibc?
>
>
>
My fault missed the c.
@Jeff
Please provide a emerge --info so that we can comment on it. Perhaps
this will protect you from some more headache when reinstalling.
signature.
On Sunday 21 December 2008 21:09:33 Jeff Cranmer wrote:
> On Sunday 21 December 2008 01:49:41 pm Justin wrote:
> > Jeff Cranmer schrieb:
> > >> Hmm, if you have a separate machine with the same architecture, you
> > >> can build those binary packages yourself, just man emerge and take a
> > >> look
On Sunday 21 December 2008 01:49:41 pm Justin wrote:
> Jeff Cranmer schrieb:
> >> Hmm, if you have a separate machine with the same architecture, you
> >> can build those binary packages yourself, just man emerge and take a
> >> look at the buildpkg section. Alternatively, you can cross compile
> >
Jeff Cranmer schrieb:
>> Hmm, if you have a separate machine with the same architecture, you
>> can build those binary packages yourself, just man emerge and take a
>> look at the buildpkg section. Alternatively, you can cross compile
>> binary packages[1].
>>
>> Or, why not just use a stage tarbal
On Sunday 21 December 2008 12:43:58 pm Willie Wong wrote:
> On Sun, Dec 21, 2008 at 11:52:11AM -0500, Penguin Lover
> Jeff Cranmer
squawked:
> > checking whether we are using the GNU C compiler... yes
> > checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
> > checking for x86_64-pc-linu
> Hmm, if you have a separate machine with the same architecture, you
> can build those binary packages yourself, just man emerge and take a
> look at the buildpkg section. Alternatively, you can cross compile
> binary packages[1].
>
> Or, why not just use a stage tarball?
>
> HTH.
>
> Joe
>
> [1]
On Sun, Dec 21, 2008 at 11:52:11AM -0500, Penguin Lover Jeff Cranmer squawked:
> checking whether we are using the GNU C compiler... yes
> checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
> checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... unsupported
> checking how to run
On Mon, Dec 22, 2008 at 01:30, Jeff Cranmer wrote:
> On Sunday 21 December 2008 11:52:11 am Jeff Cranmer wrote:
>> On Sunday 21 December 2008 11:11:59 am Justin wrote:
>> > Jeff Cranmer schrieb:
>> > > I have a problem with my gentoo system
>> > >
>> > > I am trying to update, and I get a C prepro
On Sunday 21 December 2008 11:52:11 am Jeff Cranmer wrote:
> On Sunday 21 December 2008 11:11:59 am Justin wrote:
> > Jeff Cranmer schrieb:
> > > I have a problem with my gentoo system
> > >
> > > I am trying to update, and I get a C preprocessor "/lib/cpp" fails
> > > sanity check error on a numbe
On Sunday 21 December 2008 11:11:59 am Justin wrote:
> Jeff Cranmer schrieb:
> > I have a problem with my gentoo system
> >
> > I am trying to update, and I get a C preprocessor "/lib/cpp" fails sanity
> > check error on a number of packages.
> >
> > After a bit of searching, the solution that I co
Jeff Cranmer schrieb:
> I have a problem with my gentoo system
>
> I am trying to update, and I get a C preprocessor "/lib/cpp" fails sanity
> check error on a number of packages.
>
> After a bit of searching, the solution that I come across most often is to
> recompile glibc and gcc. Unfortunat
I have a problem with my gentoo system
I am trying to update, and I get a C preprocessor "/lib/cpp" fails sanity
check error on a number of packages.
After a bit of searching, the solution that I come across most often is to
recompile glibc and gcc. Unfortunately, when I try to compile glibc,
26 matches
Mail list logo
