Red Hat Bugzilla – Bug 157123
[miscompilation] libmngbuildcore.jar: Eclipse CDT managed makefile unusable
Last modified: 2007-11-30 17:11:05 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050504 Fedora/1.0.3-4 Firefox/1.0.3
Description of problem:
Eclipse managed makefile (C project) contains strings "null" where newlines ought to be. This makes the makefile unusable.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Create a C project with managed makefile in Eclipse
2.Create a "hello world" program
3.Corrupt makefile is unusable
Actual Results: Eclipse managed makefile contains strings "null" where a newline character "\n" ought to be. The same problem exists in the include files created by Eclipse.
Expected Results: Proper makefile and its include files should have been created.
Eclipse platform and CDT plugin downloaded from eclipse.org to a Fedora Core 3 platform do not exhibit this problem. This problem is seen on a Fedora Core 4 test 2 platform with the following Eclipse packages:
For what it's worth, I was just about to file this same bug. I'm seeing "null"
instead of "\n". Managed makefile projects are unusable right now.
Rick/Jeremy/Someone: can you please take a look at this?
This only happens when using gcj, everything is fine when using a JVM. Could be
a gcj-related bug? I have seen this in the past on other files too when using
gcj but everything is OK under a JVM.
This thing is pretty flaky. When I pull in the plugin that generates the
makefile and associated files and try to run as a runtime workbench with "print"
statements it seems to work fine, line breaks are put in correctly. Hmmm, may
have to just put print statements in and rebuild /reinstall. *sigh*
Sounds like it could be a miscompilation problem. Can you try moving the
offending jar.so out of the way (ie move it to jar.so.bk) and then start
eclipse and look for the bug again. BTW, which plugin generates the makefile?
I agree with your assessment that this is a miscompilation problem. I tried
what you suggested (moving offending jar to jar.bk) but when I do this I cannot
bring up the C Managed Build wizard to create a managed C project, I get this error:
The selected wizard could not be started:
reason: while resolving class
The plugin I renamed was org.eclipse.cdt.managedbuilder.core. The package/class
in there that seems to be causing the problem is
I can still check out that plugin and run in the runtime workbench and all the
files(makefile, objects.mk, sources.mk, subdir.mk) seem ok. One problem I do
get is that I cannot bring up the makefile in any editor. I get a long message
like "Unable to create editor. This message may be due to a bug in the
editor...blah, blah, blah". But I can look at the makefile with outside tools
and it looks fine.
I am using all of the latest compilers and versions of eclipse as of 5/10/2005.
Doing this worked for me:
I'm not sure what is causing the other errors. I'm going try to get this into
The work-around for this is in eclipse-cdt-3.0.0_fc-0.M6.6. I've requested that
this new package be included with FC4.
Current eclipse-cdt-3.0.0_fc-0.M6.7 also seems to work fine. I consider this