I am trying to build chromium with minimal features using Fedora 23 64bit.
I followed the link from cef website did the below steps.
installed depot_tools package
mkdir chromium
cd chromium
fetch --no-history --no-hooks chromium
cd src
gclient runhooks
gn gen out/Default
ninja -C out/Default chrome
Build success
Now, When I tried launching the chrome (out/Default/chrome) I get the below error:
LaunchProcess: failed to execvp:
Also, I don't see libcef.so anywhere in my src folder.
Please help and guide to get a mimimal version built and running.
Before "gn gen out/Default" you need to execute these commands to get release build:
gn args out/Default, and
type "is_debug = false" in an opened editor
After build you can then run "cd out/Default && ninja mini_installer" to get an installer and archive of redistributable files.
Related
I am trying to run node js application by using appsody. I have installed appsody using brew and made project by running appsody init nodejs-express command.
Now when I run appsody run command. I get the below error. I have pulled ubuntu image from docker hub ( docker pull ubuntu ) and agin run this command but no success.
Steps I did
brew install appsody/appsody/appsody
appsody list
mkdir my-project
cd my-project
appsody init nodejs-express
appsody run
Getting below error
no matching manifest for linux/arm64/v8 in the manifest list entries
What am I doing wrong ?
This means that the appsody/init-controller image is not available for your native platform (which is linux/arm64/v8). If you click the link (earlier in this sentence) and look at the "Tags" tab on Docker Hub you'll see this image is only being published for linux/amd64 (Intel) and two other platforms, but not for ARM64.
To make this work, you need to specify another platform. You can do that by setting this environment variable before running the application:
export DOCKER_DEFAULT_PLATFORM=linux/amd64
NOTE: Docker can do this emulation (running amd64 on ARM) using qemu, but it is sometimes unstable. You may find the containers crash. But other times it works fine; YMMV.
Another option could be to rebuild all the needed images as ARM64. To do this you'd need to identify all of the images that matter, and try to find source material to rebuild them. Sometimes those are available (e.g. on GitHub) - other times they are not published. So this may not be an option for you.
Any one who is running docker by appsody and face the above problem below command worked for me.
The gist is to concatenate your command with #Dan Lowe command.
{
"label": "Appsody: debug",
"type": "shell",
"command": "export DOCKER_DEFAULT_PLATFORM=linux/amd64;appsody debug --network my-microservice_default --docker-options '--env KAFKA_BOOTSTRAP_SERVERS=kafka:xxxx' -p xxxx:xxxx -p xxxx:xxxx -p xxxx:xxxx",
"group": "build",
"problemMatcher": []
},
This is not a duplicate because although the error is same, my use case is different from others.
I am compiling a go application to deploy with docker on:
latest arch linux
latest docker version, golang:alpine image
tried with go version 1.13.3 and 1.14.4 linux amd64
i have no bash scripts or wrong file endings. Whole project is written on this Linux machine
i can deploy an empty go app that has only a fmt print without any error
however,
when i build it on my OSX machine, and send it to linux, I can deploy that executable to docker without any error
OSX mojave
latest docker
go 1.13.3
GOOS=linux
Error :
standard_init_linux.go:211: exec user process caused "no such file or directory"
When you compile your go app with cgo enabled the compiler links dynamically to libstdc .
However, golang:alpine image is so small, because it is not using libstdc but a simplified version of it called musl libc.
The error message says
standard_init_linux.go:211: exec user process caused "no such file or directory"
If you connect to your image with
$ docker run -it [image] /bin/sh
you can find your executable in let's say /dist/myexec, but when you try to run that executable, it says err not found, because of not that it can't find your executable, obviously, but it can't find file libc .
The solution is to either
disable CGO : use CGO_ENABLED=0 while building
or add
RUN apk add --no-cache libc6-compat
to your Dockerfile
or do not use golang:alpine
To have a all static binary executable, build it with:
$ CGO_ENABLED=0 GOOS=linux go build -a -ldflags '-extldflags "-static"' .
I am following this tutorial. I have compiled the code successfully, but when I try to run using command arm-none-eabi-gdb -q thumbv7em-none-eabihf/debug/led-roulette on terminal, it says that:
C:\Program Files (x86)\GNU Tools ARM Embedded\8 2018-q4-major\bin\arm-none-eabi-gdb.exe: warning: Couldn't determine a path for the index cache directory.
thumbv7em-none-eabihf/debug/led-roulette: No such file or directory
Although, I have physically checked the path and the file does exist there.
I am a beginner to stm32f3Discovery and trying to setup the device using the documentation
Steps taken so far:
Already added the target using:
rustup target add thumbv7em-none-eabihf
Compiled the program using command:
cargo build --target thumbv7em-none-eabihf
Getting correct output of the following command:
cargo readobj --target thumbv7em-none-eabihf --bin led-roulette -- -file-headers
As I am on Windows, I've tried the following command to launch openOCD:
openocd -s C:\OpenOCD\scripts -f interface/stlink-v2-1.cfg -f target/stm32f3x.cfg
Run this command to connect to gdb server, but failed:
arm-none-eabi-gdb -q target/thumbv7em-none-eabihf/debug/led-roulette
The above command should work and connect GDB server, but it doesn't.
Thanks hellow.. Your 'Triple check' statement works for me. Yes, it was the path issue which i had to change while debugging. It is rocking..
I use git clone git://git.linphone.org/linphone-android.git --recursive
I follow instruction on https://github.com/BelledonneCommunications/linphone-android/ and download lastest SDK and NDK
I set path -> sudo gedit ~/.bashrc and add last line with :
export ANDROID_HOME=/home/onysevensmarts/Android/Sdk
export ANDROID_NDK=/home/onysevensmarts/Android/Sdk/ndk-bundle
export JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64
export PATH=$PATH:$ANDROID_HOME/tools
export PATH=$PATH:$ANDROID_HOME/platform-tools
export PATH=$PATH:$ANDROID_NDK
export PATH=$PATH:$JAVA_HOME
4.I've just install Install yasm, nasm , python, pkg_config, doxygen, graphviz and cmake 3.14 .
5.At Root direktori , execute command ./prepare.py
showing message :
Configure project :liblinphone-sdk
native sdk not ready yet
6.Then I Download last liblinphone (liblinphone-android-sdk-4.0.1.zip) at https://www.linphone.org/technical-corner/liblinphone
7.I extract them, there are 3 files
- liblinphone-sdk-javadoc.jar,
- liblinphone-sdk-release.aar,
- liblinphone-sdk-sources.jar.
8. I copy them to liblinphone-sdk folder on root direktory project.
9. I try ./prepare.py againt and still show error : native sdk not ready yet.
Where i do wrong? , and i try to 'make' , this error still show,
i try open on Android Studio and i build , error message path=""
Anyone ever see this case, help .
Check cd ~/Android/Sdk/tools/bin./sdkmanager "platform-tools" "platforms;android-28" https://developer.android.com/studio/command-line/sdkmanager.html
if number 1 error, do : export JAVA_OPTS='-XX:+IgnoreUnrecognizedVMOptions --add-modules java.se.ee'
if repositories.cfg not found ,then : touch ~/.android/repositories.cfg
sudo pip install pystache
if pip not found : sudo apt install python-pip
pip install pystache
run 'make'
try to 'make install' and make sure android device connected debugging with your PC.
I'm running Cygwin 64bit but can't seem to get OpenShift oc command line to work
I downloaded oc.tar.gz ( from here https://mirror.openshift.com/pub/openshift-v3/clients/3.6.173.0.5/linux/oc.tar.gz ), unzipped it and placed it in my path in /usr/bin
When I try to run: oc login I get the following.
-bash: /usr/bin/oc: cannot execute binary file: Exec format error
Do I need to somehow 'install' the executable ?
Any help would be much appreciated.
In addition to #Graham Dumpleton's answer:
open cygwin and check for directory /usr/local/bin
mkdir -p local/bin
$ cd /usr/local/bin
if it does not exists:
$ mkdir -p local/bin
finally extract the windows package:
$ cp /cygdrive/c/Users/me/Downloads/oc-3.5.5.31.24-windows.zip /usr/local/bin/
unzip oc-3.5.5.31.24-windows.zip
$ oc version
oc v3.5.5.31.24
kubernetes v1.5.2+43a9be4
features: Basic-Auth
Use the Windows binary from the following page:
https://github.com/openshift/origin/releases
From project homepage
https://www.cygwin.com/
Cygwin is not:
a way to run native Linux apps on Windows. You must rebuild your
application from source if you want it to run on Windows.
a way to magically make native Windows apps aware of UNIX®
functionality like signals, ptys, etc. Again, you need to build your
apps from source if you want to take advantage of Cygwin
functionality.