Hi John -- Hmm, it happens in my runtime workspace on Windows but
not in 6.0.1 installed from the update site onto EPP. The weird
thing is, I made a fresh clone of the Git repository late last
night, and it happened in my runtime workspace there too. So I'm
not really sure why it would behave differently in a runtime
workspace than in an installation... but anyway I'm glad the
installed version seems to work fine.
Curious - have you updated JGit, CDT, etc.? It may be some interaction with an older library.
Do you still want a bug report, then?
Yes, we should try to figure it out anyway, so it doesn't come back to haunt us later.
John/Dave/Greg -- Regarding the dependencies, I got the same errors,
but IIRC, the Cray/compilers and OpenACC features shouldn't be
available anymore, since those were moved into PTP Core and PLDT,
respectively... so I think those could just be pulled from the
update site... (?)
Back to the topic of this thread -- Greg, I'm +1 for 6.0.1 if you
still want to get it out ASAP, or I'd be fine with Monday/Tuesday
next week too; I could do some more complete testing then.
I tried creating a few synchronized projects with 6.0.1 (openSUSE linux 32-bit). It seems to work fine, so I also give a +1.
John
Jeff
On 6/29/12 2:11 PM, John Eblen wrote:
Hi Jeff
I downloaded Juno, installed PTP 6.0.1, and tried to
reproduce this error on a Windows 7 machine,
but it compiles fine. Is this a problem in your development
environment or does it happen with a
fresh install of 6.0.1?
Please file a detailed bug, which includes the project type
and toolchains that you were using as
well as stack traces and console output. (The more detail the
better chance that it can be reproduced.)
Did this error occur when the project was first created or
later? Does it always
happen or only rarely? Did you change any settings for the
project?
It's happening for newly-created projects; I'm building
immediately after the New Project wizard finishes. So no
changes -- just the defaults for the new project -- and it
happens deterministically for me (Vista 32-bit). I can file
a bug and post the stack traces if that would help...