Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 225329 - Build of eclipse-cdt bogged down by warnings
Build of eclipse-cdt bogged down by warnings
Product: Fedora
Classification: Fedora
Component: eclipse (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ben Konrath
Depends On:
  Show dependency treegraph
Reported: 2007-01-29 17:13 EST by Jeff Johnston
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 3.2.2-1.fc6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-02-21 16:43:47 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jeff Johnston 2007-01-29 17:13:05 EST
Description of problem:
Attempting to build eclipse-cdt for FC6 is getting bogged down with access
restriction warnings of the type:

    [javac] 74. WARNING in
    [javac]  (at line 181)
    [javac] 	return new Status(IStatus.WARNING, CCorePlugin.PLUGIN_ID, -1,
Util.bind("convention.namespace.dollarName"), null); //$NON-NLS-1$
    [javac] 	                          ^^^^^^^
    [javac] Access restriction: The field WARNING from the type IStatus is not
accessible due to restriction on classpath entry

Version-Release number of selected component (if applicable):

How reproducible:

Attempt to build eclipse-cdt rpm under FC6 brew.

Actual results:

Very slow build with warnings on every line.

Expected results:

Reasonably quick build.

Additional info:

Problem does not appear to be in rawhide.  Same rpm sources built quickly there.
Comment 1 Ben Konrath 2007-01-29 17:26:40 EST
This is caused by a bug in the ecj-square-brakets patch. I just fixed it in
rawhide so I'll push an update to FC6 with the updated patch. Thanks.
Comment 2 Ben Konrath 2007-02-21 16:43:47 EST
This is fixed in the upcoming 3.2.2-1.fc6 update. Thanks.

Note You need to log in before you can comment on or make changes to this bug.