Christopher Cordell wrote:
> Hello,
>
> I am not certain that I am emailing the proper address but this is
> the address I saw on the development page.
>
> I am using Solaris 9 and attempting to build the latest CVS version
> 4.1 for a scientist who needs to use a feature only under 4.1 apparently.
>
> I tried the sample unix makefile with no success so then I grabbed
> the required versions of autoconf, m4, etc. and tried to follow the
> directions on the page.
>
> The process hangs/waits with ./prepare:
>
> opik{root}76# ./prepare
> rm -f Makefile.am Makefile.amt
> sed -n '1,/^##m4-files-begin/p' Makefile.am.in > Makefile.amt
> echo EXTRA_DIST = README Makefile.am.in buildvms.com config.* \
> djconfig.sh make_vms.com term_pc.h makefile.* | fmt | \
> (tr '\012' @; echo) |sed 's/@$/%/;s/@/ \\@/g' |tr @% '\012 ' >>
> Makefile.amt
> sed -n '/^##m4-files-end/,$p' >> Makefile.amt
>
>
> What tips do you have for building (other than on the dev. page).
You might have to do a bit more investigation on that one. The string editor is
a strange command to hang on. You are running from root, so it probably is not
a problem with file access privilege. Perhaps it is the command after the above
"sed" command.
It appears to have stopped early on in the "config" subdirectory. Check to see
what "Makefile.amt" looks like (or the non-temporary "Makefile.am" if it happens
to exist). That is, the command inside "prepare" is
&& (cd config && make -f Makefile.am.in Makefile.am ) \
So, looking at "config/Makefile.am.in", the command following your last echoed
command is
sed -n '/^##m4-files-end/,$$p' $< >> $@t
chmod a-w $@t
Could Solaris be hanging on a "chmod" command?
Dan
|
