You know, I had this same problem. Just run bootstrap twice. Not sure
what the problem is though.
-Ilia
On Fri, 2005-02-18 at 23:05 -0800, Matt Ettus wrote:
> >
> >
> > and here is where it loses it:
> >
> > checking boost/shared_ptr.hpp usability... yes
> > checking boost/shared_ptr.hpp presen
>
>
> and here is where it loses it:
>
> checking boost/shared_ptr.hpp usability... yes
> checking boost/shared_ptr.hpp presence... yes
> checking for boost/shared_ptr.hpp... yes
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: error: cannot find input file
After one of your earlier messages, I decided to clean out my CVSROOT
and start again from scratch to see if I could get by without copying
Makefile.in. I noticed that some things were not being built, so the
clean start.
No joy.
Here is the first warning in this
n4hy:/usr/local/GnuRadio/gr-build
On Friday 18 February 2005 10:40, Matt Ettus wrote:
I think the README in gnuradio-core is quite useful. This is where Matt & Eric
set the options to the fftw configure which is:
./configure --enable-single --enable-shared
I also want to again complement Matt and Eric on the quality of the code
On Fri, Feb 18, 2005 at 05:42:03AM -, Robert McGwier wrote:
> In a really good NBFM receiver, where you are attempting to use it
> for voice communications, and hand helds are involved (say), it is
> important to have threshold effect improvement. This will improve
> intelligibility on import
On Fri, Feb 18, 2005 at 05:49:26PM -0500, Bob Vincent wrote:
> Could you enumerate some of those possible rates here?
> I think we at least would find it useful to change rates.
Below are tables of acceptable Tx and Rx IF sample rates.
A couple of notes are in order. Matt's going to be making a
On Sat, Feb 19, 2005 at 12:28:07AM -, Robert McGwier wrote:
>
> Eric:
>
> Everything is built and running and the behavior
> you described is exactly what I saw in the files
> downloaded from the links on the Wiki. When I did
> bootstrap/for-all-dirs, it blew with "No makefile.in"
>
> I copi
Eric:
Everything is built and running and the behavior
you described is exactly what I saw in the files
downloaded from the links on the Wiki. When I did
bootstrap/for-all-dirs, it blew with "No makefile.in"
I copied the Makefile.in and all seemed to work.
Athlon Dual MP and Suse 9.2. It took
Hi,
I have installed ubuntu linux (a distribution of debian) and trying to
get the correct gcc version, but having trouble because the default gcc
is 3.3 and even though I have gcc 3.4, gcc seems to be linked with gcc
3.3. Do I have to remove gcc 3.3 (which requires removing so many
packages)?
Could you enumerate some of those possible rates here?
I think we at least would find it useful to change rates.
At 05:18 PM 2/18/2005, Eric Blossom wrote:
We could provide an interface
that allows the user to specify the
sampling rate that they want, and then check that against legal
values. At
On Fri, Feb 18, 2005 at 04:31:41PM -0500, Chuck Swiger wrote:
> At 12:53 PM 2/18/2005 -0800, you wrote:
> >On Thu, Feb 17, 2005 at 09:57:53PM -, Robert McGwier wrote:
> >> gr-build/gnuradio-core
> >>
> >> has no Makefile.in when I check out the code.
> >>
> >
> >
> >This sounds vaguely familiar
Hi, dear gentlemen
Some new USRP boards have arrived yesterday and I am planning to do some
experiments with it, such as FM transmission and reception. However, I
am still a beginner and hope I could use some existing codes without any
modification. Because it's still a bit difficult to me to unde
On Fri, Feb 18, 2005 at 05:20:03PM -0500, cswiger wrote:
> On Fri, 18 Feb 2005, Thomas Traber wrote:
>
> I played around with the sink.set_mux(0x98) - it looks like the
> 0x10 bit is the input and the 0x80 and 0x08 are two outputs. If you
> set DUC at 3900e3, and send it a signal at 30Khz you get
On Fri, Feb 18, 2005 at 06:45:32AM -0800, John Gilmore wrote:
> The gnuradio packages have funny ideas about what users will need
> to specify and how they need to specify them. These ideas probably
> came from implementing the guts of GNU Radio and the USRP, but they
> don't really make sense to
On Fri, 18 Feb 2005, Thomas Traber wrote:
> Chuck,
>
> > [...] looks more intensive than the
> > weaver method for now.
>
> I don't own a USRP (yet).
> Isn't it possible just to output the
> complex signal at [combine1] to the USRP
> and to IQ upconversion in the front end?
>
> >
Chuck,
> [...] looks more intensive than the
> weaver method for now.
I don't own a USRP (yet).
Isn't it possible just to output the
complex signal at [combine1] to the USRP
and to IQ upconversion in the front end?
> +---\ /+
> (f
On Fri, Feb 18, 2005 at 02:49:21AM -0800, John Gilmore wrote:
> I have a USRP that seems to be working, though I haven't been able to
> really make it do any work yet.
>
> I've created a wiki page, http://comsec.com/wiki?UsrpInstall .
> I'm trying to integrate the suggestions that have floated pa
On Fri, Feb 18, 2005 at 07:45:17AM -0500, Graham Stead wrote:
> Hi Everyone,
>
> I'm new to this and am just learning my way around.
>
> I tried building gnuradio-core 2.4 on 64-bit Fedora Core 3. When linking
> with libfftw3f (which I also downloaded, compiled and installed), I received
> the fo
On Thu, Feb 17, 2005 at 09:57:53PM -, Robert McGwier wrote:
> gr-build/gnuradio-core
>
> has no Makefile.in when I check out the code.
>
> so
>
> ./for-all-dirs ../buildit 2>&1 | tee make.log
>
> fails in the gnuradio-core build. I stole the
> Makefile.in from 2.4 and hope that it doesn't
and for a *really* pretty ssb fft plot - change the RF sampling
rate down from 2,000,000 to something just over 2X the IF, like
80Ksps, then connect up the fft window to hilbert_2, then use
the noise audio source. Then you can clearly see a 2700Hz band
of noise either above or below 30,000hz.
Here
Gang - Ok, here's a phasing SSB modulator that produces
the right output to gnuplot, that is, with an IF of 30Khz,
in upper-sideband, 300hz audio produces 30300hz and 3000hz
audio produces 33000hz, while in lower-sideband 300hz
audio produces 29700hz and 3000hz audio produces 27000hz.
You change s
What you describe sounds a little bit like what concepts like RDL
(Radio Description Language) are for.
I agree that there need to be multiple levels of accessibility:
1) one level for the application builder building a consumer friendly
front-end based on existing blocks of functionality (think
Quoting Graham Stead <[EMAIL PROTECTED]>
>
> The -fPIC suggestion seems odd; the option seems related to some older cpu
> architectures. Nevertheless, I tried to recompile libfftw3f and
> gnuradio-core with -fPIC, but received the same link error.
>
> Has anyone else done a gnuradio-core-2.4 64-bi
The gnuradio packages have funny ideas about what users will need
to specify and how they need to specify them. These ideas probably
came from implementing the guts of GNU Radio and the USRP, but they
don't really make sense to people who haven't implemented the guts.
For example, the programs we
Hi Everyone,
I'm new to this and am just learning my way around.
I tried building gnuradio-core 2.4 on 64-bit Fedora Core 3. When linking
with libfftw3f (which I also downloaded, compiled and installed), I received
the following error:
---
g++ -shared -nostdlib
/usr/lib/gcc/x86_64-redhat-linux/3
I have a USRP that seems to be working, though I haven't been able to
really make it do any work yet.
I've created a wiki page, http://comsec.com/wiki?UsrpInstall .
I'm trying to integrate the suggestions that have floated past on the
mailing list, for how to unpack and check out and use a USRP w
26 matches
Mail list logo
