[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | John Skaller <skaller@u...> |
| Subject: | Re: [Caml-list] Caml on intel-OSX |
On Fri, 2005-06-10 at 08:35 +0200, Stefano Zacchiroli wrote: > On Fri, Jun 10, 2005 at 08:51:40AM +1000, John Skaller wrote: > > (and it's a real pain for the Debian packaging .. since > > the system autodetects the native code compiler and tries > > to use it even though it doesn't work: there is no > > opportunity to intervene manually in Debian autobuilds) > > This is not true. > > Debian autobuilds simply invoke a make file (debian/rules) written by > the package, which usually invokes upstream Makefile. Since you are the > packager, if you really want the autobuilds not to build native code, > then you can change either debian/rules or Makefile so that native code > compilation is not enforced. I could include a special piece of logic in the debian rules, which checks for AMD64 and disables the native code compiler in that case... .. or I could change the config script (since I'm also the upstream author). But that isn't *manual* intervention. BTW: the packages are available in the directory http://felix.sf.net/debian There is a dependence on ocaml, but none on the native code package.. if you happen to have it installed the native code compiler will be used to build the binary package, otherwise you'll get bytecode. -- John Skaller, skaller at users.sf.net PO Box 401 Glebe, NSW 2037, Australia Ph:61-2-96600850 Download Felix here: http://felix.sf.net