[Bug 1255741] New: nunit fails to build on ppc64le
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1255741
Bug ID: 1255741
Summary: nunit fails to build on ppc64le
Product: Fedora
Version: 23
Component: nunit
Assignee: timotheus.pokorra(a)solidcharity.com
Reporter: rdossant(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: claudiorodrigo(a)pereyradiaz.com.ar,
mono(a)lists.fedoraproject.org,
timotheus.pokorra(a)solidcharity.com
Blocks: 1051573 (PPC64LETracker), 1185763
Description of problem: nunit fails to build with the following error message:
/usr/lib/mono/4.5/Microsoft.Common.targets: error : Tool exited with code: 1.
Output: Error: Exception has been thrown by the target of an invocation.
Inner exception: A null reference or invalid value was found [GDI+ status:
InvalidParameter]
Tool /usr/lib/mono/4.5/resgen.exe execution started with
arguments: /useSourcePath /compile
"TestTree.resx,obj/Debug/NUnit.UiKit.TestTree.resources"
Tool /usr/lib/mono/4.5/resgen.exe execution started with
arguments: /useSourcePath /compile
"TextOutputSettingsPage.resx,obj/Debug/NUnit.UiKit.TextOutputSettingsPage.resources"
Tool /usr/lib/mono/4.5/resgen.exe execution started with
arguments: /useSourcePath /compile
"TipWindow.resx,obj/Debug/CP.Windows.Forms.TipWindow.resources"
Tool /usr/lib/mono/4.5/resgen.exe execution started with
arguments: /useSourcePath /compile
"TreeBasedSettingsDialog.resx,obj/Debug/NUnit.UiKit.TreeBasedSettingsDialog.resources"
/usr/lib/mono/4.5/Microsoft.Common.targets: error : Tool exited with code: 1.
Output: Error: Exception has been thrown by the target of an invocation.
Inner exception: A null reference or invalid value was found [GDI+ status:
InvalidParameter]
Task "GenerateResource" execution -- FAILED
Done building target "GenerateResources" in project
"/builddir/build/BUILD/nunitv2-2.6.4/src/GuiComponents/UiKit/nunit.uikit.dll.csproj".--
FAILED
Done building project
"/builddir/build/BUILD/nunitv2-2.6.4/src/GuiComponents/UiKit/nunit.uikit.dll.csproj".--
FAILED
Task "MSBuild" execution -- FAILED
Done building target "ResolveProjectReferences" in project
"/builddir/build/BUILD/nunitv2-2.6.4/src/GuiRunner/nunit-gui/nunit-gui.csproj".--
FAILED
Done building project
"/builddir/build/BUILD/nunitv2-2.6.4/src/GuiRunner/nunit-gui/nunit-gui.csproj".--
FAILED
Build FAILED.
Errors:
/builddir/build/BUILD/nunitv2-2.6.4/src/GuiRunner/nunit-gui/nunit-gui.csproj
(default targets) ->
/usr/lib/mono/4.5/Microsoft.Common.targets (ResolveProjectReferences target) ->
/builddir/build/BUILD/nunitv2-2.6.4/src/GuiComponents/UiKit/nunit.uikit.dll.csproj
(default targets) ->
/usr/lib/mono/4.5/Microsoft.Common.targets (GenerateResources target) ->
/usr/lib/mono/4.5/Microsoft.Common.targets: error : Tool exited with code:
1. Output: Error: Exception has been thrown by the target of an invocation.
Inner exception: A null reference or invalid value was found [GDI+ status:
InvalidParameter]
/usr/lib/mono/4.5/Microsoft.Common.targets: error : Tool exited with code:
1. Output: Error: Exception has been thrown by the target of an invocation.
Inner exception: A null reference or invalid value was found [GDI+ status:
InvalidParameter]
0 Warning(s)
2 Error(s)
Time Elapsed 00:00:07.7548090
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.qjZa6L (%build)
Version-Release number of selected component (if applicable): 2.6.4-9
How reproducible: ppc-koji build nonunit on ppc64le
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1051573
[Bug 1051573] ppc64le tracker bug
https://bugzilla.redhat.com/show_bug.cgi?id=1185763
[Bug 1185763] smuxi fails to build on ppc64le
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=NByEbd61Df&a=cc_unsubscribe
7 years, 11 months
- 1
- 3
it's just a bombshell!
by Paul F. Johnson
Hi,
Have you ever seen something like that? It's a bombshell you have to see! Look at it here <http://hitawysy.mauichiromax.com/aedsl>
My Best, paul(a)all-the-johnsons.co.uk
8 years
- 1
- 0
status update
by Timotheus Pokorra
Hello Mono SIG,
I thought I write a short update, to keep everyone on the same page.
* Fedora 24 will have the latest Mono 4.2 packages, see
https://releases.xamarin.com/stable-release-cycle-6-service-release-4/
The package will be submitted to updates after the F24 Freeze.
* Fedora 24 MonoDevelop: There is still no tarball for the latest
MonoDevelop, version 5.10.3.51 from Cycle6SR3
https://releases.xamarin.com/stable-release-cycle-6-service-release-3/
Jo at Xamarin/Microsoft is having trouble with his Jenkins server
which should build the tarball. He is working on it.
* Fedora Rawhide: has the final Mono 4.4 package. see
https://releases.xamarin.com/stable-release-cycle-7/. I want to keep
Mono 4.4 there until F25 is branched off. Then we can "experiment"
again with Alpha releases in rawhide.
* MonoDevelop 6: I would be good if we could get that into Fedora 25.
There are still some issues, the main issue that there is no tarball
provided yet. I did experiment with a tarball of an alpha version. We
would need a couple of new packages. see for details
https://bugzilla.redhat.com/show_bug.cgi?id=1313236
Help is certainly appreciated, or if someone wants to take the lead in
that task, you are very welcome!
* Epel7: I am still thinking how to do this best. I see that Ubuntu
16.04 LTS comes with Mono 4.2: see
http://packages.ubuntu.com/search?keywords=mono-complete and
https://packages.debian.org/search?keywords=mono-complete
I wonder if we should get Mono 4.2 into Epel7, and hope we can use any
security fixes that Debian/Ubuntu has. Still the life cycle of Ubuntu
16.04 only goes up to April 2021, while CentOS7 is supported till June
2024, according to https://linuxlifecycle.com/
Or should we just retire Mono 4.2 in Epel7 at some point, when we
cannot provide security updates anymore, in April 2021? Or upgrade to
the version we are using in Epel8 by then.
* Epel5: I suggest we retire Mono 1.2 (!!!) from Epel5.
* Epel6: I guess we have both options: retiring Mono 2.10, or updating
to Mono 4.2 as well, depending how much work it is in Epel7.
Let me know what you think! Any help appreciated, as always!
My wife will give birth to our first child within the next week, so I
don't know how much time will be available for packaging...
All the best,
Timotheus
8 years
- 2
- 1
- ← Newer
- 1
- Older →