Yes, you can remove the slurm plugins as well if you want, but they won't cause any problems if you leave them be. They are in the current PTP build, but you don't need them in your workspace unless you plan to work on them.
Cheers, Greg On Jan 3, 2012, at 6:36 PM, David Alexander wrote:
Thanks Greg. When you say "these plugins" might that include
ptp.rm.slurm.* as I am seeing some errors there (it looks like it
has some C code and needs a Makefile generated from configure).
Dave Alexander
On 1/3/2012 3:32 PM, Greg Watson wrote:
You can remove these plugins from your workspace. This
is one of the "features" of using git. When you clone the repo,
you get everything.
Greg
On Jan 3, 2012, at 5:13 PM, Beth Tibbitts wrote:
I don't recognize
"smoa"
I include the following
because I think you want to know how to navigate this
stuff .... detective work commences...
I can't tell what
package the "JobThread" class is in, but based on the
imports for "org.eclipse.ptp.rm.smoa" and where your
package explorer view is scrolled to, it must be
related to resource managers.
Hmm I have similar
errors in mine (but obviously I don't pay attention to
build errors there do i?)
So I look in the
org.eclipse.ptp.rm.smoa.core MANIFEST.MF and it uses
descriptions from plugin.properties
which says
pluginName=PTP SMOA Computing Core
Bundle-Vendor = Poznan Supercomputing and Networking Center
remoteServices.name
= SMOA Computing
If I do Team>Show in
History I see Greg checked it in. A good while ago.
A bit of curious
googling says it's http://sourceforge.net/projects/smoa-project/
because I don't think it's the Sarasota Museum of
Arts.
RMs and SMOA, anyone???
Greg? My guess is it's
something you need the external jar or something for
SMOA. As either some invisible infrastructure or
something we are not using much.
In which case, if we
want to build it we need to update the wiki
instructions for where to get the missing pieces.
...Beth
Beth Tibbitts
Eclipse Parallel Tools Platform http://eclipse.org/ptp
IBM STG - High Performance Computing Tools
Mailing Address: IBM Corp., 745 West New Circle Road,
Lexington, KY 40511
<graycol.gif>David Alexander
---01/03/2012 04:48:02 PM---Thanks Beth. I wanted to
make sure I had a clean environment, so I started
over with a fresh downl
<ecblank.gif>
|
<ecblank.gif>
David Alexander
<alexanda@xxxxxxxxxx> |
<ecblank.gif>
|
<ecblank.gif>
ptp-dev@xxxxxxxxxxx,
|
<ecblank.gif>
|
<ecblank.gif>
01/03/2012
04:48 PM |
<ecblank.gif>
|
<ecblank.gif>
Re: [ptp-dev]
Developing Photran (and running PTP) with Juno
development version |
<ecblank.gif>
|
<ecblank.gif>
ptp-dev-bounces@xxxxxxxxxxx |
Thanks Beth. I wanted to make
sure I had a clean environment, so I started over with a
fresh download following the PTP setup page as closely
as I could. I got to the PTP/Photran build and am
getting a different "Problem" now. From the screen shot
below, you can see it is failing to find a package
com.smoa. This package is not an org.eclipse package.
Do I need to install this via the "Install New
Software"?
<48775281.gif>
Dave Alexander
On 1/3/2012 1:18 PM, Beth Tibbitts wrote:
> I am surprised I missed the RSE
No problems, that is very easy to do. Which is the
reason I recognize that error :)
If you get the UPC feature for CDT, it includes the
lrparser that it needs.
Aha! That's step 3 :-)
Thanks for debugging the wiki procedures for me
...Beth
Beth Tibbitts
Eclipse Parallel Tools Platform http://eclipse.org/ptp
IBM STG - High Performance Computing Tools
Mailing Address: IBM Corp., 745 West New Circle Road,
Lexington, KY 40511
<graycol.gif>David
Alexander ---01/03/2012 03:02:23 PM---Thanks for the
tips, Beth. I am surprised I missed the RSE, but yes
that made all of the PTP probl
Thanks for the tips, Beth. I am surprised I missed
the RSE, but yes that made all of the PTP problems go
away. Now, I am at the remaining CDT problems having
to deal with a couple of LPG packages not be found. I
don't see any reference to them in the setup page.
They are referenced in the CDT source... As you can
see I got one lpg package (lpg.runtime.java) from the
sourceforge project, but that seems like something I
should not have not needed to do.
<48428929.gif>
Dave Alexander
On 1/3/2012 12:08 PM, Beth Tibbitts wrote:
FWIW... setting up a (new) development set of source
codes can be complicated, and all of this is normal
:-)
> "No rule to
make target 'all'" error for ptp.rm.slurm.proxy
(which is some C code in PTP)
I ignore all those C projects myself, I'm not
developing them, only running them. Your mileage may
vary and I'm sure some others disagree
>below is my
Problems view.
I notice the first ones I see are probably because
you don't have RSE installed.
How do you tell? Double-click on one of those errors
and it will take you to the line in the source code
in the error.
e.g. blahblah cannot be resolved .... will probably
match an import at the top of that source file that
can't be found.
The package name of the import it's looking for
should help narrow it down.
In http://wiki.eclipse.org/PTP/environment_setup_60 under
Setup_for_development_of_PTP_6.0 one of the things I
mentioned you need to install is RSE (step 4)
If you install that it should force a restart of
your eclipse and a rebuild and those should go away
(and expose the next set :-) )
>I am bit
confused when you get a package from both "Install
New Software" and "clone of Git repo".
Basically yes.. "Install new software" installs
stuff into your eclipse installation, and "clone of
Git repo" checks out the projects (source code) into
your workspace.
Some installing will include an "SDK" which usually
means they include a jar? of source code so you can
find the source code anyway, without having it as
source code projects in your workspace.
Try fooling around with e.g. hyperlinking from a
java source code file (ctrl-click) to something you
don't have in your workspace. I think all the CDT
source is like this. Others probably too.
At the moment I don't know what we do with PTP... we
*should* include source code as an SDK feature...
Hope this helps...
...Beth
Beth Tibbitts
Eclipse Parallel Tools Platform http://eclipse.org/ptp
IBM STG - High Performance Computing Tools
Mailing Address: IBM Corp., 745 West New Circle
Road, Lexington, KY 40511
<graycol.gif>David
Alexander ---01/03/2012 01:08:02 PM---Hi Jeff,
Thanks for the answer. I saw the photran docs, but
they all say indigo
Hi Jeff,
Thanks for the answer. I saw the photran docs, but
they all say indigo and I am trying to work with the
juno code, so I wasn't sure if it directly applied.
I am not developing any PTP code at this point, but
I would like to run remotely to test my Photran
development. So I need at the jars, but I am also
just interested in learning the source, so I want to
build it as well.
Anyway, I reset all (CDT, PTP, Photran) to the
master branch; ran a "clean", then re-built. I am
now getting a "No rule to make target 'all'" error
for ptp.rm.slurm.proxy (which is some C code in PTP)
and below is my Problems view. Lots of PTP error,
some CDT, but no Photran. By the way, I am bit
confused when you get a package from both "Install
New Software" and "clone of Git repo". Without
thinking much, I guessed that the first gets you the
jar files and the second gets you the source, but
then I wondered what happened when the Git code is
compiled, which byte code used in the resulting
runtime app?
<48252863.gif>
--
David Alexander
On 12/30/2011 9:48 AM, Jeffrey Overbey wrote:
Hi David,
The master branches should be fine.
For Photran, the first couple of appendices in the
Photran Developer's Guide at http://www.eclipse.org/photran/contributorinfo.php describe how to check out
the sources, set up an API baseline, etc. -- they
should be (more or less) up to date. Hopefully
those will help you get rid of the errors in the
Photran-related projects. FWIW, if you're just
doing Photran development, you don't need the PTP
sources, so you should be able to follow those
instructions (starting from a fresh workspace) and
be done.
If you did want all of the PTP sources, I can't
say for sure what the errors are... they should
show up in the Problems view with more detail...
you might have to select the project in the
Package Explorer before its errors will appear...
(?)
Jeff
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
[attachment "alexanda.vcf" deleted by Beth
Tibbitts/Watson/IBM] _______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
[attachment "alexanda.vcf" deleted by Beth
Tibbitts/Watson/IBM] _______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
<alexanda.vcf>_______________________________________________ ptp-dev mailing list ptp-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/ptp-dev
|