Description of problem: Attempting to build eclipse-cdt on s390x results in the following error: [javac] 1. ERROR in /builddir/build/BUILD/eclipse-cdt-3.1.0/org.eclipse.cdt.releng/results/plugins/org.eclipse.cdt.ui/src/org/eclipse/cdt/internal/ui/dialogs/MessageLine.java [javac] [reading org/eclipse/jface/dialogs/Dialog.class] [javac] [reading org/eclipse/jface/window/Window.class] [javac] [reading org/eclipse/jface/window/IShellProvider.class] [javac] [567 units compiled] [javac] (at line 27) [javac] public class MessageLine extends CLabel { [javac] ^^^^^^ [javac] The type org.eclipse.swt.custom.CLabel cannot be resolved. It is indirectly referenced from required .class files [javac] ---------- [javac] 1 problem (1 error) Version-Release number of selected component (if applicable): 3.2.0-6.fc6 How reproducible: Always Steps to Reproduce: 1. make build in eclipse-cdt/devel Actual results: Build fails. Expected results: Build succeeds Additional info: Brew task 250509
Does it even make sense to build CDT on s390x? The CDT has a fragment with native libs (org.eclipse.cdt.core.linux.x86) and it won't work unless this is ported to s390x. I propose we only build CDT on the arches that upstream supports and revert eclipse-changelog back to the arches that the CDT supports. What do you think?
(In reply to comment #1) > > I propose we only build CDT on the arches that upstream supports and revert > eclipse-changelog back to the arches that the CDT supports. What do you think? I think this sounds good.
Ok, I reverted the update; we only build CDT on these arches again: ExclusiveArch: %{ix86} x86_64 ppc ia64 I also fixed changelog to only build on this arches and fired off a build. Closing bug.