From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Byron Hale <byron.hale@einfo.com>
Cc: caml-list@inria.fr
Subject: Re: Update: [Caml-list] GODI for ocaml release 3.07
Date: 04 Oct 2003 03:12:52 +0200 [thread overview]
Message-ID: <1065229972.1055.3.camel@ice.gerd-stolpmann.de> (raw)
In-Reply-To: <5.2.0.9.2.20031003173045.02f45970@einfo.com>
Am Sam, 2003-10-04 um 02.35 schrieb Byron Hale:
> GODI failed on a Red Hat 7.3 ix86 box at the bootstrap level
> with the following message:
>
> "===> Creating sample godi.conf/bin/cp: cannot create regular file
> `../godi/share/mk/sys.mk':
> No such file or directory"
Just an idea: The --prefix must be an absolute path, not a relative
path like ../godi
Gerd
> Thanks,
> Byron Hale
>
> At 11:49 PM 9/30/2003 +0200, Gerd wrote:
> >Am Die, 2003-09-30 um 15.42 schrieb Gerd Stolpmann:
> > > GODI has been tested on Linux (several flavours), FreeBSD 4.8, Solaris
> > > 8. It probably runs on more operating systems, but not on Windows (the
> > > Cygwin port has made some progress but is not yet done). There is still
> > > a problem for FreeBSD concerning threads, so it might be a good idea to
> > > wait until I have found the problem (any help appreciated).
> >
> >These problems have been solved, it runs now flawlessly on FreeBSD. The
> >change ensures that ocamlrun links against libc, and not libc_r.
> >
> >To get the changes: Simply bootstrap from the same tarball I posted the
> >afternoon. It updates itself automatically.
> >
> > > -- How to install GODI: --
> > >
> > > Download the bootstrap tarball from
> > > http://www.ocaml-programming.de/packages/godi-bootstrap-20030929.tar.gz
> > > and follow the instruction in the README file.
> >
> >Gerd
> >--
> >------------------------------------------------------------
> >Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany
> >gerd@gerd-stolpmann.de http://www.gerd-stolpmann.de
> >------------------------------------------------------------
> >
> >-------------------
> >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
>
>
> -------------------
> 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
--
------------------------------------------------------------
Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany
gerd@gerd-stolpmann.de http://www.gerd-stolpmann.de
------------------------------------------------------------
-------------------
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
prev parent reply other threads:[~2003-10-04 1:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 13:42 Gerd Stolpmann
2003-09-30 21:49 ` Update: " Gerd Stolpmann
2003-10-04 0:35 ` Byron Hale
2003-10-04 1:12 ` Gerd Stolpmann [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=1065229972.1055.3.camel@ice.gerd-stolpmann.de \
--to=info@gerd-stolpmann.de \
--cc=byron.hale@einfo.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