note: Undefined symbols for architecture x86_64:
"_CFURLResourceIsReachable", referenced from:
alacritty::config::Monitor:🆕:_$u7b$$u7b$closure$u7d$$u7d$::h8c82fbfba8a3a673 in alacritty-6a8d3226ed5c4bef.alacritty.9tpyu7jw-cgu.1.rcgu.o
"_NSDefaultRunLoopMode", referenced from:
alacritty::main::hd6e46019b2208595 in alacritty-6a8d3226ed5c4bef.alacritty.9tpyu7jw-cgu.1.rcgu.o
ld: symbol(s) not found for architecture x86_64
clang-5.0: error: linker command failed with exit code 1 (use -v to see invocation)
* polar-bookshelf: init at 1.0.11
* Grab gsettings_desktop_schemas from gnome3
* Explain why we're not building from source
* Use autoPatchelfHook
* Updated license & further cleanup
gImageReader is a GUI for tesseract, an optical character recognition engine.
While the UI supports Qt/Gtk, I have only added the gtk one in the nix derivation.
* uses meson now
* crashes on start complaining schema not installed,
so I added a postInstall that compiles the schema?
Fixes the problem but I'm not particularly familiar
with these bits so review appreciated.
These packages should in theory work with our GCC toolchains, but
there are some definite breakages that need to be tracked down.
Comparing output of these to old gcc-arm-embedded is important.
Affected packages include:
- axolooti
- avrdudess
- opentx
- microscheme
- betaflight
- inav
- blackmagic
- simavr
- gnuk
Upgrading icalendar to 4.0.3 broke the pinned dateutil version.
Luckily khal 0.9.10 now works with dateutil 2.7, so we no longer need to
override it. However now one test in khal fails (the string output
changed from icalendar 4.0.2 to 4.0.3)...
* the jre is no longer an official part of the jdk (jmod is
recommended as a replacement when needing to create smaller runtime
images)
* darwin continues to use zulu from azul
* apps that used 10 now use 11 (eclipse, bazel, josm)
There is at least one recorded issue against our kiwix version. Upstream
does no longer support this version of the project. They have moved to a
different repository & software architecture.
Removed the wxGUI switch because it was never working.
To build VeraCrypt text-only you still need wxGTK _and_ you need to
rebuild wxGTK without GUI too...
Moreover, the normal build provides both GUI and text-only interfaces
so it is already usable in pure CLI contexts.
TrueCrypt has been retired for a while now and the source archive we
pointed to is gone. Moreover the VeraCrypt fork is available, maintained
and fixes issues previous audits found in TrueCrypt.
