I'm running in a Docker image. When I do an apk add tesseract-ocr, I get version 4.0.0. I found version 4.1.1 here: https://alpine.pkgs.org/edge/alpine-community-aarch64/tesseract-ocr-4.1.1-r5.apk.html. Tried various combinations with apk add --repository, but couldn't get it working. So I just downloaded the apk file and now trying to install it directly, but it's not automatically getting the dependencies. Any ideas? I'm a newbie when it comes to using APK. Not sure what the APKINDEX is that it's complaining about
# apk add --allow-untrusted tesseract-ocr-4.1.1-r5.apk
fetch https://pkgs.org/x86_64/APKINDEX.tar.gz
ERROR: https://pkgs.org/: Permission denied
WARNING: Ignoring APKINDEX.8fc13182.tar.gz: No such file or directory
ERROR: unsatisfiable constraints:
so:libicui18n.so.67 (missing):
required by: tesseract-ocr-4.1.1-r5[so:libicui18n.so.67]
so:libicuuc.so.67 (missing):
required by: tesseract-ocr-4.1.1-r5[so:libicuuc.so.67]
/ #
Here is the contains of /etc/apk/repositories when the docker image first comes up
/ # cat /etc/apk/repositories
http://dl-cdn.alpinelinux.org/alpine/v3.9/main
http://dl-cdn.alpinelinux.org/alpine/v3.9/community
My dockerfile contains FROM openjdk:8-jre-alpine
All my experimentation has been done on a clean image, so nothing is messed up.
Related
I am trying to build an application that communicates with dds with opendds. I am using the opendds layer on krikstone. The bitbake image is built with the opendds libraries but when I build the sdk it seems the layer nativesdk is not installed. When I run the cmake I get the error "Missing required dependencies OPENDDS_IDL;ACE_GPERF;TAO_IDL".
from the opendds.inc I see there is the nativesdk install. I added a junk line and expected that when i build the opendds or build the populate-sdk I will fail but it seems that the nativesdk is not run.
build is for imx8mm variscite som with command bitbake fsl-image-qt5 -v populate_sdk_ext
layer with the problem is meta-opendds (krikstone branch) building version 3.22
the layer has a bb file that requires an opendds.inc file which has the nativesdk install
Blockquote
do_install:append:class-nativesdk() {
dfdf -- my junk line to trigger failure
ln -sf ${bindir}/opendds_idl ${D}${datadir}/dds/bin/opendds_idl
ln -sf ${bindir}/ace_gperf ${D}${datadir}/ace/bin/ace_gperf
ln -sf ${bindir}/tao_idl ${D}${datadir}/ace/bin/tao_idl
}
Blockquote
** i added a junk line to trigger failure but it doesnt fail with building the sdk or image itself
why is the nativesdk command not run and why is the sdk without the opendds_idl executable
thanks
I was able at last to build the nativesdk files. I had to build them specifically as they are not build by default. i had to "bitbake nativesdk-opendds" manually.
my mistake was to believe that the nativesdk will be defaulted. my assumption is that if i am using the opendds that most probable that i will build subscribers/produces applications and will need the opendds_idl executable.
!!!! after testing the nativesdk-opendds it did not solve the problem !!!
!! in general after adding building the opendds layer i cannot build the Messanger example for lack of the opendds_idl and other two (tao,ace) executable
I'm getting a Failed to start plugin error when trying to add the grafana-druid plugin:
EROR[09-22|14:50:59] Failed to start plugin
logger=plugins.backend pluginId=grafadruid-druid-datasource
error="fork/exec /Users/Documents/Projects/Software/Plugins/druid/dist/grafadruid-druid-datasource_darwin_amd64:
no such file or directory"
I've taken the Source code for druid-grafana plugin from here - https://github.com/grafadruid/druid-grafana/releases/tag/v1.3.0
And I built it using npm install followed by npm run build, but after I copied the dist folder into the plugins directory, I see this error. It's looking for an amd64 binary, but the other plugins I added (which don't have the binary in their dist folders) using the same process work without issues. I'm running Grafana version 8.1.8. Any help appreciated.
I'm trying to get manpages working on alpinelinux 3.12, used latest 3.12 version and:
# apk add man
ERROR: unsatisfiable constraints:
man (missing):
required by: world[man]
Weird? apk add man-pages works perfectly. I've enabled all repos (community, edge, etc) apk update and still can't find man?
Found the problem they changed package name from man to mandoc. apk add man doesn't work anymore, it's:
# apk add mandoc
in 3.12
I am trying to install GTK on my Mac (running Catalina) using vcpkg.
I get the following error message on running ./vcpkg install gtk
How can I fix this?
Error: Building package glib:x64-osx failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: glib:x64-osx
Vcpkg version: 2019.09.12-unknownhash
Additionally, attach any relevant sections from the log files above.
EDIT
I used --keep-going while running the install command, and it installed all the packages that do not require glib to build.
I've added the log file outputs:
config-x64-osx-dbg-out.log
config-x64-osx-dbg-err.log
CMakeOutput.log
I have a Yocto bitbake image recipe that can be built successfully.
However, the same image recipe fails when generating SDK with -c populate_sdk command.
The error seems to be caused by mixing 32-bit and 64-bit versions of libraries, which is fine when building images with only binaries, but the header files collide with each other when populating the SDK root fs:
Running transaction check
Transaction check succeeded.
Running transaction test
Error: Transaction check error:
file /usr/bin/curl-config from install of lib32-curl-dev-7.53.1-r0.cortexa7hf_neon_vfpv4 conflicts with file from package curl-dev-7.53.1-r0.aarch64
file /usr/include/nettle/version.h from install of lib32-nettle-dev-3.3-r0.cortexa7hf_neon_vfpv4 conflicts with file from package nettle-dev-3.3-r0.aarch64
file /usr/include/nettle/nettle-stdint.h from install of lib32-nettle-dev-3.3-r0.cortexa7hf_neon_vfpv4 conflicts with file from package nettle-dev-3.3-r0.aarch64
What is the best way to exclude 32-bit versions of libraries(recipes) when doing -c populate_sdk without excluding them entirely from the production image?
You can remove target packages from the toolchain by removing them from the TOOLCHAIN_TARGET_TASK variable and host packages by removing them from the TOOLCHAIN_HOST_TASK.
For example to remove the target package "curl-dev" from your sdk you have to add the following in your image recipe:
TOOLCHAIN_TARGET_TASK_remove = "curl-dev"
To remove the same host package from your sdk you have to add the following in your image recipe:
TOOLCHAIN_HOST_TASK_remove = "curl-dev"