Hi, Yeo Eng Hee
I don't know the details you want to handle. However, a batch script
which calls "./configure" itself and analyze the output may help you to
deal with your problem.
Best wishes
Zheng LI
在 2007-07-26四的 10:19 +0800，Yeo Eng Hee写道：
> On Mon, 23 Jul 2007, Ulrich Dobramysl wrote:
> >> I am having difficulty using the configure script to build meep. I
> have
> >> built and installed all the dependent packages, and at the final step
> of
> >> putting it all together in meep, but hte configure script cannot seem
> to
> >> find the libctl location, even though I used the --with-libctl=<dir>
> >> flag. The output of the configure script is below.
> >>
> >> I would be grateful if anyone can help tell me where I went wrong.
> >>
> >> Thanks in advance.
> >
> > It seems you do not have the libctl.a in /usr/lib or some other
> standard
> > library path. With the config option --with-libctl you specify the
> > location of the scheme files used by libctl whereas you need to have
> the
> > library in a known lib path. Try to specify
> > LIBDIR=${LIBDIR}:/directory/containing/libctl.a/ on your configure
> > commandline.
>
> This is not quite right. You also need to tell it where to find the
> header files, and LIBDIR is not the documented way to tell it about
> library directories in any case.
>
> In general, suppose you have installed stuff in /my/dir, i.e. you have
> libraries in /my/dir/lib and header files in /my/dir/include, etcetera.
> (Here, I'm assuming you actually ran 'make install' like you are
> supposed
> to.) Then, you always tell the configure scrip where to find libraries
> by:
>
> ./configure CPPFLAGS=-I/my/dir/include LDFLAGS=-I/my/dir/lib
>
> This is not specific to MPB; it is true for *all* software that uses
> configure scripts and depends on libraries you installed in nonstandard
> locations.
>
> However, libctl needs some additional information, because it has some
> additional files that it installs in /my/dir/share/libctl ...you tell
> it
> where to find these with --with-libctl-dir=/my/dir/share/libctl
>
> Steven
>
> ===========================
>
> Hi all,
>
> I understand the need to put in the header and library using the
> CPPFLAGS and LDFLAGS parameter, but if all dependencies need a little
> something in these parameters, then the setting of these CPPFLAGS and
> LDFLAGS become complicated. I expect that the configure script should
> be able to handle this. Since the directory hierachy of libctl is quite
> fixed, why not let the configure script figure out everything by just
> specifying the top directory of libctl?
>
> Anyway, I managed to build by installing libctl in the standard
> /usr/local/lib directory. However, this is less than ideal in my case,
> as I have more than 60 compute nodes, and I have to install on each one
> (normally, I would just install on a shared directory via NFS).
>
> Eng Hee.
>
> _______________________________________________
> meep-discuss mailing list
> [email protected]
> http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss
>
_______________________________________________
meep-discuss mailing list
[email protected]
http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/meep-discuss
