Very odd
i would run autogen.sh (programers pre-distribution script) if thier is one and see if it worked, have you tried
$cat autogen.sh #!/bin/sh
set -x aclocal -I config autoheader libtoolize --automake touch AUTHORS ChangeLog automake --add-missing --copy autoconf $
Regards
Owen Synge
On Mon, 5 Sep 2005 14:01:07 +0100 Chris Green chris@areti.co.uk wrote:
On Mon, Sep 05, 2005 at 01:50:55PM +0100, Brett Parker wrote:
Chris Green chris@areti.co.uk wrote:
I'm trying to configure a utility using autoconf, when I run ./configure I get all the usual checking sort of stuff, then at the end:-
checking for XShapeCombineMask in -lXext... no checking for jpeg_destroy_compress in -ljpeg... no not updating unwritable cache ./config.cache creating ./config.status sed: can't read confdefs.h: No such file or directory creating autoconf/Makefile.defines sed: can't read ./autoconf/Makefile.defines.in: No such file or directory creating autoconf/Makefile.common sed: can't read ./autoconf/Makefile.common.in: No such file or directory creating autoconf/Makefile.common.lib sed: can't read ./autoconf/Makefile.common.lib.in: No such file or directory creating Makefile sed: can't read ./Makefile.in: No such file or directory creating config.h cat: ./autoconf/config.h.in: No such file or directory config.h is unchanged... but all those errors are nonsense, there is a writable ./config.cache (created earlier by autoconf) and the autoconf directory does exist and has those files in it.
What am I missing?
Only thing I can think of, off the top of my not-yet-caffienated-enough head is that you may have some permissions problems, are you running configure as the same user you ran autoconf as?
also: not updating unwritable cache ./config.cache
would suggest to me that you can't make files in that directory, which leads to it being a permissions problem...
In the directory where I'm running ./configure I can quite happile write to ./config.cache myself.
However there's something fundamentally wrong, I've just noticed that ./configure is creating files and directories in the *parent* directory for some wierd reason. I've just cleared out config.h config.status Makefile and an autoconf directory in the directory above where I'm running ./configure, then I ran it again and it's recreated them 'above' again!
-- Chris Green (chris@areti.co.uk)
"Never ascribe to malice that which can be explained by incompetence."
main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!