Bug 5907 - Recent patches broke build (at least on MinGW) - syscall_signal
Summary: Recent patches broke build (at least on MinGW) - syscall_signal
Alias: None
Product: Runtime
Classification: Mono
Component: General ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-06-28 10:47 UTC by James Bellinger
Modified: 2012-06-28 19:37 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description James Bellinger 2012-06-28 10:47:37 UTC

I am now getting the error

../../../mono/utils/mono-threads-posix.c: In function ‘suspend_signal_handler’:
../../../mono/utils/mono-threads-posix.c:89: error: ‘MonoThreadInfo’ has no member named ‘syscall_signal’
../../../mono/utils/mono-threads-posix.c:90: error: ‘MonoThreadInfo’ has no member named ‘syscall_signal’
../../../mono/utils/mono-threads-posix.c: In function ‘mono_threads_core_abort_syscall’:
../../../mono/utils/mono-threads-posix.c:180: error: ‘MonoThreadInfo’ has no member named ‘syscall_signal’
make[4]: *** [mono-threads-posix.lo] Error 1

I did an earlier build two days ago and this did not occur.
Definitely some new change.
Comment 1 Zoltan Varga 2012-06-28 19:37:02 UTC
This is already fixed.