caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alessandro Baretta <alex@baretta.com>
To: Ocaml <caml-list@inria.fr>,
	Christophe TROESTLER <debian00@tiscalinet.be>
Subject: Re: [Caml-list] Signal analysis
Date: Thu, 11 Jul 2002 23:11:57 +0200	[thread overview]
Message-ID: <3D2DF49D.8020200@baretta.com> (raw)
In-Reply-To: <20020711.194206.122060257.Christophe.Troestler@umh.ac.be>



Christophe TROESTLER wrote:
> On Thu, 11 Jul 2002, Alessandro Baretta <alex@baretta.com> wrote:
> 
>>Now, here I am building fft libraries and trying to get a grasp of
>>them. I have just typed "make" on my terminal, and I died horribly
>>because of a header it could not find.
> 
> 
> Do you mean the (r)fftw.h headers ?
> 

Yes. That's it. I had to specify a -I option in the Makefile 
to allow gcc to find the headers.

>>ocamlc tells me it type Complex.t is undefined. Now this seems to be
>>a real impediment: I have grep'ed my ocaml distro and have found no
>>reference to module Complex.
> 
> 
> Sorry for your inconvenience.  It's going to be said more clearly that
> the FFTW interface requires complex number hence the OCaml CVS
> distribution (which explains the strange paths in my Makefile) --
> until the next Ocaml release at least.  Don't worry, compiling Ocaml
> from CVS is easy, just look at http://camlcvs.inria.fr/ to download
> the files and follow the instructions. 

Compiling the CVS version is no real problem, but it tends 
to be slightly less stable than the distro, so I tend to 
prefer to stick with the distro for production work. Well, I 
guess I'll have to update my source directory and bootstrap it.

> I recommend running
> ./configure with an option like -prefix /usr/local/stow/ocaml-cvs/ if
> you want to keep it alongside Ocaml 3.04 (if you do not know "stow",
> have a look to it, it is interesting).

Reading your Makefile I had thought that stow was some 
strange name or acronym for a project you might be working 
on. Now you teach it is a package manager. Ok, I'll try it out.

> The compile directory of the FFTW interface is where the library is
> expected to stay.  I may try to add a "make install" if you need it.

Of course, I would appreciate greatly. But I do not wish to 
hassle you more than I have already. I am already idebted to 
you for writing the fftw package.

> Do not hesitate to report further difficulties with the installation
> -- I will try to write a quick INSTALL file from your remarks.

This is definitely worth the effort. But, it is such a pity 
that nothing can be done to rendere the installation 
painless until the new release is out.

Thank you very much.

Alex

-------------------
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


  parent reply	other threads:[~2002-07-11 21:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-03 19:19 Alessandro Baretta
2002-06-03 17:38 ` Eray Ozkural
2002-06-04 13:59   ` Christophe TROESTLER
     [not found]     ` <3D2CD456.4030808@baretta.com>
     [not found]       ` <20020711.194206.122060257.Christophe.Troestler@umh.ac.be>
2002-07-11 21:11         ` Alessandro Baretta [this message]
2002-06-03 18:24 ` Berke Durak
2002-06-03 18:40   ` Markus Mottl

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=3D2DF49D.8020200@baretta.com \
    --to=alex@baretta.com \
    --cc=caml-list@inria.fr \
    --cc=debian00@tiscalinet.be \
    /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).