From: "climb" <onlyclimb@163.com>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: [Caml-list] Ocaml Makefile on FreeBSD
Date: Fri, 29 Nov 2002 9:31:26 +0800 [thread overview]
Message-ID: <20021129013116.496C01C462A19@sm205.163.com> (raw)
I am forced to used FreeBSD these days.
So, i copy the my caml project dir into FreeBSD.
But i can not use Ocaml Makefile which can use in RedHat8
when i type make ,
it says at XXX line , Need an operator. Error expanding embeded variable
how can i solve these problem ?
Best regards
Yours
climb
onlyclimb@163.com
2002-11-29
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next reply other threads:[~2002-11-29 3:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-29 1:31 climb [this message]
2002-11-29 1:48 climb
2002-11-29 2:48 ` Ceri Storey
2002-11-29 6:47 ` Johan Baltié
2002-11-29 8:51 ` Richard Nyberg
2002-11-29 14:46 ` Nicolas Cannasse
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=20021129013116.496C01C462A19@sm205.163.com \
--to=onlyclimb@163.com \
--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).