Re: How to build libtool from git sources properly?
Mathieu Lirzin <[email protected]>
| Newsgroups | gmane.comp.gnu.libtool.general |
|---|---|
| Message-ID | <[email protected]> |
Hi, Bob Friesenhahn <[email protected]> writes: > On Wed, 18 May 2016, Igor Zhbanov wrote: >>> >>> run `./bootstrap` >>> -mike >> >> It doesn't work on a PC without git or without network connection >> because it needs to clone gnulib (although there is no gnulib folder >> in libtool-2.4.6.tar.gz. But this is probably another story. > > This is very unfortunate. Why? Development repositories are not meant for end users. Having a tarball requiring only a subset of the dependencies necessary or convenient to the developers seems nice. > I am not sure if it would work if you cloned gnulib on another > computer and copied the gnulib folder into place since it may still > make subsequent git accesses. > > The bootstrap requirements make it difficult to support or test on > targets which can not run git or don't have network access. To test a unreleased version of a package that uses the GNU build system on a restricted system, the usual method would be to bootstrap a tarball with ‘make dist’ from a development machine with Git, network access, ... and then install the produced tarball on the targeted machine. -- Mathieu Lirzin _______________________________________________ https://lists.gnu.org/mailman/listinfo/libtool