File soapy-remote.spec of Package failed_soapy-remote

```
Name:           soapysdr0.8-module-remote
Version:        0.5.2
Release:        1.1
Summary:        Remote support module for SoapySDR
License:        BSD-3-Clause
Group:          Development/Libraries/C and C++
URL:            https://github.com/pothosware/SoapyRemote
Source0:        %{name}-%{version}.tar.gz
BuildRequires:  cmake
BuildRequires:  gcc-c++
BuildRequires:  pkgconfig
BuildRequires:  SoapySDR-devel
Requires:       SoapySDR

%description
This package provides the remote support module for SoapySDR, enabling
remote device access over a network.

%prep
%setup -q

%build
mkdir -p build
cd build
cmake .. \
    -DCMAKE_INSTALL_PREFIX=%{_prefix} \
    -DCMAKE_INSTALL_LIBDIR=%{_libdir} \
    -DCMAKE_BUILD_TYPE=RelWithDebInfo
make %{?_smp_mflags}

%install
%make_install

# Ensure the correct module directory is used
mkdir -p %{buildroot}%{_libdir}/SoapySDR/modules0.8-3
mv %{buildroot}%{_libdir}/SoapySDR/modules0.8-3/libremoteSupport.so %{buildroot}%{_libdir}/SoapySDR/modules0.8-3/

%files
%license LICENSE_1_0.txt
%doc README.md Changelog.txt
%{_libdir}/SoapySDR/modules0.8-3/libremoteSupport.so
%{_bindir}/SoapySDRServer
%{_mandir}/man1/SoapySDRServer.1*
%{_unitdir}/SoapySDRServer.service
%{_sysconfdir}/sysctl.d/SoapySDRServer.conf

%changelog
* Sun Aug 10 2025 Your Name <your.email@example.com> - 0.5.2-1.1
- Initial package for SoapySDR remote module.
```

### Explanation of Changes
1. **Updated `%install` Section**:
   - Added `mkdir -p` to ensure the `modules0.8-3` directory exists.
   - Used `mv` to explicitly place the `libremoteSupport.so` file in the correct directory.

2. **Updated `%files` Section**:
   - Changed the path from `modules0.8` to `modules0.8-3` to match the actual installation directory.

### Additional Notes
- The `modules0.8-3` directory reflects the version of the SoapySDR API being used. If this version changes in the future, the spec file must be updated accordingly.
- The `%make_install` macro ensures that the `make install` step is executed correctly, but additional steps (like `mkdir` and `mv`) are necessary to align with the RPM packaging expectations.

By applying these changes, the build process should complete successfully without encountering the "Directory not found" or "File not found" errors.