From: BoehmeSilvio <Boehme.Silvio@afb.de>
To: "'gentoo-dev@gentoo.org'" <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] Some Problems
Date: Tue May 8 01:46:01 2001 [thread overview]
Message-ID: <E19CBDD9F21ED111A96A00805F0D6AE0CAF214@AFBWNT01> (raw)
Hi,
after the changes in gnome-1.4 gnome builds successfull on my system !?
I build gnome on a other machine with the same fixes also successfull.
My bigger problem was point 2...
Can some give me some hints on that ?
2.) After a reboot i receive:
(last good boot messages)
devfs...
agpgart...
(now the problem)
/etc/rc.d/init.d/rc: /var/log/boot: Read-only file system
/etc/rc.d/init.d/rc: /var/log/boot: Read-only file system
/etc/rc.d/init.d/rc: /var/log/boot: Read-only file system
(line repeat ~10 times)
rm: cannot unlink 'var/log/.boot': Read-only file system
INIT: Entering runlevel: 3
/etc/rc.d/init.d/rc: /var/log/boot: Read-only file system
/etc/rc.d/init.d/rc: /var/log/boot: Read-only file system
/etc/rc.d/init.d/rc: /var/log/boot: Read-only file system
(line repeat ~10 times, after some time the next message comes up)
INIT: Id "c1" respawning to fast: disabled for 5 minutes
INIT: Id "c2" respawning to fast: disabled for 5 minutes
INIT: Id "c3" respawning to fast: disabled for 5 minutes
INIT: Id "c4" respawning to fast: disabled for 5 minutes
INIT: Id "c5" respawning to fast: disabled for 5 minutes
INIT: Id "c6" respawning to fast: disabled for 5 minutes
> > Well, after making those changes I'm still getting errors
> myself. One was a quick dependancy issue regarding freetype2
> (need freetype-2.0.1-r1.ebuild for one of the packages.. I
> forget which one.)
> >
> > Now I'm getting the following:
> >
> > nautilus-volume-monitor.c:994: (Each undeclared identifier
> is reported only once
> > nautilus-volume-monitor.c:994: for each function it appears in.)
> > nautilus-volume-monitor.c:999: `PROC_MOUNTS_SEPARATOR'
> undeclared (first use in this function)
> > make[2]: *** [nautilus-volume-monitor.lo] Error 1
> > make[2]: Leaving directory
> `/tmp/portage/nautilus-1.0.2/work/nautilus-1.0.2/libnautilus-e
> xtensions'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory
> `/tmp/portage/nautilus-1.0.2/work/nautilus-1.0.2'
> > make: *** [all-recursive-am] Error 2
> >
> > !!! ERROR: the make command did not complete successfully.
> > !!! ("make")
> > !!! Since this is a critical task, ebuild will be stopped.
> >
> > Not sure what this means.
>
> Hrm, sounds like another unresolved dependencie. Can you log the
> compilation to a file and send me the
> configure part.
>
next reply other threads:[~2001-05-08 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 1:46 BoehmeSilvio [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-07 2:17 [gentoo-dev] Some Problems BoehmeSilvio
2001-05-07 18:51 ` JP Sartre
2001-05-07 19:20 ` Achim Gottinger
2001-05-08 2:12 ` Kevin Gordon
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=E19CBDD9F21ED111A96A00805F0D6AE0CAF214@AFBWNT01 \
--to=boehme.silvio@afb.de \
--cc=gentoo-dev@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