Willem Jan Palenstijn wrote: > On Sun, Jul 19, 2009 at 11:34:26PM +0100, Dr. David Kirkby wrote: >> Willem Jan Palenstijn wrote: >>> 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 >> Interesting. Note however that the missing file is install-sh and not >> install.sh > > Sorry, that was a typo. > > >> The simplest, though perhaps not the cleanest fix is to simply copy >> install-sh to the top level directory where SPKG.txt and friends reside. > > A different hack might be to patch src/kernel/Makefile.in (again...) and > change the line 'INSTALL = @INSTALL@' to 'INSTALL=./install.sh'. > That'll be slower on systems with an install binary, but should be > negligable compared to the total build time. > > >> I would be surprised if /usr/bin/install was found where there was an >> absolute path to a file, but clearly something like that must be >> happening, otherwise it would be broken on every system. > > It isn't hardcoded; it looks for install in $PATH. > > > In the meantime, I also asked for advice on the autoconf mailing list, > to see if this is a bug in autoconf or a bug in Singular's build system. > That's more for a long-term solution, though. > > > -Willem Jan
Thank you. I assume $PATH would include $SAGE_HOME/local/bin, so perhaps yet another way is to put install-sh there. But to solve an immediate need, I done it the easiest way I could and created a patch to singular, which just adds install-sh. It will allow me to make some progress on Solaris, which I disparately need to do! Sometimes I think it is one step forward and two back. If you get a response from the autoconf people and can provide a better solution, that would be good. But for my purposes, the above approach works. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
