On Sun, Jul 19, 2009 at 10:44:21PM +0100, Dr. David Kirkby wrote:
> On closer inspection, I see this error:
> 
> make[1]: Entering directory 
> `/export/home/drkirkby/sage/sage-4.1/spkg/build/singular-3-1-0-2-20090620/src/kernel'
> ./mkinstalldirs /export/home/drkirkby/sage/sage-4.1/local/include/singular
> for file in *.h; do ../.././install-sh -c $file 

Strangely, this actually seems to be a bug in the config.status script
generated by configure, in turn generated by autoconf.

If I understand things correctly, this is what happens:
when src/Singular/config.status outputs ../kernel/Makefile, it
interprets the two slashes in that path as the output file being two
subdirectories down from Makefile, and so adjusts (the correct)
'./install.sh' (i.e., actually src/Singular/install-sh) to (the broken)
'../.././install.sh' .

The reason this doesn't show up on my system (and presumably other
systems) is that /usr/bin/install (with an absolute path) is found and used
instead of ./install.sh.

Not sure how to work around or fix this... I tried using the latest
autoconf 2.63 to regenerate the configure script, but that doesn't fix it.


-Willem Jan

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to