Hi Gerard - so the problems you're having are on W10 but not Debian?
If you're having trouble with Debian, please post the contents of
/etc/debian_version
-- Cinaed
On 11/26/21 23:57, Gerard F6EEQ wrote:
Hi all,
I have two implementations of GNU.
One is under W10 on my main PC.
The second
Hi Gerard,
as long as you have the same version on both devices, you should not
have such differences. My guess is, that Debian did not automatically
install some of the dependencies. Do other Qt elements work? Maybe there
are some Qt libraries missing, but I am not a Debian expert. There are
Hi Gerard,
what versions are you using? My guess is that you are using a fairly old
version in Debian, as Debian is a distribution made for stability and is
therefore usually a bit behind.
What warning do you get? Often warnings are just warnings and you can
ignore them ;)
Best regards,
Fabia
Hi all,
I have two implementations of GNU.
One is under W10 on my main PC.
The second one is under LINUX (Debian) on a portable PC.
I do not have the same rendering on both machines.
For instance, when I look at he "oscilloscope" (QT Gui Time Sink) I have
a capability to expand the trace on De
I'm pretty sure this doesn't happen if you start with a clean build dir.
If you run cmake with -DCMAKE_INSTALL_PREFIX, all paths will be correct.
Only if you re-run cmake with a new -DCMAKE_INSTALL_PREFIX, it will only
update the install path, not the config path. If you're doing that, you
must
On Wed, May 29, 2013 at 06:02:54AM -0700, Johnathan Corgan wrote:
> Ok, somehow the CMake configuration is messing up the calculation of
> sysconfdir. The line at:
>
> http://gnuradio.org/cgit/gnuradio.git/tree/CMakeLists.txt#n128
>
> ...should be appending 'etc' to the install prefix, which as
On Wed, May 29, 2013 at 5:49 AM, Volker Schroer wrote:
>> $ gnuradio-config-info --prefix
>> $ gnuradio-config-info --sysconfdir
>>
>>
> schroer@tux64 ~ $ gnuradio-config-info --prefix
> /usr/local/gnuradio-3.7
> schroer@tux64 ~ $ gnuradio-config-info --sysconfdir
> /usr/local/etc
>
> and
>
> sc
$ gnuradio-config-info --prefix
$ gnuradio-config-info --sysconfdir
schroer@tux64 ~ $ gnuradio-config-info --prefix
/usr/local/gnuradio-3.7
schroer@tux64 ~ $ gnuradio-config-info --sysconfdir
/usr/local/etc
and
schroer@tux64 ~ $ gnuradio-config-info --prefix
/usr/local/gnuradio-3.6
schroer
link
> /usr/local/gnuradio to the directory just required.
>
> The installation works find but the second installation overwrites the
> config files of the first installation as both config files go to
> /usr/local/etc instead of /etc.
>
Can you run these two commands, each w
find but the second installation overwrites the
config files of the first installation as both config files go to
/usr/local/etc instead of /etc.
Is this a bug or a feature?
-- Volker
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https
All audio module source and sink constructors are now homologous.
They accept:
audio.sink(sample_rate, device_name, ok_to_block),
audio.source(sample_rate, device_name, ok_to_block),
where device_name and ok_to_block are optional and default to "" and
True respectively. ok_to_block should b
Eric Blossom wrote:
On Fri, Mar 31, 2006 at 05:30:04PM -0800, Thomas Schmid wrote:
Hi Eric,
I tried the new scripts today. Updating of my old distribution with
cvs up didn't work. It had some problems with the parallel to serial
--snip --
Thomas
Thanks for the feedback.
The p
On Fri, Mar 31, 2006 at 05:30:04PM -0800, Thomas Schmid wrote:
> Hi Eric,
>
> I tried the new scripts today. Updating of my old distribution with
> cvs up didn't work. It had some problems with the parallel to serial
> scripts which were removed and didn't want to compile. Thus, I did a
> fresh ch
Hi Eric,
I tried the new scripts today. Updating of my old distribution with
cvs up didn't work. It had some problems with the parallel to serial
scripts which were removed and didn't want to compile. Thus, I did a
fresh checkout of everything and the build worked flawlessly. This was
on my debian
Hi Folks,
There have been a lot of updates in CVS and a few in svn over the last
few days. Yes, I know that that having some of the stuff in CVS and
some in subversion is a pain. Consider it an experiment that will
converge to a single solution as soon as we think it's safe.
Part 1: working wit
15 matches
Mail list logo