Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-laptop
Navigation:
Lists: gentoo-laptop: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-laptop@g.o
From: Jürgen Pierau <gentoo-laptop@...>
Subject: Re: emerge broken after update gcc
Date: Thu, 04 Jan 2007 12:32:34 +0100
maillists schrieb:
> Hi,
>
> I just updated gcc and am running 4.1.1. but now my emerge does not work
> at all.
>
> Here is an example of trying to update portage for example:
>
> thor rbragg # emerge -a portage
> emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
> emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
>   
It looks like your filesystem is mounted with the 'ro' option. Seeing 
the output of 'mount' would help.

Bye,
Jürgen
-- 
gentoo-laptop@g.o mailing list


Replies:
Re: emerge broken after update gcc
-- maillists
References:
emerge broken after update gcc
-- maillists
Navigation:
Lists: gentoo-laptop: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
emerge broken after update gcc
Next by thread:
Re: emerge broken after update gcc
Previous by date:
Re: problem with glibc update
Next by date:
Re: emerge broken after update gcc


Updated Jun 17, 2009

Summary: Archive of the gentoo-laptop mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.