caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Kip Macy" <kip.macy@gmail.com>
To: "Shawn W" <shawnw@speakeasy.org>
Cc: Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] disconcerting asm warnings when building for freebsd-sparc64
Date: Sat, 7 Oct 2006 16:50:44 -0700	[thread overview]
Message-ID: <b1fa29170610071650r53a19b71we2f3349f47548b1@mail.gmail.com> (raw)
In-Reply-To: <45283D60.6000100@speakeasy.org>

ok, thanks - sorry for missing it

On 10/7/06, Shawn W <shawnw@speakeasy.org> wrote:
> Kip Macy wrote:
> > Is this a bug in ocaml? Or have I mis-configured gas?
> >
> > Thanks.
>
>
> Native code generation doesn't work for sparc64. There was a fairly
> recent thread about this, with a link to a patch that seems to fix the
> problems.
>
>


      reply	other threads:[~2006-10-07 23:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-07 23:35 Kip Macy
2006-10-07 23:50 ` [Caml-list] " Shawn W
2006-10-07 23:50   ` Kip Macy [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=b1fa29170610071650r53a19b71we2f3349f47548b1@mail.gmail.com \
    --to=kip.macy@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=shawnw@speakeasy.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).