[EMAIL PROTECTED] wrote:

  Hi,

  I just installed FreeBSD6.2 onto my home computer.  I chose the
  'minimum installation' option.  I then installed the ports tree by
  'portsnap fetch', followed by 'portsnap extract', and then 'portsnap
  fetch upgrade'.  Then I successfully installed Xorg via the ports
  tree.  I then configured and tested X11.  So far, all went very well.

  Next, I wanted to install the Gnome Desktop Environment, so 'cd
  /usr/ports/x11/gnome2' followed by 'make install clean'.  The
  installation went well for over two hours, and then it stopped with
  the message that I have included from the script file below.

  I have a few questions:
  1.  How can I continue, and complete, the installation of Gnome?
  2.  What, besides general Googling and checking the FreeBSD archives,
  can I do when the installation generates an error message like the one
  below that is merely descriptive and not prescriptive?  (I'd like to
  not have to come running to this forum every time an installation
  doesn't succeed.  I realize that a learning curve is involved, but I'm
  willing to do a bit of research if I can find the right resources.  I
  did look at /usr/ports/UPDATING but didn't find anything that looked
  relevant.)
  3.  In the past (5.4), I have used 'portupgrade' to maintain my ports
  tree.  I understand that 'portsnap' is a new utility that is supposed
  to be easier to use and more reliable.  So does this mean that I can
  do all of my ports tree maintenance with 'portsnap' and never use
  'portupgrade' again?

  Any advice, suggestions, or comments would be appreciated!

  Thank you,
  Larry

  Error Message **********
                                         (Excerpt)
  *
  *
  *
  ===>   gnome-control-center-2.18.1_1 depends on shared library: xml2.5
  - found
  ===>   gnome-control-center-2.18.1_1 depends on shared library: xslt.2
  - found
  ===>   gnome-control-center-2.18.1_1 depends on shared library: linc.1
  - found
  ===>   gnome-control-center-2.18.1_1 depends on shared library:
  metacity-private.0 - not found
  ===>    Verifying install for metacity-private.0 in
  /usr/ports/x11-wm/metacity
  ===>  Building for metacity-2.18.5
  gmake  all-recursive
  gmake[1]: Entering directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5'
  Making all in src
  gmake[2]: Entering directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src'
  gmake  all-recursive
  gmake[3]: Entering directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src'
  Making all in wm-tester
  gmake[4]: Entering directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src/wm-tester'
  gmake[4]: Nothing to be done for `all'.
  gmake[4]: Leaving directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src/wm-tester'
  Making all in tools
  gmake[4]: Entering directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src/tools'
  gmake[4]: Nothing to be done for `all'.
  gmake[4]: Leaving directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src/tools'
  Making all in themes
  gmake[4]: Entering directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src/themes'
  gmake[4]: Nothing to be done for `all'.
  gmake[4]: Leaving directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src/themes'
  gmake[4]: Entering directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src'
  gmake[4]: Nothing to be done for `all-am'.
  gmake[4]: Leaving directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src'
  gmake[3]: Leaving directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src'
  gmake[2]: Leaving directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/src'
  Making all in po
  gmake[2]: Entering directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/po'
  file=`echo cs | sed 's,.*/,,'`.gmo \
     && rm -f $file && /usr/local/bin/msgfmt -o $file cs.po
  cs.po:1160:72: invalid multibyte sequence
  cs.po:1160: keyword "a" unknown
  cs.po:1160:76: parse error
  cs.po:1161: end-of-line within string
  /usr/local/bin/msgfmt: found 4 fatal errors
  gmake[2]: *** [cs.gmo] Error 1
  gmake[2]: Leaving directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5/po'
  gmake[1]: *** [all-recursive] Error 1
  gmake[1]: Leaving directory
  `/usr/ports/x11-wm/metacity/work/metacity-2.18.5'
  gmake: *** [all] Error 2
  *** Error code 2
  Stop in /usr/ports/x11-wm/metacity.
  *** Error code 1
  Stop in /usr/ports/sysutils/gnome-control-center.
  *** Error code 1
  Stop in /usr/ports/x11/gnome-applets.
  *** Error code 1
  Stop in /usr/ports/x11/gnome2.
  *** Error code 1
  Stop in /usr/ports/x11/gnome2.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Ok. Could you tell me if you installed 6.2 release (this is the official one ) or 6.2 stable(you have to get this as a snap shot or rebuild the world)? Second question is if you installed 6.2 release then you probably have
XOrg 6.9 not XOrg 7.2. Just to be on the safe side check /var/db/pkg ?
I would guess that the failure has to do with the dependency issues related to XOrg 7.2. Gnome 2.18 was not part of official 6.2 release and probably depends on XOrg 7.2. I build 2.18 successfully from ports but I am running 6.2 stable and XOrg 7.2. I also used make BATCH=yes install clean (I used batch mode to avoid answering questions about the packages
and creating dependency issues)
It took over 12 hours on Instel Core 2 Duo to compile whole meta port and another 5 hours for fifth-toe and gnome-office. My knowledge is very limited so I could not tell you anything more about failure of your compiler or answer the rest of your questionts.

According to FreeBSD Gnome http://www.freebsd.org/gnome/ the failure of compiler is not uncommon. Maybe you should post
your question on there mailing list.

All the best
Predrag

_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to