From: maillists <lists@gmnet.net>
To: gentoo-laptop@lists.gentoo.org
Subject: Re: [gentoo-laptop] problem with glibc update
Date: Wed, 03 Jan 2007 16:47:09 -0500 [thread overview]
Message-ID: <1167860830.16744.68.camel@localhost> (raw)
In-Reply-To: <c52221f0701031108k62c4c19fl2b38eb1930055711@mail.gmail.com>
On Wed, 2007-01-03 at 14:08 -0500, Devon Miller wrote:
> On 1/3/07, maillists <lists@gmnet.net> wrote:
> > On Wed, 2007-01-03 at 08:28 +0100, Praveen C wrote:
> > > I think you first need to update to gcc4.
> > > praveen
> >
> >
> > Hi Thanks, but I do have sys-devel/gcc version 4.1.1-r1.
> >
> > Does anybody know what the problem could be?
>
> Check that you're actually using gcc4:
> gcc-config -c
>
> Next, let's see what USE flags are in play
> emerge -pv sys-devlgcc sys-libs/glibc
>
> dcm
Thanks! I now am really using gcc4! but I am still not out of the hot
water.
Now I get what seems to be a permissions error...
Here is my emerge...
thor rbragg # emerge -auvDN system
emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
These are the packages that would be merged, in order:
Calculating system dependencies... done!
[ebuild U ] sys-libs/glibc-2.4-r4 [2.3.5-r3] USE="nls nptl nptlonly*
-build -glibc-compat20 -glibc-omitfp -hardened (-multilib) -profile
(-selinux) (-erandom%) (-linuxthreads-tls%) (-pic%) (-userlocales%)" 0
kB
[ebuild U ] app-arch/bzip2-1.0.3-r6 [1.0.3-r5] USE="-build -static"
653 kB
[ebuild U ] app-arch/tar-1.16-r2 [1.15.1] USE="nls -static (-build%)
(-bzip2%*)" 1,743 kB
...bla-bla-bla...
Total size of downloads: 18,542 kB
Would you like to merge these packages? [Yes/No] y
Traceback (most recent call last):
File "/usr/bin/emerge", line 4049, in ?
emerge_main()
File "/usr/bin/emerge", line 4044, in emerge_main
myopts, myaction, myfiles, spinner)
File "/usr/bin/emerge", line 3584, in action_build
mergetask.merge(pkglist, favorites, mtimedb)
File "/usr/bin/emerge", line 1854, in merge
"\n".join(myfavdict.values()))
File "/usr/lib/portage/pym/portage_util.py", line 738, in write_atomic
raise ReadOnlyFileSystem(func_call)
portage_exception.ReadOnlyFileSystem:
"write_atomic('/var/lib/portage/world')"
emergelog(): [Errno 30] Read-only file system: '/var/log/emerge.log'
The "/var/log/emerge.log" file is owned by portage.portage, and mode is
ug+rw.
and the "/var/lib/portage/world" file is owned by root.root with u+rw
and go+r
I am running my emerge as root of course...
It seems that I can't even chown the would file.
I tried this:
thor rbragg # chown root.portage /var/lib/portage/world
chown: changing ownership of `/var/lib/portage/world': Read-only file
system
thanks again!
rick
--
gentoo-laptop@gentoo.org mailing list
next prev parent reply other threads:[~2007-01-03 21:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 0:55 [gentoo-laptop] problem with glibc update maillists
2007-01-03 7:28 ` Praveen C
2007-01-03 13:18 ` maillists
2007-01-03 19:08 ` Devon Miller
2007-01-03 21:47 ` maillists [this message]
2007-01-04 0:17 ` Randy Barlow
2007-01-04 0:57 ` maillists
2007-01-04 16:26 ` Devon Miller
-- strict thread matches above, loose matches on Subject: below --
2007-01-03 16:42 Longman, Bill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1167860830.16744.68.camel@localhost \
--to=lists@gmnet.net \
--cc=gentoo-laptop@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox