 |
 |
Hello, Andreas The reason for this is that the distribution tarballs are currently just archives of the files in CVS and not bootstrapped tarballs, since many people still use configure.classic. They contain the input files from which autotools create configure and all the dependent scripts (bootstrap.sh), but they require a reasonably up to date version of the autotools. Bootstrapping should only be necessary for the maintainer producing the tarballs or for developers changing parts of the makefile structure. If "make dist" or "make distcheck" is executed in a bootstrapped autotools project, a portable tarball is produced, that contains all the autotools generated helper files. Once we really switch to the autotools build, the downloadable tarball should be generated like this. I have here a page where I try to stay up to date with the bootstrapped versions of the tarballs: http://project-arda-dev.web.cern.ch/project-arda-dev/xrootd/tarballs/ (look towards the bottom of the page for xrootd-20060414-1334-r1.tar.gz) Actually I would be in favor of deleting "configure" from the CVS because it tends to confuse people. It anyhow cannot be used without the additional bootstrapping. Cheers, Derek On Tuesday 18 April 2006 19.33, Andreas Petzold wrote: > Hi Pete, > > On Tuesday 18 April 2006 19:21, Peter Elmer wrote: > > Hi Andreas, > > > > On Tue, Apr 18, 2006 at 07:07:13PM +0200, Andreas Petzold wrote: > > > after un-tarring the source, ./configure dies with the following error > > > when used OOTB: > > > > > > $ ./configure > > > configure: error: cannot find install-sh or install.sh in . ./.. > > > ./../.. > > > > > > I really don't know, why it expects install.sh to be found in one of > > > these directories. But anyway, after running > > > > > > libtoolize --copy --force > > > aclocal > > > automake -acf > > > autoconf > > > > > > (maybe not all the steps are necessary) > > > > > > ./configure runs successfully. Is this the intended behavior? > > > > Derek can probably respond as to the current state of the autotools > > support. We have still been using "./configure.classic" for most things, > > but are planning to move to default use of the autotools stuff after > > the production build goes out (probably the one I built today, although > > not yet announced). > > ah, I see. > > > BTW, is this for FZK use for BaBar? I thought you guys were using the > > standard rpms or binary tarballs. Do you normally rebuild it yourself? > > This is not for fzk. I need the libs, headers, and binaries for building > some private stuff on fc4/fc5/suse10.0. > > Cheers, > > Andreas > > > Pete > > > > ------------------------------------------------------------------------- > > Peter Elmer E-mail: [log in to unmask] Phone: +41 (22) 767-4644 > > Address: CERN Division PPE, Bat. 32 2C-14, CH-1211 Geneva 23, Switzerland > > -------------------------------------------------------------------------