[Mono-dev] Segmentation Fault on Solaris 10 Build (mono 1.2.3.1)
Iain Jackson
iain.jackson at memex.com
Thu Apr 5 04:30:45 EDT 2007
Hi,
I'm currently having an issue with building mono 1.2.3.1 on Solaris 10
06/06 on SPARC. The build process gets as far as executing the mcs
compiler where the mono runtime crashes with a segmentation fault.
How I'm building it:
export PATH=/usr/local/bin:/usr/sfw/bin:/usr/ccs/bin:/usr/bin
export PKG_CONFIG_PATH=/opt/mono/lib/pkgconfig
export LD_LIBRARY_PATH=/opt/mono/lib:/usr/local/lib
./configure --prefix="/opt/mono"
gmake get-monolite-latest
gmake
To compile it I'm using gcc 3.4.4 which I've installed in
/usr/local/bin. I've compiled my own copy of glib2 (2.12.11) into
/opt/mono. I've attached logs from configure and make in case these
are of any use.
I took a stack trace from the crashed process and it receives the
signal in GC_read_dirty() when it initialises the garbage collector.
Has anyone seen this problem before? Is there a flag or option that
needs to be set when building on Solaris?
Thanks,
Iain
---
Iain Jackson
Software Engineer
Memex Technology Ltd.
Tel: +44 (0)1355 233804
Fax: +44 (0)1355 239767
<http://www.memex.co.uk> www.memex.co.uk
Memex Technology Ltd.
Registered in: Scotland Company number: SC215165
Registered Office: 2 Redwood Court, Peel Park, East Kilbride, G74 5PF
Confidentiality and Proprietary Rights Notice:
-----------------------------------------------
The information contained in this e-mail message, including any and all
attachments, is for the sole use of the intended recipient(s) and contains
information that Memex Technology Ltd. and Memex, Inc. consider confidential
and proprietary. If the reader of this message is not the intended recipient
or an agent responsible for delivering it to the intended recipient, you are
hereby notified that you have received this document in error and that any
review, dissemination, distribution, or copying of this message is strictly
prohibited. If you have received this communication in error, please notify
us immediately by e-mail, and delete the original message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20070405/feaf83a7/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.log.gz
Type: application/octet-stream
Size: 25069 bytes
Desc: not available
Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20070405/feaf83a7/attachment.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mono-build.log.gz
Type: application/octet-stream
Size: 40307 bytes
Desc: not available
Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20070405/feaf83a7/attachment-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mono-configure.log.gz
Type: application/octet-stream
Size: 3709 bytes
Desc: not available
Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20070405/feaf83a7/attachment-0002.obj
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: stack_trace.txt
Url: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20070405/feaf83a7/attachment.txt
More information about the Mono-devel-list
mailing list