-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LD: error #4
Comments
have you installed https://github.com/pothosware/SoapySDR ? |
yes I have installed |
i can't reproduce this error on my macbook air m1. maybe try to compile master branch of soapysdr library(instead of 0.8.1 version from package managers)? |
now I have uninstall soapysdr over brew and than I compile and install SoapySDR from Source again now I have following ###################################################### Soapy SDR -- the SDR abstraction library###################################################### Lib Version: v0.8.1-gbb33b2d2
Now the next question:how can I transfer the SDDC_FX3.img to RX888? |
you can use this to upload the image https://github.com/cozycactus/rx888_test |
great, next problem CubicSDR found the device:Cypress Semiconductor Corp. RX888 :: 0008012302023031 gqrx found it not. grts radioman1511 |
Hello, greetings, i have a problem to compile your sources on Mac mini M2 .
The following error appears:
Undefined symbols for architecture arm64:
"SoapySDR::Device::getSettingInfo(std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator> const&) const", referenced from:
vtable for SoapyRX888 in Settings.cpp.o
"SoapySDR::Device::getSettingInfo(int, unsigned long, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator> const&) const", referenced from:
vtable for SoapyRX888 in Settings.cpp.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [librx888Support.so] Error 1
make[1]: *** [CMakeFiles/rx888Support.dir/all] Error 2
make: *** [all] Error 2
What am I doing wrong ?
The text was updated successfully, but these errors were encountered: