public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kevin Gordon" <kgordon@paradise.net.nz>
To: <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Some Problems
Date: Tue May  8 02:12:01 2001	[thread overview]
Message-ID: <003e01c0d796$90ee0c80$0501010a@kgpro> (raw)
In-Reply-To: 3AF742D9.28784B90@gentoo.org

The order in which I installed packages (amongst 140 of them) was:
librep-0.13.6
rep-gtk-0.15-r1
gnome-core-1.4.0.1
scollkeeper-0.2
sawfish-0.38
libunicode-0.4-r1
gal-0.5
gtkhtml-0.8.3
libgtop-1.0.12
openssl-0.9.6-r1
ammonite-1.0.0
medusa-0.5.0
nautilus-0.8.2
gnome-applets-1.4.0.1
medusa-0.3.2
gnome-1.4

I think scollkeeper-0.2 was an unspecified dependency. Most unlike me not to
have noted it. But from memory I think that is an extra.
Cheers,
Kevin
----- Original Message -----
From: "Achim Gottinger" <AGottinger@t-online.de>
To: <gentoo-dev@gentoo.org>
Sent: Tuesday, May 08, 2001 12:50 PM
Subject: Re: [gentoo-dev] Some Problems


> JP Sartre wrote:
> >
> > * BoehmeSilvio (Boehme.Silvio@afb.de) wrote:
> > > Hi,
> > >
> > > i have 2 problems with gentoo. The first one is easy....
> > >
> > > 1.) i have tried to merge "gnome-1.4.ebuild". There are 2 unresolved
> > > dependencies.
> > >     gnome-1.4.ebuild
> > >       -> medusa-0.3.2         -> fixed to 0.5.0
> > >       -> nautilus-0.8.2               -> fixed to 1.0.2
> > >       -> gnome-core-1.4.0.1   -> fixed to 1.4.0.2
> > >     Now gnome merges successfull.
> > >
> > >
> >
> > 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-extensions'
> > 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.
>
> bye achim~
>
> >
> > JP
> >
> > _______________________________________________
> > gentoo-dev mailing list
> > gentoo-dev@gentoo.org
> > http://www.gentoo.org/mailman/listinfo/gentoo-dev
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev
>
>




  reply	other threads:[~2001-05-08  8:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-08  1:46 BoehmeSilvio

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='003e01c0d796$90ee0c80$0501010a@kgpro' \
    --to=kgordon@paradise.net.nz \
    --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