Home » Eclipse Projects » Linux Tools Project » After upgrade to 2.0 Autotools does not work(autotools)
| After upgrade to 2.0 Autotools does not work [message #503121] |
Thu, 10 December 2009 18:08  |
Eclipse User |
|
|
|
I've just updated Autotools to 2.0 and now they do not work.
The Autotools project category and all information in the project configuration dialog is gone.
I'm running Eclipse 3.5.1 with CDT 6.0 on Mac OS X 10.5.8.
Any ideas?
Thanks!
|
|
| | | | | | | | |
| Re: After upgrade to 2.0 Autotools does not work [message #628907 is a reply to message #503121] |
Fri, 24 September 2010 12:47  |
| Eclipse User |
|
|
|
OK, well here is the log data that I think is relevant:
smithrm-mac:eclipse smithrm$ ./eclipse -clean -consoleLog
!SESSION 2010-09-21 13:22:01.745 -----------------------------------------------
eclipse.buildId=
java.version=1.5.0_24
java.vendor=Apple Inc.
BootLoader constants: OS=macosx, ARCH=x86, WS=cocoa, NL=en_US
Framework arguments: -product org.eclipse.epp.package.cpp.product
Command-line arguments: -os macosx -ws cocoa -arch x86 -product org.eclipse.epp.package.cpp.product -clean -consoleLog
<other data deleted>
!ENTRY org.eclipse.ui 4 4 2010-09-21 13:22:14.299
!MESSAGE Plug-in 'org.eclipse.linuxtools.systemtap.ui.dashboardextension' contributed an invalid Menu Extension (Path: 'file2' is invalid): org.eclipse.linuxtools.systemtap.ui.dashboardextension.actio ns.ExportScript
!ENTRY org.eclipse.ui 4 4 2010-09-21 13:22:14.324
!MESSAGE Plug-in 'org.eclipse.linuxtools.systemtap.ui.dashboardextension' contributed an invalid Menu Extension (Path: 'file2' is invalid): org.eclipse.linuxtools.systemtap.ui.dashboardextension.actio ns.CreateModuleAction
!ENTRY org.eclipse.jface 2 0 2010-09-21 13:22:14.519
!MESSAGE Keybinding conflicts occurred. They may interfere with normal accelerator operation.
!SUBENTRY 1 org.eclipse.jface 2 0 2010-09-21 13:22:14.519
!MESSAGE A conflict occurred for ALT+CTRL+P:
Binding(ALT+CTRL+P,
ParameterizedCommand(Command(org.eclipse.linuxtools.changelo g.core.preparechangelog,Prepare Changelog,
Prepares Changelog,
Category(org.eclipse.linuxtools.changelog,Changelog,Changelo g key bindings,true),
org.eclipse.linuxtools.changelog.core.actions.PrepareChangel ogKeyHandler,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)
Binding(ALT+CTRL+P,
ParameterizedCommand(Command(org.eclipse.team.svn.ui.command .CreatePatchCommand,Create Patch...,
,
Category(org.eclipse.team.svn.ui.command.category,SVN,null,t rue),
ActionDelegateHandlerProxy(null,org.eclipse.team.svn.ui.acti on.local.CreatePatchAction),
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)
!SUBENTRY 1 org.eclipse.jface 2 0 2010-09-21 13:22:14.519
!MESSAGE A conflict occurred for COMMAND+P:
Binding(COMMAND+P,
ParameterizedCommand(Command(org.eclipse.linuxtools.systemta p.ui.graphicalrun.commands.ModifyParsing,Modify &Parsing Expression,
Modify Parsing Expression,
Category(org.eclipse.linuxtools.systemtap.ui.graphing.catego ry.edit,%category.edit.name,%category.edit.desc,true),
,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)
Binding(COMMAND+P,
ParameterizedCommand(Command(org.eclipse.ui.file.print,Print ,
Print,
Category(org.eclipse.ui.category.file,File,null,true),
,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)
!ENTRY org.eclipse.core.net 1 0 2010-09-21 13:22:14.774
!MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences
|
|
|
| Re: After upgrade to 2.0 Autotools does not work [message #629345 is a reply to message #628907] |
Mon, 27 September 2010 17:12 |
| Eclipse User |
|
|
|
The only thing of note in the log is the SystemTap plugin UI issues. It might be possible this is causing UI issues during loading.
Try renaming your ~/.eclipse file. There is plugin information stored in the .metadata and sometimes upgrades cause problems as data is cached and there are invalid references that are still around.
Failing this, you can try uninstalling the SystemTap plugins to see if that helps.
If that doesn't solve the issue, there may be dependencies for the Autotools plugins that are not being loaded, though I would have expected to see some messages in your log file.
How did you do your upgrade - via the Eclipse update site or did you use an rpm?
If you upgraded via the update site, go to Help->About Eclipse Platform->Installation Details->Plugins you can verify what, if any, Autotools plugins are recognized and loaded. If they aren't noted there and you used an update site, check to see if the plugins actually exist in your eclipse/plugins directory. If they are there, you'll have to look at the MANIFEST.MF files for the plugin dependencies and check to see if the dependencies are recognized by Eclipse. If missing, you have to repeat the process to find the lowest level culprit.
|
|
|
Goto Forum:
Current Time: Mon Jun 30 23:10:33 EDT 2025
Powered by FUDForum. Page generated in 0.03993 seconds |
Home