Ltmain.sh in 3.3.0 tarball?

Hi,

I’m wondering if ltmain.sh really is supposed to be distributed in the
release tarballs… Commit 81133f7b
(gnuradio.git - GNU Radio)
seems to indicate otherwise. I stumbled on this because the
combination of very old system libtool (1.5.22) and tarball ltmain.sh
(2.2.6b) causes build errors at the beginning of “make”.

Catalin

On Fri, Jun 11, 2010 at 02:25:03PM -0400, Catalin P. wrote:

Hi,

I’m wondering if ltmain.sh really is supposed to be distributed in the
release tarballs… Commit 81133f7b
(gnuradio.git - GNU Radio)
seems to indicate otherwise.

That was about whether it should be in the repo, not the generated
tarballs.

I stumbled on this because the
combination of very old system libtool (1.5.22) and tarball ltmain.sh
(2.2.6b) causes build errors at the beginning of “make”.

Catalin

Yes, ltmain.sh should be in the tarballs.

If you unpack the tarball (and don’t modify anything), run configure,
then
make, it should work.

If you modify anything you’ll need a consistent set of autotools.

Eric

On Fri, Jun 11, 2010 at 3:36 PM, Eric B. [email protected] wrote:

If you unpack the tarball (and don’t modify anything), run configure, then
make, it should work.
Yes, you’re right. The problem was that I was also running autoreconf,
which I guess creates a mixed-version libtool environment in the tree.

If you modify anything you’ll need a consistent set of autotools.
The reason for all this is I need to make changes in a *.am file. Is
there a way to un-bootstrap a tarball? Just doing ./bootstrap causes
the same mismatched libtool version problem. The only solution I’ve
found so far is to remove ltmain.sh from the tree, then bootstrap,
which feels kind of hackish.

Thanks,
Catalin

On Fri, Jun 11, 2010 at 04:28:19PM -0400, Catalin P. wrote:

found so far is to remove ltmain.sh from the tree, then bootstrap,
which feels kind of hackish.

That will work, or you can use git to checkout directly from the repo.

Using git also allows you to more easily manage your local changes as
the
code in the repo moves forward.

Eric