Good deal!
Still messing with hardware, bought the stereo audio 44.1k board (hat)
and soldered that together. PS the header kits are for Teensy 3.6, so
luckily I had a bunch of headers from old projects.
My hacked 700C vocoder is failing miserably on Ubuntu. Guess I'll have
to go line by line. Si
Hi Steve and all,
At $25 ea. I've acquired two Teensy 4 boards for my Codec 2 project.
How's the code going?
Alan VK2ZIW
On Sun, 16 Feb 2020 13:07:48 -0600, Steve wrote
> > ...adding the static keyword
> > on to functions that are only called from within a single file.
>
> That is my own codin
> ...adding the static keyword
> on to functions that are only called from within a single file.
That is my own coding style. In early MS-DOS days, this saved time and
memory during linking, Smaller symbol tables, etc...
Plus, if you list all the static functions at the top of the file as
prototy
On 2/16/20, Steve wrote:
> I added it to the CMakeLists.txt file:
>
> # Set default C flags.
> set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wall -Wno-strict-overflow
> -fno-common")
To help detect some related problems that can lead to dead code
and missed optimization, -Wstrict-prototypes and -Wmissing-
Only one error found in abandoned code. Make the .h file an extern and add
the definition to the C file.
$ diff ~/github/codec2/stm32/inc/si53xx.h si53xx.h
287c287
< T_Si5351_data Si5351_Config;
---
> extern T_Si5351_data Si5351_Config;
$ diff ~/github/codec2/stm32/src/si53xx.c si53xx.c
44a45
Oh OK, I see now the error is with ARM, so I'm looking at the STM32.
First error is with si5351_ut.elf.
arm-none-eabi/bin/ld:
CMakeFiles/si5351_ut.dir/src/si53xx.c.obj:/home/ssampson/codec2/stm32/inc/si53xx.h:287:
multiple definition of `Si5351_Config'
I wonder if all that abandoned SM2000 code
I added it to the CMakeLists.txt file:
# Set default C flags.
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wall -Wno-strict-overflow -fno-common")
Compiled without errors or warnings on GCC 7.4.0
No change.
On Sun, Feb 16, 2020 at 10:48 AM Albert Cahalan wrote:
> > Maybe just add -fcommon to the Ma
> Maybe just add -fcommon to the Makefile
No, add -fno-common to the Makefile, ensuring that people with older
versions will get the same errors.
It's a saner and safer default, and is more compatible with Win32.
___
Freetel-codec2 mailing list
Freete
Maybe just add -fcommon to the Makefile
On Sun, Feb 16, 2020 at 7:41 AM Richard Shaw wrote:
>
> Guys,
>
> As usual new releases of GCC are more pedantic about being compliant to the
> standards that previous releases. With GCC 10 codec2 no longer compile due to
> multiple definitions of functio
Guys,
As usual new releases of GCC are more pedantic about being compliant to the
standards that previous releases. With GCC 10 codec2 no longer compile due
to multiple definitions of functions.
https://bugzilla.redhat.com/show_bug.cgi?id=1799237
The guide to porting can be found here:
https://
10 matches
Mail list logo
