eclipse fails to launch svn'ed project FreeBSD

Is there any output on the first console?

Press CTRL + ALT + F1 to see.

Also try dmesg to see if there is any messages that tell you more about the error...

I don't have a control key

What kind of keyboard are you using then?

The one with the broken control key.. I'm looking for the thing you told me thru menus now.

Did you try

dmesg

already?

Okay this "console" doesn't have the shortcut you asked for
eclipse-console.png

We're supposed to be using Java 1.5 not java 1.6  was portupgrade -a a bad idea?

ke[2]: Entering directory `/usr/ports/x11/zenity/work/zenity-2.22.1'
gmake[2]: Nothing to be done for `all-am'.
gmake[2]: Leaving directory `/usr/ports/x11/zenity/work/zenity-2.22.1'
gmake[1]: Leaving directory `/usr/ports/x11/zenity/work/zenity-2.22.1'
--->  Backing up the old version
--->  Uninstalling the old version
--->  Deinstalling 'zenity-2.20.0'
pkg_delete: package 'zenity-2.20.0' is required by these other packages
and may not be deinstalled (but I'll delete it anyway):
gdm-2.20.1_1
gnome2-2.20.1
[Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 618 packages found (-1 +0) (...)

It's literally been running for days now.

644 /usr/local/lib/gstreamer-0.10/libgstpng.a
ranlib /usr/local/lib/gstreamer-0.10/libgstpng.a
----------------------------------------------------------------------
Libraries have been installed in:
   /usr/local/lib/gstreamer-0.10

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `LD_LIBRARY_PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,--rpath -Wl,LIBDIR' linker flag

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
gmake[1]: Leaving directory `/usr/ports/graphics/gstreamer-plugins-libpng/work/gst-plugins-good-0.10.10/ext/libpng'
===>   Registering installation for gstreamer-plugins-libpng-0.10.10_3,3
===>  Cleaning for gstreamer-plugins-libpng-0.10.10_3,3
--->  Cleaning out obsolete shared libraries
[Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 619 packages found (-0 +1) . done]

dmesg?  I suspect I mucked up the subversion check out or the creation of the project.  Why would we need dmesg?

Is it possible for me to debug a java project with jdb instead of eclipse?

I created some  different "date directories" so I can have multiple copies of the nachos directory. In
the nachos directory, all the directories for existing nachos code and code we add to the project
are there.. e.g.

KV_BSD% cd cs162
KV_BSD% ls
eclipse.png             look_right.png          oct24_08
eclipse_console.png     nachos                  oct24_08b
eclipse_launch.png      no_sound.png            oct27_08
java_project.png        nov06_08                svn.png
jp_dialog.png           oct23_08
KV_BSD% cd nachos
KV_BSD% pwd
/home/kayve/cs162/nachos
KV_BSD% ls
Makefile        bin             proj1           proj4           threads
README          machine         proj2           security        userprog
ag              network         proj3           test            vm
KV_BSD%


the current project (proj3) we edit files in the vm directory.  I don't really care about using eclipse but
I guess I have to be able to debug better than using system.outs.  I have been able to check out and check
in just fine from my command line.. the directories you see above called "proj1 etc" just have a
config file and a makefile or something.. to run the program after editing files in userprog or threads or
vm direcotries, you must be cd'ed to the correct proj directory (proj3 now) and type "gmake" then
i type "../bin/nachos" (instead of messing with my $PATH) to run it.

dmesg | grep (what?)

dmesg has the usual ACPI errors nothing else.  FreeBSD gurus (from freebsd-acpi mailing list) told me not to worry about ACPI errors because it is just a mistimed binding that works itself out before boot up.

The ACPI errors are nothing to worry about, but dmesg could give some clue about what goes wrong in eclipse. THere is another way to see if you can get more info on the error. try this:

Open a console in X
Type
eclipse

And try to open the project. Are there any errors appearing in the console window?

I don't know if I have a project correctly.  The correct thing to do is import project from the subversion.  THat is what this question is about.  I sent you screenshots of eclipse I opened using the method you are talking about. The guy in my group showed me about import
import.png

shoot.  Did I include the subversion area in this question?  How do I tell how I have associated this questions. Are you a subversion expert as well as FreeBSD

Yes. I use subversion myself. Subversion doesn't have much to do with this. I you checked out the project correctly than that's it. So you said that there is a makefile somewhere. Do you have to run that after you edit the source or before to make it compatible with your system?

I see in your first screenshot that there is a README file. Doesn't that give you any clues?

Subversion is everything about this question.  I really don't know if I checked out a "project" correctly.  I managed to get a file hierarchy, but that in no way implies I did the correct thing with respect to checking out a "project."

There are 4 different makefiles for the four different phases of the project.  they are in the directories proj1.
etc.  

I know how to do the makefiles on the command line, but that apparently isn't going to cut it unless you know jdb real well.  I haven't used any makefiles with eclipse, I have no idea how to do that.

Better than README is the URL I gave.  I'm getting a stomach ache

   Nachos for Java README

Welcome to Nachos for Java. We believe that working in Java rather than
C++ will greatly simplify the development process by preventing bugs
arising from memory management errors, and improving debugging support.

Getting Nachos:

Download nachos-java.tar.gz from the Projects section of the class
homepage at:

        http://www-inst.EECS.Berkeley.EDU/~cs162/

Unpack it with these commands:

        gunzip -c nachos-java.tar.gz | tar xf -

Additional software:

Nachos requires the Java Devlopment Kit, version 1.5 or later. This is
installed on all instructional machines in:
        /usr/sww/lang/jdk-1.5.0_05
To use this version of the JDK, be sure that
is on your PATH. (This should be the case for all class accounts
already.)

If you are working at home, you will need to download the JDK.
It is available from:
        http://java.sun.com/j2se/1.5/
Please DO NOT DOWNLOAD the JDK into your class account! Use the
preinstalled version instead.

The build process for Nachos relies on GNU make. If you are running on
one of the instructional machines, be sure you run 'gmake', as 'make'
does not support all the features used. If you are running Linux, the
two are equivalent. If you are running Windows, you will need to
download and install a port. The most popular is the Cygnus toolkit,
available at:

        http://sources.redhat.com/cygwin/mirrors.html

The Cygnus package includes ports of most common GNU utilities to
Windows.

For project 2, you will need a MIPS cross compiler, which is a
--More--(17%)
specially compiled GCC which will run on one architecture (e.g.
Sparc) and produce files for the MIPS processor. These compilers
are already installed on the instructional machines, and are
available in the directory specified by the $ARCHDIR environment
variable.

If you are working at home, you will need to get a cross-compiler
for yourself. Cross-compilers for Linux and Win32 will be available
from the CS162 Projects web page. Download the cross compiler
distribution and unpack it with the following command:

        gunzip -c mips-x86-linux-xgcc.tar.gz | tar xf -

(Substitute the appropriate file name for mips-x86.linux-xgcc in the
above command.) You need to add the mips-x86.linux-xgcc directory to
your PATH, and set an environment variable ARCHDIR to point to this
directory. (Again, this has already been done for you on the
instructional machines.)

Compiling Nachos:

You should now have a directory called nachos, containing a Makefile,
this README, and a number of subdirectories.
First, put the 'nachos/bin' directory on your PATH. This directory
contains the script 'nachos', which simply runs the Nachos code.

To compile Nachos, go to the subdirectory for the project you wish
to compile (I will assume 'proj1/' for Project 1 in my examples),
and run:

        gmake

This will compile those portions of Nachos which are relevant to the
project, and place the compiled .class files in the proj1/nachos
directory.

You can now test Nachos from the proj1/ directory with:

        nachos

You should see output resembling the following:

  nachos 5.0j initializing... config interrupt timer elevators user-check grader
  *** thread 0 looped 0 times
  *** thread 1 looped 0 times

--More--(35%)
  *** thread 0 looped 1 times
  *** thread 1 looped 1 times
  *** thread 0 looped 2 times
  *** thread 1 looped 2 times
  *** thread 0 looped 3 times
  *** thread 1 looped 3 times
  *** thread 0 looped 4 times
  *** thread 1 looped 4 times
  Machine halting!

  Ticks: total 24750, kernel 24750, user 0
  Disk I/O: reads 0, writes 0
  Console I/O: reads 0, writes 0
  Paging: page faults 0, TLB misses 0
  Network I/O: received 0, sent 0

This is the correct output for the "bare bones" Nachos, without any of
the features you will add during the projects.

If you are working on a project which runs user programs (projects 2-4),
you will also need to compile the MIPS test programs with:

        gmake test
Command Line Arguments:

For a summary of the command line arguments, run:

        nachos -h

The commands are:

        -d <debug flags>
                Enable some debug flags, e.g. -d ti

        -h
                Print this help message.

        -s <seed>
                Specify the seed for the random number generator

        -x <program>
                Specify a program that UserKernel.run() should execute,
                instead of the value of the configuration variable
                Kernel.shellProgram

     -z
                print the copyright message

        -- <grader class>
                Specify an autograder class to use, instead of
                nachos.ag.AutoGrader

        -# <grader arguments>
                Specify the argument string to pass to the autograder.

        -[] <config file>
                Specifiy a config file to use, instead of nachos.conf


Nachos offers the following debug flags:

    c: COFF loader info
    i: HW interrupt controller info
    p: processor info
    m: disassembly
    M: more disassembly
To use multiple debug flags, clump them all together. For example, to
monitor coff info and process info, run:

        nachos -d ac

nachos.conf:

When Nachos starts, it reads in nachos.conf from the current
directory.  It contains a bunch of keys and values, in the simple
format "key = value" with one key/value pair per line. To change the
default scheduler, default shell program, to change the amount of
memory the simulator provides, or to reduce network reliability, modify
this file.

Machine.stubFileSystem:
    Specifies whether the machine should provide a stub file system. A
    stub file system just provides direct access to the test directory.
    Since we're not doing the file system project, this should always
    be true.

Machine.processor:
    Specifies whether the machine should provide a MIPS processor. In
 the first project, we only run kernel code, so this is false. In
    the other projects it should be true.

Machine.console:
    Specifies whether the machine should provide a console. Again, the
    first project doesn't need it, but the rest of them do.

Machine.disk:
    Specifies whether the machine should provide a simulated disk. No
    file system project, so this should always be false.

ElevatorBank.allowElevatorGUI:
    Normally true. When we grade, this will be false, to prevent
    malicious students from running a GUI during grading.

NachosSecurityManager.fullySecure:
    Normally false. When we grade, this will be true, to enable
    additional security checks.

Kernel.kernel:
    Specifies what kernel class to dynmically load.  For proj1, this is
    nachos.threads.ThreadedKernel. For proj2, this should be
    nachos.userprog.UserKernel. For proj3, nachos.vm.VMKernel. For
  proj4, nachos.network.NetKernel.

Processor.usingTLB:
    Specifies whether the MIPS processor provides a page table
    interface or a TLB interface. In page table mode (proj2), the
    processor accesses an arbitrarily large kernel data structure to do
    address translation. In TLB mode (proj3 and proj4), the processor
    maintains a small TLB (4 entries).

Processor.numPhysPages:
    The number of pages of physical memory.  Each page is 1K. This is
    normally 64, but we can lower it in proj3 to see whether projects
    thrash or crash.

Documentation:

The JDK provides a command to create a set of HTML pages showing all
classes and methods in program. We will make these pages available on
the webpage, but you can create your own for your home machine by doing
the following (from the nachos/ directory):

        mkdir ../doc
        gmake doc
Troubleshooting:

If you receive an error about "class not found exception", it may be
because you have not set the CLASSPATH environment variable. Add the
following to your .cshrc:

        setenv CLASSPATH .

Credits:

Nachos was originally written by Wayne A. Christopher, Steven J.
Procter, and Thomas E. Anderson. It incorporates the SPIM simulator
written by John Ousterhout. Nachos was rewritten in Java by Daniel
Hettena.

Copyright:

Copyright (c) 1992-2001 The Regents of the University of California.
All rights reserved.

Permission to use, copy, modify, and distribute this software and its
documentation for any purpose, without fee, and without written

Permission to use, copy, modify, and distribute this software and its
documentation for any purpose, without fee, and without written
agreement is hereby granted, provided that the above copyright notice
and the following two paragraphs appear in all copies of this
software.

IN NO EVENT SHALL THE UNIVERSITY OF CALIFORNIA BE LIABLE TO ANY PARTY
FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF
THE UNIVERSITY OF CALIFORNIA HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.

THE UNIVERSITY OF CALIFORNIA SPECIFICALLY DISCLAIMS ANY WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE SOFTWARE
PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND THE UNIVERSITY OF
CALIFORNIA HAS NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES,
ENHANCEMENTS, OR MODIFICATIONS.

KV_BSD%

    t: thread info
    a: process info (formerly "address space", hence a)

I'm sorry this is a better link

http://inst.eecs.berkeley.edu/~cs162/fa08/Nachos/subversion.html

It looks like they are using a MacIntosh and I may have Europa and not Ganymede like
they are using.  That's why I decided to do a portupgrade -a the other day.

Oh jeez.  This looks new.  Maybe I am supposed to use subclipse

http://subclipse.tigris.org/

oh wait.. I gave you the wrong link

http://inst.eecs.berkeley.edu/~cs162/fa08/Nachos/eclipse/
eclipse-page.png

for pkg-config... /usr/local/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for GTKHTML2... yes
checking for GAILUTIL... yes
checking for GNOME_VFS... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating docs/Makefile
config.status: creating libgtkhtml/Makefile
config.status: creating libgtkhtml/css/Makefile
config.status: creating libgtkhtml/document/Makefile
config.status: creating libgtkhtml/dom/Makefile
config.status: creating libgtkhtml/dom/core/Makefile
config.status: creating libgtkhtml/dom/html/Makefile
config.status: creating libgtkhtml/dom/events/Makefile
config.status: creating libgtkhtml/dom/views/Makefile
config.status: creating libgtkhtml/dom/traversal/Makefile
config.status: creating libgtkhtml/graphics/Makefile
config.status: creating libgtkhtml/layout/Makefile
config.status: creating libgtkhtml/layout/html/Makefile
config.status: creating libgtkhtml/util/Makefile
config.status: creating libgtkhtml/view/Makefile
config.status: creating libgtkhtml/a11y/Makefile
config.status: creating tests/Makefile
config.status: creating tests/samples/Makefile
config.status: creating libgtkhtml-2.0.pc
config.status: creating config.h
config.status: executing depfiles commands
===>  Building for libgtkhtml-2.11.1_2
gmake  all-recursive
gmake[1]: Entering directory `/usr/ports/www/libgtkhtml/work/libgtkhtml-2.11.1'
Making all in libgtkhtml
gmake[2]: Entering directo

that was purdy {:)

This link:
http://inst.eecs.berkeley.edu/~cs162/fa08/Nachos/eclipse/

Explains it all very well in step by step instructions (man, I wish I had clear instructions like this when I was still in university). DId you follow these? For instance, to get to the window in the above screenshot do this:

First you need to set up Eclipse to connect with your CVS repository. Start by switching to the CVS Repository Exploring perspective. Do this by going to Window > Open Perspective. Then right click in the CVS Repositories view (on the left) and select New > Repository Location. You will get this window:

I don't have time to read all the documentation for you, why don't you ask the members of your project for help?

creating libgstgnomevfs.la
(cd .libs && rm -f libgstgnomevfs.la && ln -s ../libgstgnomevfs.la libgstgnomevfs.la)
--->  Backing up the old version
--->  Uninstalling the old version
--->  Deinstalling 'gstreamer-plugins-gnomevfs-0.10.14_2,3'
pkg_delete: package 'gstreamer-plugins-gnomevfs-0.10.14_2,3' is required by these other packages
and may not be deinstalled (but I'll delete it anyway):
alacarte-0.11.3_2
deskbar-applet-2.20.1
gnome-applets-2.20.0
gnome-games-2.20.1
gnome2-2.20.1
py25-gnome-desktop-2.20.0
totem-2.20.1
[Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 619 packages found (-1 +0) (...) done]
--->  Installing the new version via the port

nd
===>   libsexy-0.1.11_1 depends on file: /usr/local/bin/libtool - found
===>   libsexy-0.1.11_1 depends on file: /usr/local/bin/intltool-extract - found
===>   libsexy-0.1.11_1 depends on executable: pkg-config - found
===>   libsexy-0.1.11_1 depends on shared library: enchant - found
===>   libsexy-0.1.11_1 depends on shared library: atk-1.0.0 - found
===>   libsexy-0.1.11_1 depends on shared library: glib-2.0.0 - found
===>   libsexy-0.1.11_1 depends on shared library: gtk-x11-2.0.0 - found
===>   libsexy-0.1.11_1 depends on shared library: xml2.5 - found
===>   libsexy-0.1.11_1 depends on shared library: pango-1.0.0 - found
===>  Configuring for libsexy-0.1.11_1
checking for a BSD-compatible install... /usr/bin/install -c

sexy libs!  {:D

I told you! no such windows exist!  I think I have Europa!

oh wait.  where on the page was that?  

Don't I want SVN not CVS?  That might be a typo on the page

I've done this part before, you know and it didn't werk right I don't think

c p
svn-repos.png

I have the repository already, that's not the problem
svn-properties.png

okay maybe there is a window
co-svn.png

around in circles
new-project.png

I'm going in circles {:(  I don't understsand
co-again.png

You have been assuming I did nothing before asking the question.  I did things.  I asked my partners.  The drawback is that I can't get internet in Berkeley, and they don't come to San Francisco to see my desktop.
They got tired of screenshots but now I see the major flaw.
project-made.png
not-fished.png

icesconfig.o iface-state-monitor-dummy.o
ranlib .libs/liboobs-1.a
creating liboobs-1.la
(cd .libs && rm -f liboobs-1.la && ln -s ../liboobs-1.la liboobs-1.la)
Making all in doc
Making all in reference
--->  Backing up the old version
--->  Uninstalling the old version
--->  Deinstalling 'liboobs-2.20.0'
--->  Preserving /usr/local/lib/liboobs-1.so.3 as /usr/local/lib/compat/pkg/liboobs-1.so.3
pkg_delete: package 'liboobs-2.20.0' is required by these other packages
and may not be deinstalled (but I'll delete it anyway):
gnome-system-tools-2.20.0
gnome2-2.20.1
[Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 619 packages found (-1 +0) (...) done]
--->  Installing the

The problem might be that I dont' have Ganymede.. just Europa.  Can you answer my question, i.e. "should
I be trying a `portupgrade -a` and will this mean I upgrade to Ganymede without upgrading to java 6?"  If
I end up adding java 6 can I set eclipse to use java 5?

doing portupgrade as we speek.. days in days.. still compiling.
portupgrade.png

Yay for Obama!
gobama.png

I can run it fine from my command line. it is all badness with eclipse.. now I realize I don't care about
using eclipse subversion.  I can't make eclipse compile and run the project right.

How do I run eclipse-devl ? "eclipse-devel" from command line?  I guess that I can figure out easily enough.

How long is this portupgrade -a going to compile? My puter better be really kewl when it's done.. I think
we are going on 100 hours of compilation at least now.

There is still the central problem of eclipse not acting the way the instructions say it would.  I'm sorry,
I guess I could have written a better question to begin with.  I didn't post the question because I was
too lazy to read the instructions, and I didn't provide the instructions ...

arg.

I really didn't think this was going to be that difficult.  Should I kill the portupgrade -a make and
run the eclipse-devel make?

Killing a portupgrade is dangerous to say the least... It might leave you with an instable OS. Be patient and once it's done try the eclipse-devel port to see if it helps your situation...

Hmm.. I guess I have been lucky. I have killed portupgrade twice so far (in order to bring my puter to skewl
and back!) but I restarted it when I rebooted.

Well, it might brake for instance your X environment. It does take a long time though, you must have installed a sh*tload of stuff...

When I am done with portupgrade -a and cd /usr/ports/java/eclipse-devel; make install clean
when I run eclipse it will be Ganymede?

Yes, but make sure you uninstall Europa first...

cd /usr/ports/java/eclipse; make deinstall; cd /usr/ports/java/eclipse-devel; make install clean,
right?

Yep, right.

I feel like portupgrade -a might be repeating itself. Is this because I messed up when I killed it twice? Could it be in an infinite loop?

It can't loop and if it was messed up it would give a lot of errors. You've installed a lot of programs and everything is compiled from scratch, that takes a while.

You could kill it and see if you can build eclipse-devel if you're in a hurry, but make sure you do finish the portupgrade or you'll end up with an (potential) unstable system...

portupgrade -a asked me about gnome screensavers again.  I think it's in an infinite loop!  {:(

I started the eclipse-devel in a different window

Oops.  Now I started the deinstall.  You know about subclipse?

it's only this far

eclipse-devel
You have new mail.                                                              
KV_BSD# make install clean

 eclipse-devel is using firefox for gecko support, but you can
 change that by defining WITH_GECKO to the following values:

   firefox
   xulrunner
   seamonkey

=> eclipse-sourceBuild-srcIncluded-3.4.1.zip doesn't seem to exist in /usr/ports/distfiles/eclipse.
=> Attempting to fetch from http://download.eclipse.org/eclipse/downloads/drops/R-3.4.1-200809111700/.
eclipse-sourceBuild-srcIncluded-3.4.1.zip      73% of  101 MB  293 kBps 01m32s

KV_BSD# cd /usr/ports/java/eclipse
KV_BSD# make deinstall
===>  Deinstalling for java/eclipse
===>   Deinstalling eclipse-3.3.2
pkg_delete: package 'eclipse-3.3.2' is required by these other packages
and may not be deinstalled (but I'll delete it anyway):
subclipse-1.2.4_1
pkg_delete: unable to completely remove directory '/usr/local/eclipse/features'
pkg_delete: unable to completely remove directory '/usr/local/eclipse/plugins'
pkg_delete: unable to completely remove directory '/usr/local/eclipse'
pkg_delete: couldn't entirely delete package (perhaps the packing list is
incorrectly specified?)
KV_BSD#

[Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 670 packages found (-1 +0) (...) done]
--->  Backing up the old version
--->  Uninstalling the old version
--->  Deinstalling 'gnome-control-center-2.20.1_1'
--->  Preserving /usr/local/lib/libgnome-window-settings.so.1 as /usr/local/lib/compat/pkg/libgnome-window-settings.so.1
pkg_delete: package 'gnome-control-center-2.20.1_1' is required by these other packages
and may not be deinstalled (but I'll delete it anyway):
alacarte-0.11.3_2
deskbar-applet-2.20.1
gnome-applets-2.20.0
gnome-games-2.20.1
gnome-session-2.20.1_1
gnome2-2.20.1
py25-gnome-desktop-2.20.0
totem-2.20.1

Connection to nova.cs.berkeley.edu closed.
KV_BSD% su -
Password:
KV_BSD# ps -aux | clean
zsh: command not found: clean
KV_BSD# set -o vi
KV_BSD# ps -aux | grep clean
KV_BSD# ps -aux | grep make
root  25132  0.0  0.1  2912  1396  p2  I+    2:56PM   0:00.53 make install clea
root  46478  0.0  0.1  4120  1320  p4  I+    2:58PM   0:00.01 gmake all
root  46483  0.0  0.1  4120  1432  p4  S+    2:58PM   0:00.03 gmake all
root  74402  0.0  0.1  2912  1440  p4  Is+   2:49PM   0:01.63 make
root  81057  0.0  0.1  4120  1280  p4  I+    2:51PM   0:00.01 gmake -f Makefile
root  81058  0.0  0.1  4120  1324  p4  I+    2:51PM   0:00.01 gmake all-recursi
KV_BSD# kill 25132
KV_BSD#

ol-center-2.22.2.1'
[Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 670 packages found (-1 +0) (...) done]
--->  Backing up the old version
--->  Uninstalling the old version
--->  Deinstalling 'gnome-control-center-2.20.1_1'
--->  Preserving /usr/local/lib/libgnome-window-settings.so.1 as /usr/local/lib/compat/pkg/libgnome-window-settings.so.1
pkg_delete: package 'gnome-control-center-2.20.1_1' is required by these other packages
and may not be deinstalled (but I'll delete it anyway):
alacarte-0.11.3_2
deskbar-applet-2.20.1
gnome-applets-2.20.0
gnome-games-2.20.1
gnome-session-2.20.1_1
gnome2-2.20.1
py25-gnome-desktop-2.20.0
totem-2.20.1

py25-gnome-desktop-2.20.0
totem-2.20.1
[Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 669 packages found (-1 +0) (...) done]
--->  Installing the new version via the port
===>  Installing for gnome-control-center-2.22.2.1_1
===>   gnome-control-center-2.22.2.1_1 depends on executable: gnome-eject - found
===>   gnome-control-center-2.22.2.1_1 depends on file: /usr/local/libexec/gnome-settings-daemon - not found
===>    Verifying reinstall for /usr/local/libexec/gnome-settings-daemon in /usr/ports/sysutils/gnome-settings-daemon
=> gnome-settings-daemon-2.22.2.1.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/.
=> Attempting to fetch from ftp://ftp.belnet.be/mirror/ftp.gnome.org/sources/gnome-settings-daemon/2.22/.
gnome-settings-daemon-2.22.2.1.tar.bz2         63% of 1112 kB  218 kBps

-settings-daemon-2.22.2.1_1
configure: WARNING: Unrecognized options: --with-html-dir, --disable-gtk-doc
checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/local/bin/gmkdir -p
checking for gawk... gawk
checking whether gmake sets $(MAKE)... yes
checking how to create a ustar tar archive... gnutar
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by gmake... GNU
checking for gcc... cc
checking for C compiler default output file name... a.out
checking whether the C compiler works...

   eclipse-devel-3.4.1_1 depends on shared library: pango-1.0.0 - found
===>  Configuring for eclipse-devel-3.4.1_1
===>  Building for eclipse-devel-3.4.1_1
[: missing ]
     [echo] TARGET: compiler
     [echo] UPDATE ecj.jar

BUILD SUCCESSFUL
Total time: 42 seconds
     [echo] TARGET: compiler2
     [echo] compilerArg -enableJavadoc -nowarn -encoding ISO-8859-1
     [echo] build compiler org.eclipse.jdt.core.JDTCompilerAdapter
     [echo] UPDATE ecj.jar

BUILD SUCCESSFUL
Total time: 44 seconds
     [echo] Deleting jars to recompile...
     [echo] Compiling SWT native libraries...
     [exec] callback.c: In function 'Java_org_eclipse_swt_internal_Callback_bind':
     [exec] callback.c:493: warning: unused variable 'pad'

[javac] Iterator is a raw type. References to generic type Iterator<E> should be parameterized
    [javac] ----------
    [javac] 63. WARNING in /usr/ports/java/eclipse-devel/work/plugins/org.eclipse.equinox.launcher/src/org/eclipse/equinox/launcher/WebStartMain.java (at line 306)
    [javac]     ArrayList toAdd = (ArrayList) iterator.next();
    [javac]     ^^^^^^^^^
    [javac] ArrayList is a raw type. References to generic type ArrayList<E> should be parameterized
    [javac] ----------
    [javac] 64. WARNING in /usr/ports/java/eclipse-devel/work/plugins/org.eclipse.equinox.launcher/src/org/eclipse/equinox/launcher/WebStartMain.java (at line 306)
    [javac]     ArrayList toAdd = (ArrayList) iterator.next();
    [javac]                        ^^^^^^^^^
    [javac] ArrayList is a raw type. References to generic type ArrayList<E> should be parameterized
    [javac] ----------
    [javac] 65. WARNING in /usr/ports/java/eclipse-devel/work/plugins/org.eclipse.equinox.launcher/src/org/eclipse/equinox/launcher/WebStartMain.java (at line 307)
    [javac]     for (Iterator iterator2 = toAdd.iterator(); iterator2.hasNext();) {
    [javac]          ^^^^^^^^
    [javac] Iterator is a raw type. References to generic type Iterator<E> should be parameterized
    [javac] ----------
    [javac] 65 problems (65 warnings)

(cd /usr/ports/java/eclipse-devel/work/eclipse;  /bin/cp -R about.html epl-v10.html icon.xpm notice.html readme /usr/local/eclipse-devel)
===>   Registering installation for eclipse-devel-3.4.1_1
pkg_create: dependency loop detected for package eel-2.22.2_1
pkg_create: dependency loop detected for package eel-2.22.2_1
pkg_create: dependency loop detected for package gnome-desktop-2.22.3
pkg_create: dependency loop detected for package eel-2.22.2_1
pkg_create: dependency loop detected for package gnome-desktop-2.22.3
pkg_create: dependency loop detected for package eel-2.22.2_1
pkg_create: dependency loop detected for package gnome-desktop-2.22.3
pkg_create: dependency loop detected for package gvfs-0.2.5
pkg_create: dependency loop detected for package libgnomeui-2.22.1_2
pkg_create: dependency loop detected for package eel-2.22.2_1
pkg_create: dependency loop detected for package gnome-desktop-2.22.3
pkg_create: dependency loop detected for package gvfs-0.2.5
pkg_create: dependency loop detected for package libgnomeui-2.22.1_2
pkg_create: dependency loop detected for package nautilus-2.22.5.1_1
===>  Cleaning for eclipse-devel-3.4.1_1
KV_BSD#

I'm having serious deja vu with this evolution stuff.. wait SPAMASSASSIN.. is that for if I were
running a mail server?

        Options for evolution 2.22.3.1                      
         
            [ ] PILOT         Enable Palm Pilot sync support             
            [X] LDAP          Enable LDAP support                        
            [ ] SPAMASSASSIN  Enable SpamAssassin spam filtering         
                                                                         
                                                                         
                                                                         
                                                                         
                                                                         
                                                                         
                                                                         
                                                                         
                                                                         
                                                                         
                                                                         
                                                                         
     $  
                            [  OK  ]       Cancel                          
       
                                                         

oh that's that infinite loop blocker you were talking about?

still working on that freek evoluation thing.  might be I have a sloooooww processor!

                                                        ^
mk/evolution.xml:6907: parser error : Entity 'rdquo' not defined
o_dialog-info.png"/> icon is displayed with a &ldquo;for-your-information&rdquo;
                                                                               ^
xsltproc -o evolution-mk.omf --stringparam db2omf.basename evolution --stringparam db2omf.format 'docbook' --stringparam db2omf.dtd "-//OASIS//DTD DocBook XML V4.1.2//EN" --stringparam db2omf.lang mk --stringparam db2omf.omf_dir "/usr/local/share/omf" --stringparam db2omf.help_dir "/usr/local/share/gnome/help" --stringparam db2omf.omf_in "/usr/ports/mail/evolution/work/evolution-2.22.3.1/help/evolution.omf.in"  --stringparam db2omf.scrollkeeper_cl "`scrollkeeper-config --pkgdatadir`/Templates/C/scrollkeeper_cl.xml" `/usr/local/bin/pkg-config --variable db2omf gnome-doc-utils` mk/evolution.xml || { rm -f "evolution-mk.omf"; exit 1; }
gmake[2]: Leaving directory `/usr/ports/mail/evolution/work/evolution-2.22.3.1/help'
gmake[2]: Entering directory `/usr/ports/mail/evolution/work/evolution-2.22.3.1'
gmake[2]: Nothing to be done for `all-am'.
gmake[2]: Leaving directory `/usr/ports/mail/evolution/work/evolution-2.22.3.1'
gmake[1]: Leaving directory `/usr/ports/mail/evolution/work/evolution-2.22.3.1'
[Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 672 packages found (-0 +1) . done]
--->  Backing up the old version

nome-2 -lpopt -ledataserver-1.2 -lxml2 -lgconf-2 -lbonobo-2 -lbonobo-activation -lgmodule-2.0 -lORBit-2 -lgthread-2.0 -lgobject-2.0 -lglib-2.0 -liconv )  

*** Warning: Linking the shared library liborg-gnome-evolution-startup-wizard.la against the loadable module
*** libevolution-calendar.so is not portable!

*** Warning: Linking the shared library liborg-gnome-evolution-startup-wizard.la against the loadable module
*** libevolution-mail.so is not portable!

2 -lpopt -ledataserver-1.2 -lxml2 -lgconf-2 -lbonobo-2 -lbonobo-activation -lgmodule-2.0 -lORBit-2 -lgthread-2.0 -lgobject-2.0 -lglib-2.0 -liconv )  

