Whey trying to build a new AUR package for this new SD 1.3.1 release, the package successfully runs ./build.sh linguist but bails when running ./build.sh release with the following:
Compiling SilentDragon 1.3.1 with 16 threads...
QMake version 3.1
Using Qt version 5.15.8 in /usr/lib
GNU Make 4.4.1
Built for x86_64-pc-linux-gnu
Copyright (C) 1988-2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Makefile:2159: warning: overriding recipe for target 'src/ui_viewalladdresses.h'
Makefile:2151: warning: ignoring old recipe for target 'src/ui_viewalladdresses.h'
Makefile:2171: warning: overriding recipe for target 'src/ui_viewalladdresses.h'
Makefile:2159: warning: ignoring old recipe for target 'src/ui_viewalladdresses.h'
res/libsodium/buildlibsodium.sh
Building libsodium
/usr/bin/rcc -name application application.qrc -o qrc_application.cpp
libsodium-1.0.18.tar.gz: OK
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /sbin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether UID '1000' is supported by ustar format... yes
checking whether GID '1000' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking whether make supports nested variables... (cached) yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/mnt/MY_PATH/AUR/silentdragon/tst2/src/silentdragon/res/libsodium/libsodium-1.0.18':
configure: error: C compiler cannot create executables
See `config.log' for more details
make[1]: Entering directory '/mnt/MY_PATH/AUR/silentdragon/tst2/src/silentdragon/res/libsodium/libsodium-1.0.18'
make[1]: *** No rule to make target 'clean'. Stop.
make[1]: Leaving directory '/mnt/MY_PATH/AUR/silentdragon/tst2/src/silentdragon/res/libsodium/libsodium-1.0.18'
Building libsodium with 4 cores...
make[1]: Entering directory '/mnt/MY_PATH/AUR/silentdragon/tst2/src/silentdragon/res/libsodium/libsodium-1.0.18'
make[1]: warning: -j4 forced in submake: resetting jobserver mode.
make[1]: *** No targets specified and no makefile found. Stop.
make[1]: Leaving directory '/mnt/MY_PATH/AUR/silentdragon/tst2/src/silentdragon/res/libsodium/libsodium-1.0.18'
cp: cannot stat 'libsodium-1.0.18/src/libsodium/.libs/libsodium.a': No such file or directory
make: *** [Makefile:1249: /mnt/MY_PATH/AUR/silentdragon/tst2/src/silentdragon/res/libsodium.a] Error 1
make: *** Waiting for unfinished jobs....
==> ERROR: A failure occurred in build().
Aborting...
The strange thing here is that I have successfully tested an Arch Linux "manual" build as written in the README.md, yet this package is going THE SAME THING and doesn't want to work. I was able to manually build the previous version of SD this method too, as mentioned in Issue https://git.hush.is/jahway603/AUR-packages/issues/1
I also saw SD not build on Ubuntu 20.04 with something about libsodium as seen in SD Issue hush/SilentDragon#125
?????????????
Whey trying to build a new AUR package for this new SD 1.3.1 release, the package successfully runs `./build.sh linguist` but bails when running `./build.sh release` with the following:
```
Compiling SilentDragon 1.3.1 with 16 threads...
QMake version 3.1
Using Qt version 5.15.8 in /usr/lib
GNU Make 4.4.1
Built for x86_64-pc-linux-gnu
Copyright (C) 1988-2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Makefile:2159: warning: overriding recipe for target 'src/ui_viewalladdresses.h'
Makefile:2151: warning: ignoring old recipe for target 'src/ui_viewalladdresses.h'
Makefile:2171: warning: overriding recipe for target 'src/ui_viewalladdresses.h'
Makefile:2159: warning: ignoring old recipe for target 'src/ui_viewalladdresses.h'
res/libsodium/buildlibsodium.sh
Building libsodium
/usr/bin/rcc -name application application.qrc -o qrc_application.cpp
libsodium-1.0.18.tar.gz: OK
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /sbin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether UID '1000' is supported by ustar format... yes
checking whether GID '1000' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking whether make supports nested variables... (cached) yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/mnt/MY_PATH/AUR/silentdragon/tst2/src/silentdragon/res/libsodium/libsodium-1.0.18':
configure: error: C compiler cannot create executables
See `config.log' for more details
make[1]: Entering directory '/mnt/MY_PATH/AUR/silentdragon/tst2/src/silentdragon/res/libsodium/libsodium-1.0.18'
make[1]: *** No rule to make target 'clean'. Stop.
make[1]: Leaving directory '/mnt/MY_PATH/AUR/silentdragon/tst2/src/silentdragon/res/libsodium/libsodium-1.0.18'
Building libsodium with 4 cores...
make[1]: Entering directory '/mnt/MY_PATH/AUR/silentdragon/tst2/src/silentdragon/res/libsodium/libsodium-1.0.18'
make[1]: warning: -j4 forced in submake: resetting jobserver mode.
make[1]: *** No targets specified and no makefile found. Stop.
make[1]: Leaving directory '/mnt/MY_PATH/AUR/silentdragon/tst2/src/silentdragon/res/libsodium/libsodium-1.0.18'
cp: cannot stat 'libsodium-1.0.18/src/libsodium/.libs/libsodium.a': No such file or directory
make: *** [Makefile:1249: /mnt/MY_PATH/AUR/silentdragon/tst2/src/silentdragon/res/libsodium.a] Error 1
make: *** Waiting for unfinished jobs....
==> ERROR: A failure occurred in build().
Aborting...
```
**The strange thing here is that I have successfully tested an Arch Linux "manual" build as written in the [README.md](https://git.hush.is/hush/SilentDragon#arch-linux), yet this package is going THE SAME THING and doesn't want to work. I was able to manually build the previous version of SD this method too, as mentioned in Issue https://git.hush.is/jahway603/AUR-packages/issues/1**
I also saw SD not build on Ubuntu 20.04 with something about libsodium as seen in SD Issue https://git.hush.is/hush/SilentDragon/issues/125
?????????????
@duke just changed ./build.sh release to just ./build.sh in the PKGBUILD file and I get the following (which I don't want to publicly share, so it's in this repo).
@duke just changed `./build.sh release` to just `./build.sh` in the PKGBUILD file and I get the following (which I don't want to publicly share, so it's in [this repo](https://git.hush.is/jahway603/thisfucknsnow/issues/1)).
@jahway603 sounds related to the fact that build.sh release uses linux-clang as a compiler instead of gcc. So you probably don't have a working clang compiler on that machine.
@jahway603 sounds related to the fact that `build.sh release` uses linux-clang as a compiler instead of gcc. So you probably don't have a working clang compiler on that machine.
Section 2.2 of https://wiki.archlinux.org/title/Clang might help you
@duke clang is already installed on this Arch system. I can manually run ./build.sh or ./build.sh release & both build SD 1.3.1 perfectly fine.
This Issue is that the package is not letting me proceed, which makes no sense at all, on the same exact system I've manually build SD 1.3.1 on a ton already. None of this makes any sense.
@duke clang is already installed on this Arch system. I can **manually** run `./build.sh` or `./build.sh release` & both build SD 1.3.1 perfectly fine.
This Issue is that the package is not letting me proceed, which makes no sense at all, on the same exact system I've manually build SD 1.3.1 on a ton already. None of this makes any sense.
@jahway603 in reading some links about other projects getting this error, it seems to happen when a compiler is changed and there is some compiled files left over from a previous compile. The AUR package creation process must have some kind of cached directory of a previous compile which needs to be deleted.
A normal build.sh uses gcc but build.sh release uses clang, so that is the change of compiler. Also, if you changed package creation to switch between build.sh and "build.sh release", that may leave some compiled files around that mess things up.
@jahway603 in reading some links about other projects getting this error, it seems to happen when a compiler is changed and there is some compiled files left over from a previous compile. The AUR package creation process must have some kind of cached directory of a previous compile which needs to be deleted.
A normal `build.sh` uses gcc but `build.sh release` uses clang, so that is the change of compiler. Also, if you changed package creation to switch between build.sh and "build.sh release", that may leave some compiled files around that mess things up.
Closing issue as I was able to get it to build in the PKGBUILD with commit 91ab6334a8
Closing issue as I was able to get it to build in the PKGBUILD with commit https://git.hush.is/jahway603/AUR-packages/commit/91ab6334a858283bed1a9075afe3bd31bef89b53
Whey trying to build a new AUR package for this new SD 1.3.1 release, the package successfully runs
./build.sh linguistbut bails when running./build.sh releasewith the following:The strange thing here is that I have successfully tested an Arch Linux "manual" build as written in the README.md, yet this package is going THE SAME THING and doesn't want to work. I was able to manually build the previous version of SD this method too, as mentioned in Issue https://git.hush.is/jahway603/AUR-packages/issues/1
I also saw SD not build on Ubuntu 20.04 with something about libsodium as seen in SD Issue hush/SilentDragon#125
?????????????
@jahway603
checking whether the C compiler works... noseems bad.Does
./build.shby itself work ?@duke just changed
./build.sh releaseto just./build.shin the PKGBUILD file and I get the following (which I don't want to publicly share, so it's in this repo).@duke when using just
./build.shby itself, I do getchecking whether the C compiler works... yes@jahway603 sounds related to the fact that
build.sh releaseuses linux-clang as a compiler instead of gcc. So you probably don't have a working clang compiler on that machine.Section 2.2 of https://wiki.archlinux.org/title/Clang might help you
@duke clang is already installed on this Arch system. I can manually run
./build.shor./build.sh release& both build SD 1.3.1 perfectly fine.This Issue is that the package is not letting me proceed, which makes no sense at all, on the same exact system I've manually build SD 1.3.1 on a ton already. None of this makes any sense.
@jahway603 in reading some links about other projects getting this error, it seems to happen when a compiler is changed and there is some compiled files left over from a previous compile. The AUR package creation process must have some kind of cached directory of a previous compile which needs to be deleted.
A normal
build.shuses gcc butbuild.sh releaseuses clang, so that is the change of compiler. Also, if you changed package creation to switch between build.sh and "build.sh release", that may leave some compiled files around that mess things up.Closing issue as I was able to get it to build in the PKGBUILD with commit
91ab6334a8