From: John Skaller <skaller@users.sourceforge.net>
To: Stefano Zacchiroli <zack@debian.org>
Cc: Inria Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Caml on intel-OSX
Date: Fri, 10 Jun 2005 19:07:26 +1000 [thread overview]
Message-ID: <1118394446.8693.171.camel@rosella.wigram> (raw)
In-Reply-To: <20050610063505.GB30637@fistandantilus.takhisis.org>
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
next prev parent reply other threads:[~2005-06-10 9:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 5:33 John Skaller
2005-06-09 8:23 ` [Caml-list] " Agustín Valverde
2005-06-09 14:00 ` james woodyatt
2005-06-09 15:27 ` John Skaller
2005-06-09 16:20 ` padiolea
2005-06-09 22:51 ` John Skaller
2005-06-10 0:02 ` Jonathan Bryant
2005-06-10 2:55 ` John Skaller
2005-06-10 7:10 ` Florian Hars
2005-06-10 0:41 ` Jacques Garrigue
2005-06-10 1:57 ` John Skaller
2005-06-14 0:28 ` Sven Luther
2005-06-10 6:35 ` Stefano Zacchiroli
2005-06-10 9:07 ` John Skaller [this message]
2005-06-10 23:39 ` Jon Harrop
2005-06-11 18:39 ` John Skaller
2005-06-11 19:03 ` Jon Harrop
2005-06-12 6:58 ` John Skaller
2005-06-13 19:19 ` [Caml-list] AMD64 ocamlopt bug Xavier Leroy
2005-06-13 19:32 ` John Skaller
2005-06-13 20:18 ` Damien Doligez
2005-06-13 20:27 ` John Skaller
2005-06-13 21:01 ` Anil Madhavapeddy
2005-06-09 23:44 ` [Caml-list] Caml on intel-OSX Jonathan Bryant
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=1118394446.8693.171.camel@rosella.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=zack@debian.org \
/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).