|
From: Rafael L. <rla...@us...> - 2003-12-20 18:16:59
|
[Cc:ing to plplot-general]
* Alan W. Irwin <ir...@be...> [2003-12-20 08:30]:
> Rob Managan sailed through all the configuration part for Mac OS X without
> troubles in September. Have we changed something relevant in our
> configuration since?
No I do not remember doing anything that would break building on MacOS X.
However, it may be appropriate to ask Rob Managan if he can build the
current cvs release of PLplot.
> I would appreciate you taking over here with Michel. I don't even know the
> relevant questions to ask.
>
> Alan
> ---------- Forwarded message ----------
> Date: Sat, 20 Dec 2003 10:29:11 +0100 (CET)
> From: Michel Peyrard <Mic...@en...>
> To: Alan W. Irwin <ai...@us...>
> Subject: --disable-dyndrivers won't configure
>
>
> Dear Alan,
>
> I tried to use ./configure --disable-dyndrives, but the command fails at
> the configuration level (see the details below).
>
> Since it seemd to come from the cpp preprocessor which is not in /lib/cpp
> but in /usr/bin/cpp on Mac OS X, I tried to define the environment
> variable CPP='/usr/bin/cpp'
> With this variable the ./configure --disable-dyndrivers copmmand goes much
> further, but finally fails with another error.
>
> In you preceding message you said that no developper has access to Mac OS
> X. I do not have expertise and time to be a developper, but, if you think
> that it is useful, I can be a "tester" of the new releases.
>
> [...]
>
> With --disbale-dyndrivers, and the environment variable CPP='/usr/bin/cpp'
> -------------------------------------------------------------------------
> ... many successful steps ...
>
> checking for vfork.h... no
> checking for fork... yes
> checking for vfork... yes
> checking for working fork... yes
> checking for working vfork... (cached) yes
> checking for popen... yes
> checking for usleep... yes
> checking for isinf... yes
> checking for finite... yes
> checking for isnan... yes
> checking for dynamic drivers...
> checking for perl... found
> configure: error: conditional "AMDEP" was never defined.
> Usually this means the macro was only invoked conditionally.
This is a very strange bug. It looks like the /bin/sh program in your
system is failing with configure. Could you please run the following line
at your shell and send the result to us (it should be either "t" or "f").
echo `a=1;b=;if test -z "$a"&& test -z "$b";then echo t;else echo f; fi'|/bin/sh
Also, looking at the resulting config.log may also help. Could you please
send it here?
--
Rafael
|