From: Joao C. <jc...@fe...> - 2002-12-09 08:48:35
|
On Monday 09 December 2002 02:41, Alan W. Irwin wrote: > Joao, > > Your present difficulties with symlinks on OSF1 are due to my mistake w= hich > I have just fixed with a bootstrap.sh commit. Sorry! > > Once you update, then a ./bootstrap.sh in a *fresh checkout* > will make copies of automake-related files rather than symlinks. If yo= u > have an almost fresh checkout with just the old bootstrap.sh executed, = then > you must remove the symlinks before you execute (the new) bootstrap.sh > again. I'm using the -h option to tar; that's late here. Meanwhile, configure has detected how to make shared libs in osf -- that = were=20 not supported till AT!. But configure fails: ... checking for python... no checking if Python version >=3D 1.5... configure: error: too old configure should just set python to no instead of dying. ./configure --enable-dyndrivers --disable-python ... checking for python... no checking if Python version >=3D 1.5... configure: error: too old same error! Bye, Joao PS-if this message doesn't appears in the mailing list, could you please=20 forward it? Tomorrow I will see what is happening at the univ. mailler de= amon=20 (i.e. call the sysop -:) > > There should be no symlinks in the tarball you create once you use the = new > bootstrap.sh procedure. You can test for their presence in the tarball= by > looking for the string "->" in the table of contents that you get by ta= r > ztvf .... > > Good luck, Joao, and let me know how it goes with your further testing = of > OSF1. > > Alan > > email: ir...@be... > phone: 250-727-2902=09FAX: 250-721-7715 > snail-mail: > Dr. Alan W. Irwin > Department of Physics and Astronomy, > University of Victoria, P.O. Box 3055, > Victoria, British Columbia, Canada, V8W 3P6 > __________________________ > > Linux-powered astrophysics > __________________________ |