From: "Nicolás Ojeda Bär" <nicolas.ojeda.bar@lexifi.com>
To: "Christoph Höger" <christoph.hoeger@celeraone.com>
Cc: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Is there some builtin function that flushes buffers on shutdown?
Date: Fri, 3 Feb 2017 10:16:08 +0100 [thread overview]
Message-ID: <CADK7aFPfP2NwRrK0y9tyKsQr62juNLQHnY7d4Thfqu+e_=KGwA@mail.gmail.com> (raw)
In-Reply-To: <CAOazmvtC2=JAH0z11ong-nLLpTnGHWMTJ1JGsLAQSHYadiAQNg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
Hi Christoph,
I can't check now, but it sounds like you forgot to link $(ocamlc
-where)/std_exit.o into your executable.
Cheers!
Nicolas
On Fri, Feb 3, 2017 at 9:56 AM, Christoph Höger <
christoph.hoeger@celeraone.com> wrote:
> Dear all,
>
> I managed to manually link and run an object file generated by ocamlopt. A
> small part seems to be missing, however:
>
> ➜ llvmlink ocamlfind opt -package ANSITerminal -linkpkg -verbose
> -output-obj -o test.object.o test.ml
>
> ➜ llvmlink clang -I$(ocamlc -where) -lm wrapper.c test.object.o -o
> wrapper ~/.opam/4.04.0/lib/ocaml/libunix.a -ldl ~/.opam/4.04.0/lib/ocaml/libasmrun.a
> /home/choeger/.opam/4.04.0/lib/ANSITerminal/libANSITerminal_stubs.a
>
> These commands produce an executable output, but the screen remains empty.
> This changes, when I manually flush the stdout buffer in the code (I obtain
> the desired results then).
>
> Find attached the test sources. When I uncomment the Printf.printf in
> test.ml, everything seems to work fine. But when I compile the test using
> ocamlopt solely, this is not necessary. It seems some buffers do not get
> flushed here. Does anyone know, why?
>
> regards,
>
> Christoph
>
>
[-- Attachment #2: Type: text/html, Size: 1809 bytes --]
next prev parent reply other threads:[~2017-02-03 9:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 8:56 Christoph Höger
2017-02-03 9:16 ` Nicolás Ojeda Bär [this message]
2017-02-03 10:15 ` Christoph Höger
2017-02-03 10:52 ` Nicolás Ojeda Bär
2017-02-03 11:37 ` Nicolás Ojeda Bär
2017-02-09 12:53 ` Christoph Höger
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='CADK7aFPfP2NwRrK0y9tyKsQr62juNLQHnY7d4Thfqu+e_=KGwA@mail.gmail.com' \
--to=nicolas.ojeda.bar@lexifi.com \
--cc=caml-list@inria.fr \
--cc=christoph.hoeger@celeraone.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