Re: [Discuss-gnuradio] Mac OS X gnuradio take 2

[H. R. Myler (@ pbLULU)]

Admittedly, no. Those tools are present, but much later versions:

autoconf (GNU Autoconf) 2.52

automake (GNU automake) 1.6.1

libtool won't tell me what version it is, but file says: libtool: 
Mach-O executable ppc

So I guess later is not better. Will backtracking to those specific 
versions squirrel something else up? I suppose I could put the 
specific versions in a side directory and put it first in the path.

At 12:14 PM -0800 4/2/03, Eric Blossom wrote:
> On Wed, Apr 02, 2003 at 08:56:44AM -0600, H. R. Myler (@ pbLULU) wrote:
> >  Dear unix cones, I may be getting too old for this (ahhhh...to be at
> >  the level I was back in the grad school days...<sigh>) or too lazy.
> >  Anyway, I got this far:
> >
> >  [pbLULU:/developer/gnuradio] hmyler% make
> >  make  all-recursive
> >  Making all in config
> >  make[2]: Nothing to be done for `all'.
> >  Making all in cppunit
> >  Making all in config
> >  make[3]: Nothing to be done for `all'.
> >  Making all in src
> >  Making all in cppunit
> >  source='TestAssert.cpp' object='TestAssert.lo' libtool=yes \
> >  depfile='.deps/TestAssert.Plo' tmpdepfile='.deps/TestAssert.TPlo' \
> >  depmode=gcc3 /bin/sh ../../config/depcomp \
> >  /bin/sh ../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I.
> >  -I../../include -I./../../include    -O2 -c -o TestAssert.lo `test -f
> >  'TestAssert.cpp' || echo './'`TestAssert.cpp
> >  ../../libtool: ../../libtool: No such file or directory
> >  make[4]: *** [TestAssert.lo] Error 127
> >  make[3]: *** [all-recursive] Error 1
> >  make[2]: *** [all-recursive] Error 1
> >  make[1]: *** [all-recursive] Error 1
> >  make: *** [all] Error 2
>
> Do you have the tools and the versions called for in the README?
> Are they in your path?
>
>        autoconf 2.13
>        automake 1.4-p6
>        libtool 1.4.2
>
> Eric