*** Warning: Linking the shared library liborg-gnome-exchange-operations.la against the loadable module
*** libevolution-calendar.so is not portable!

*** Warning: Linking the shared library liborg-gnome-exchange-operations.la against the loadable module
*** libevolution-mail.so is not portable!

*** Warning: Linking the shared library liborg-gnome-exchange-operations.la against the loadable module
*** libevolution-addressbook.so is not portable!

g directory `/usr/ports/x11-themes/gnome-themes/work/gnome-themes-2.22.2'
===>   Registering installation for gnome-themes-2.22.2_1
pkg_create: dependency loop detected for package eel-2.22.2_1
pkg_create: dependency loop detected for package eel-2.22.2_1
pkg_create: dependency loop detected for package gnome-desktop-2.22.3
pkg_create: dependency loop detected for package eel-2.22.2_1
pkg_create: dependency loop detected for package gnome-desktop-2.22.3
pkg_create: dependency loop detected for package eel-2.22.2_1
pkg_create: dependency loop detected for package gnome-desktop-2.22.3
pkg_create: dependency loop detected for package gvfs-0.2.5
pkg_create: dependency loop detected for package libgnomeui-2.22.1_2
pkg_create: dependency loop detected for package eel-2.22.2_1
pkg_create: dependency loop detected for package gnome-desktop-2.22.3
pkg_create: dependency loop detected for package gvfs-0.2.5
pkg_create: dependency loop detected for package libgnomeui-2.22.1_2
pkg_create: dependency loop detected for package nautilus-2.22.5.1_1
===>  Cleaning for gnome-themes-2.22.2_1
--->  Cleaning out obsolete shared libraries
[Updating the pkgdb <format:bdb_btree> in /var/db/pkg

When I don't know stuff is, I tend to check yes just in case.. e.g. here one thing was checked and I just decided to check them all

      For more information, and contact details about the security
      status of this software, see the following webpage:
http://www.burtonini.com/blog/computers/sound-juicer/
===>  Cleaning for sound-juicer-2.22.0_4
--->  Cleaning out obsolete shared libraries
[Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 672 packages found (-0 +1) . done]
--->  Upgrading 'totem-2.20.1' to 'totem-2.22.2_2' (multimedia/totem)
--->  Building '/usr/ports/multimedia/totem'
===>  Cleaning for totem-2.22.2_2
cd /usr/ports/multimedia/totem && make config;


     
                         Options for totem 2.22.2_2                        
         
        [X] LIRC           Enable lirc support                           
        [X] GALAGO         Enable Galago support                         
        [X] GECKO_PLUGINS  Enable install plugins for gecko browser      
        [X] PUBLISH        Enable Publish (network playlist) plugin      
        [X] TRACKER        Enable tracker local search plugin            
                                                                         
                                                                         
                                                                         
                                                                         
                                                                         
                                                                         
                                                                         
                                                                         
                                                                         
                                                                         
     $  
                            [  OK  ]       Cancel                          
       
                                                                             

 totem is using firefox for gecko support, but you can
 change that by defining WITH_GECKO to the following values:

   firefox
   mozilla
   seamonkey
   xulrunner

===> The default DVD device is /dev/acd0
===> Define WITH_DVD_DEVICE if you want to change the default
===> For example, 'make WITH_DVD_DEVICE="/dev/somedevice"'
===>  Found saved configuration for totem-2.22.2_2
=> totem-2.22.2.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/gnome2.
=> Attempting to fetch from ftp://ftp.belnet.be/mirror/ftp.gnome.org/sources/totem/2.22/.
totem-2.22.2.tar.bz2                          100% of 2347 kB  246 kBps
===>  Extracting for totem-2.22.2_2
=> MD5 Checksum OK for gnome2/totem-2.22.2.tar.bz2.

Do I have obsessive-compulsive widget disorder?  {:(

:46: error: 'GWeatherApplet' has no member named 'gconf'
gmake[2]: *** [main.o] Error 1
gmake[2]: Leaving directory `/usr/ports/x11/gnome-applets/work/gnome-applets-2.22.3/gweather'
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.1116.0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=gnome-applets-2.20.0 UPGRADE_PORT_VER=2.20.0 make reinstall
--->  Restoring the old version

