caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Andres Varon <avaron@gmail.com>
To: Alain Frisch <alain@frisch.fr>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml version 3.11.0+beta1
Date: Wed, 15 Oct 2008 11:56:44 -0400	[thread overview]
Message-ID: <BE41BECE-FCC3-4D74-B982-BD1B6C89767E@gmail.com> (raw)
In-Reply-To: <48F60D13.2070302@frisch.fr>


On Oct 15, 2008, at 11:32 AM, Alain Frisch wrote:

> Daniel Bünzli wrote:
>> And on macosx ? It seems here on 10.5.5 that only dynlink.cma and  
>> dynlink.cmi for bytecode get installed. So I guess there's no  
>> support. What about the future ?
>
> Native dynlink used to work on Mac OS X < 10.5 (x86 only). The new  
> linker in 10.5 does not support linking shared libraries with non- 
> PIC code. It is still possible to use the old linker, called  
> ld_classic, but some libraries (like X11) does not work, so this has  
> been disabled in the configure script.

>
>
> The clean solution to make natdynlink work on recent Mac OS X systems
> (beside convincing Apple to support the old behavior of their linker  
> in their new implementation) is to change OCaml's x86 backend so  
> that it produces only PIC code (this has been done for the AMD64  
> port). I don't think there is currently any plan to work on that.

Ouch, this makes it almost a dead end for us. I can offer some time to  
help in this effort, working in the port, or providing feedback. The  
native dynlink and toplevel are, at least to me, the killer features  
in 3.11, but adding another hole for Mac OS X intel (in addition to  
not supporting x86_64) does not seem like the best choice for an  
increasingly popular architecture.

Again, thanks for the good work!

Andres

>
>
> Alain
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs


  reply	other threads:[~2008-10-15 15:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15 13:40 Damien Doligez
2008-10-15 14:19 ` [Caml-list] " Dario Teixeira
2008-10-15 14:55 ` Andres Varon
2008-10-15 15:04   ` Alain Frisch
2008-10-15 15:18     ` Andres Varon
2008-10-15 15:37       ` Alain Frisch
2008-10-15 15:44         ` Andres Varon
2008-10-15 15:46           ` Alain Frisch
2008-10-15 15:22     ` Daniel Bünzli
2008-10-15 15:27       ` Andres Varon
2008-10-15 17:41         ` Daniel Bünzli
2008-10-15 15:32       ` Alain Frisch
2008-10-15 15:56         ` Andres Varon [this message]
2008-10-15 16:03           ` Xavier Leroy
2008-10-15 19:39             ` Andres Varon
2008-10-15 15:29     ` Stefano Zacchiroli
2008-10-15 15:32 ` Jaap Boender
2008-10-15 18:07 ` Richard Jones
2008-10-16  8:20 ` David Allsopp
2008-10-17 15:53   ` Xavier Leroy
2008-10-16  9:58 ` David Allsopp
2008-10-16 13:08   ` Alain Frisch
2008-10-16 15:42     ` Re : " Adrien
2008-10-16 16:00       ` Alain Frisch
2008-10-16  9:58 ` David Allsopp
2008-10-16 16:22   ` Andres Varon
2008-10-16 16:31     ` Andres Varon
2008-10-16 16:50       ` Andres Varon

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=BE41BECE-FCC3-4D74-B982-BD1B6C89767E@gmail.com \
    --to=avaron@gmail.com \
    --cc=alain@frisch.fr \
    --cc=caml-list@inria.fr \
    /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).