caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Eray Ozkural <examachine@gmail.com>
Cc: Caml List <caml-list@inria.fr>
Subject: AW: [Caml-list] Re: Ocaml 4.0 build error on Darwin i386
Date: Thu, 07 Feb 2013 16:18:08 +0100	[thread overview]
Message-ID: <1360250288.18230.8@samsung> (raw)
In-Reply-To: <CA+rXZpaR8zz2yYss4p=hAVatEwHkvbraaMQa=ZnTgiDVdSNUSg@mail.gmail.com> (from examachine@gmail.com on Thu Feb  7 15:57:32 2013)

That's in the stack overflow detection code. If it does not work, you  
can disable it (by undef'ing HAS_STACK_OVERFLOW_DETECTION in s.h after  
running "configure"). Maybe Fink is doing this.

Gerd

Am 07.02.2013 15:57:32 schrieb(en) Eray Ozkural:
> More information on my problem. GODI fails with the same errors using  
> 3.12.
> Fink package for 3.12 compiles successfully. What could be the culprit
> here?
> 
> On Thu, Feb 7, 2013 at 1:51 PM, Eray Ozkural <examachine@gmail.com>  
> wrote:
> 
> > I receive the same error with both GODI and OPAM. I remember this  
> error
> > from somewhere but I couldn't figure out how to resolve it.
> >
> > It's Darwin 11.2.0, 64-bit kernel and extensions are turned off on  
> this
> > system. I remember that I could compile this code on an x64 kernel.
> >
> > ....
> > gcc -I../byterun -DCAML_NAME_SPACE -DNATIVE_CODE -DTARGET_amd64
> > -DSYS_macosx  -O -D_FILE_OFFSET_BITS=64 -D_REENTRANT -I/sw/include   
> -c -o
> > signals_asm.o signals_asm.c
> > signals_asm.c: In function ‘segv_handler’:
> > signals_asm.c:206: error: ‘struct __darwin_mcontext64’ has no  
> member named
> > ‘ss’
> > signals_asm.c:206: error: ‘struct __darwin_mcontext64’ has no  
> member named
> > ‘ss’
> > signals_asm.c:206: error: ‘struct __darwin_mcontext64’ has no  
> member named
> > ‘ss’
> > signals_asm.c:206: error: ‘struct __darwin_mcontext64’ has no  
> member named
> > ‘ss’
> > signals_asm.c:206: error: ‘struct __darwin_mcontext64’ has no  
> member named
> > ‘ss’
> > signals_asm.c:211: error: ‘struct __darwin_mcontext64’ has no  
> member named
> > ‘ss’
> > signals_asm.c:212: error: ‘struct __darwin_mcontext64’ has no  
> member named
> > ‘ss’
> >
> >
> > --
> > Eray Ozkural
> >
> >
> 
> 
> --
> Eray Ozkural
> 
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs



-- 
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany    gerd@gerd-stolpmann.de
Creator of GODI and camlcity.org.
Contact details:        http://www.camlcity.org/contact.html
Company homepage:       http://www.gerd-stolpmann.de
------------------------------------------------------------

      reply	other threads:[~2013-02-07 15:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07 11:51 [Caml-list] " Eray Ozkural
2013-02-07 14:57 ` [Caml-list] " Eray Ozkural
2013-02-07 15:18   ` Gerd Stolpmann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1360250288.18230.8@samsung \
    --to=info@gerd-stolpmann.de \
    --cc=caml-list@inria.fr \
    --cc=examachine@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).