The tarball is generated when you run "make dist" from a bootstrapped
build tree. This tarball contains the files generated from doing the
bootstrap (all the makefile.ins, configure, so on...)
You could think of it this way: a bootstrapped build does not have a way
of comprehending its pre-boo
Thanks for the question and response as this also helps me with the
problems I was having. Can you explain this also in the context of
the instructions that say not to run ./bootstrap if building from the
tarball? Indeed, I find that if I run ./bootstrap after unpacking
the tarball it has a t
On Sat, Jan 09, 2010 at 11:02:47AM -0600, John Orlando wrote:
> On Sat, Jan 9, 2010 at 9:58 AM, Eric Blossom wrote:
>
> >
> > ./bootstrap && ./configure
> >
> > Should work
> >
> Ahh...I didn't think bootstrapping first was necessary if re-building (I had
> assumed that configure took care of agg
On Sat, Jan 9, 2010 at 9:58 AM, Eric Blossom wrote:
> On Sat, Jan 09, 2010 at 08:16:01AM -0600, John Orlando wrote:
> > Hi all,
> > I'm working with GNUradio 3.2.2 on an Ubuntu 8.04 x86 box. I'm in the
> > process of making some modifications to the source that builds libusrp,
> and
> > part of
On Sat, Jan 09, 2010 at 08:16:01AM -0600, John Orlando wrote:
> Hi all,
> I'm working with GNUradio 3.2.2 on an Ubuntu 8.04 x86 box. I'm in the
> process of making some modifications to the source that builds libusrp, and
> part of these modifications includes adding some new files under
> usrp/ho
Hi all,
I'm working with GNUradio 3.2.2 on an Ubuntu 8.04 x86 box. I'm in the
process of making some modifications to the source that builds libusrp, and
part of these modifications includes adding some new files under
usrp/host/lib/legacy, where all the RF daughterboard code lives. This
seemed e