OMFG

-->  Cleaning out obsolete shared libraries
[Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 693 packages found (-0 +1) . done]
--->  Skipping 'x11/gnome2' (gnome2-2.20.1) because a requisite package 'seahorse-2.20.1' (security/seahorse) failed (specify -k to force)
** Listing the failed packages (-:ignored / *:skipped / !:failed)
        - ftp/curl (marked as IGNORE)
        - x11-drivers/xf86-video-i810 (marked as IGNORE)
        ! multimedia/ffmpeg (ffmpeg-2007.10.04_1)       (unknown build error)
        * security/gnupg (gnupg-2.0.4)
        * net/opal (opal-2.2.8_1)
        * x11-drivers/xorg-drivers (xorg-drivers-7.3)
        * x11/xorg (xorg-7.3_1)
        ! graphics/evince (evince-2.20.1)       (configure error)
        * net/ekiga (ekiga-2.0.9_1)
        * security/seahorse (seahorse-2.20.1)
        ! x11/gnome-applets (gnome-applets-2.20.0)      (install error)
        * x11/gnome2 (gnome2-2.20.1)
You have new mail.                                                              
KV_BSD#

oooh nooo! You went bye bye  {:(  

I make another question?  I totally crashed my X

ooookay.. I killed the SEAHORSE!  DEATH TO THE SEAHORSE!!

that did the trick..

hrm..

I have Ganymede.

BUT IT REMAINS...

HOW DO I INSTALL MY DOO DOO?

I'm still comfused {:*

My Ganymede is a nice deep poiple

Oh disaster.  I am following the directions but things don't look quite the same.
external-tool.png

double down or nothing!  {:D

https://www.experts-exchange.com/Programming/Editors_IDEs/Java/Eclipse/Q-23893444-external-tool-causes-eclipse-puke.html

I didn't go bye bye... I just wasn't sure what you wanted with all those listings you posted...

In your last screenshot I see that location says:
nachos.machine.Machine

SHouldn't that be localhost? Or the path to the project?

Did you follow these steps already?
http://inst.eecs.berkeley.edu/~cs162/fa08/Nachos/eclipse/#nachoscvs
(all steps UNTIL the 'Importing Nachos From the Filesystem' section)

and then
http://inst.eecs.berkeley.edu/~cs162/fa08/Nachos/eclipse/#nachosrun

and then
http://inst.eecs.berkeley.edu/~cs162/fa08/Nachos/eclipse/#eclipsecvs

If so, where EXACTLY did it go wrong?

It's going wrong on the second.. in the Run->Run

I realized that this link

http://inst.eecs.berkeley.edu/~cs162/fa08/Nachos/eclipse/#nachosfs

tells me I don't have to deal with the Windoze network nightmare and go with
the gold ole unix command that has been working super for me i.e.

"svn co https://isvn.eecs.berkeley.edu/cs162/group6/trunk/nachos"

and then I have a new directory structure starting from nachos revision 97
now.  I have been making directories and saving many copies of this
_BSD% ls *08
nov06_08:
nachos

nov08_08:
nachos

nov10_08:
nachos

oct23_08:
nachos

oct24_08:
nachos

oct27_08:
nachos
KV_BSD% ls -d *08
nov06_08      nov10_08      oct24_08
nov08_08      oct23_08      oct27_08
KV_BSD% cd n
nachos/    nov06_08/  nov08_08/  nov10_08/


If I make sure to start up eclipse in the correct date directory, then it seems to like using nachos
from source...at least to a point