Develop Reference

How can i build Miscord on aarch64?

I am trying to build Miscord from source
(https://github.com/miscord/miscord/archive/v5.0.4.tar.gz)
on aarch64(my phone). root#kali is a Chroot enviorment on my phone. I have tested other distros((debian&ubuntu)aarch64) but no success as well. On PC amd64 starts no problem.
This is how i tried to start it. Posted the log at the bottom.
Thanks in advance!
npm was installed with
apt get install npm
Here is the commands i run:
root#kali:/home/kali/Miscdord# cd miscord-5.0.4/
root#kali:/home/kali/Miscdord/miscord-5.0.4# ls
CHANGELOG.md Dockerfile package.json tsconfig.json
CODE_OF_CONDUCT.md Dockerfile.beta package-lock.json tslint.json
config.example.json Dockerfile.dev README.md
CONTRIBUTING.md LICENSE.md src
dist node_modules static
root#kali:/home/kali/Miscdord/miscord-5.0.4# npm install
> miscord#5.0.4 prepare
> npm run clean && npm run compile
> miscord#5.0.4 clean
> shx rm -rf dist/
> miscord#5.0.4 compile
> tsc
up to date, audited 518 packages in 5m
10 vulnerabilities (5 low, 1 moderate, 4 high)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
root#kali:/home/kali/Miscdord/miscord-5.0.4# npm start
> miscord#5.0.4 start
> npm run prepare && node dist/bin/index.js
> miscord#5.0.4 prepare
> npm run clean && npm run compile
> miscord#5.0.4 clean
> shx rm -rf dist/
> miscord#5.0.4 compile
> tsc
Miscord should not be run with root permissions.
If running without sudo doesn't work, you can either fix your permission problems or change where npm stores global packages by putting ~/npm/bin in your PATH and running:
npm config set prefix ~/npm
See: https://github.com/sindresorhus/guides/blob/master/npm-global-without-sudo.md
If you really need to run Miscord with sudo, add parameter --runningWithSudoIsDangerous.
npm ERR! code 77
npm ERR! path /home/kali/Miscdord/miscord-5.0.4
npm ERR! command failed
npm ERR! command sh -c npm run prepare && node dist/bin/index.js
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2020-10-28T22_36_22_637Z-debug.log
Here is the log:
0 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
1 info using npm#7.0.3
2 info using node#v12.19.0
3 timing config:load:defaults Completed in 2ms
4 timing config:load:file:/usr/share/npm/npmrc Completed in 3ms
5 timing config:load:builtin Completed in 3ms
6 timing config:load:cli Completed in 2ms
7 timing config:load:env Completed in 1ms
8 timing config:load:file:/home/kali/Miscdord/miscord-5.0.4/.npmrc Completed in 1ms
9 timing config:load:project Completed in 3ms
10 timing config:load:file:/root/.npmrc Completed in 0ms
11 timing config:load:user Completed in 0ms
12 timing config:load:file:/etc/npmrc Completed in 0ms
13 timing config:load:global Completed in 0ms
14 timing config:load:cafile Completed in 1ms
15 timing config:load:validate Completed in 0ms
16 timing config:load:setUserAgent Completed in 1ms
17 timing config:load:setEnvs Completed in 1ms
18 timing config:load Completed in 14ms
19 verbose npm-session 1d677a5bd581f35b
20 timing npm:load Completed in 26ms
21 timing command:run-script Completed in 250435ms
22 timing command:start Completed in 250438ms
23 verbose stack Error: command failed
23 verbose stack at ChildProcess.<anonymous> (/usr/share/npm/node_modules/#npmcli/promise-spawn/index.js:63:27)
23 verbose stack at ChildProcess.emit (events.js:314:20)
23 verbose stack at maybeClose (internal/child_process.js:1021:16)
23 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
24 verbose pkgid miscord#5.0.4
25 verbose cwd /home/kali/Miscdord/miscord-5.0.4
26 verbose Linux 4.14.117-perf+
27 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
28 verbose node v12.19.0
29 verbose npm v7.0.3
30 error code 77
31 error path /home/kali/Miscdord/miscord-5.0.4
32 error command failed
33 error command sh -c npm run prepare && node dist/bin/index.js
34 verbose exit 77

Issue compiling boringssl for Android

I'm trying to compile boringssl libraries so that I could use it in an Android project (building on Ubuntu 18.04). I'm following the build steps from this link.
amy#test-ubuntu18:~/android_test/boringssl/build$ cmake -DANDROID_ABI=arm64-v8a -DCMAKE_TOOLCHAIN_FILE=${ANDROID_NDK}/build/cmake/android.toolchain.cmake -DANDROID_NATIVE_API_LEVEL=21 -GNinja ..
CMake Error at CMakeLists.txt:14 (enable_language):
The CMAKE_C_COMPILER:
/home/amy/android_test/android-ndk-r21-beta2/toolchains/llvm/prebuilt/linux-x86_64/bin/clang
is not a full path to an existing compiler tool.
Here's my env set up:
amy#test-ubuntu18:~/android_test/boringssl/build$ echo $ANDROID_NDK
/home/amy/android_test/android-ndk-r21-beta2
amy#test-ubuntu18:~/android_test/boringssl/build$ echo $CC
/usr/bin/gcc
amy#test-ubuntu18:~/android_test/boringssl/build$ echo $CXX
/usr/bin/g++
And the tools do exist in my /usr/bin
amy#test-ubuntu18:~/android_test/boringssl/build$ ls -l /usr/bin/*g{cc,++}*
-rwxr-xr-x 1 root root 428 May 7 2006 /usr/bin/c89-gcc
-rwxr-xr-x 1 root root 454 Apr 11 2011 /usr/bin/c99-gcc
lrwxrwxrwx 1 root root 27 May 16 2018 /usr/bin/clang++ -> ../lib/llvm-6.0/bin/clang++
lrwxrwxrwx 1 root root 27 Apr 5 2018 /usr/bin/clang++-6.0 -> ../lib/llvm-6.0/bin/clang++
lrwxrwxrwx 1 root root 25 Apr 10 2019 /usr/bin/clang++-8 -> ../lib/llvm-8/bin/clang++
lrwxrwxrwx 1 root root 5 May 20 2019 /usr/bin/g++ -> g++-7
lrwxrwxrwx 1 root root 22 May 8 2019 /usr/bin/g++-7 -> x86_64-linux-gnu-g++-7
lrwxrwxrwx 1 root root 5 May 20 2019 /usr/bin/gcc -> gcc-7
lrwxrwxrwx 1 root root 22 May 8 2019 /usr/bin/gcc-7 -> x86_64-linux-gnu-gcc-7
lrwxrwxrwx 1 root root 8 May 20 2019 /usr/bin/gcc-ar -> gcc-ar-7
lrwxrwxrwx 1 root root 25 May 8 2019 /usr/bin/gcc-ar-7 -> x86_64-linux-gnu-gcc-ar-7
lrwxrwxrwx 1 root root 8 May 20 2019 /usr/bin/gcc-nm -> gcc-nm-7
lrwxrwxrwx 1 root root 25 May 8 2019 /usr/bin/gcc-nm-7 -> x86_64-linux-gnu-gcc-nm-7
lrwxrwxrwx 1 root root 12 May 20 2019 /usr/bin/gcc-ranlib -> gcc-ranlib-7
lrwxrwxrwx 1 root root 29 May 8 2019 /usr/bin/gcc-ranlib-7 -> x86_64-linux-gnu-gcc-ranlib-7
lrwxrwxrwx 1 root root 5 May 20 2019 /usr/bin/x86_64-linux-gnu-g++ -> g++-7
-rwxr-xr-x 1 root root 1010624 May 8 2019 /usr/bin/x86_64-linux-gnu-g++-7
lrwxrwxrwx 1 root root 5 May 20 2019 /usr/bin/x86_64-linux-gnu-gcc -> gcc-7
-rwxr-xr-x 1 root root 1010624 May 8 2019 /usr/bin/x86_64-linux-gnu-gcc-7
lrwxrwxrwx 1 root root 8 May 20 2019 /usr/bin/x86_64-linux-gnu-gcc-ar -> gcc-ar-7
-rwxr-xr-x 1 root root 27104 May 8 2019 /usr/bin/x86_64-linux-gnu-gcc-ar-7
lrwxrwxrwx 1 root root 8 May 20 2019 /usr/bin/x86_64-linux-gnu-gcc-nm -> gcc-nm-7
-rwxr-xr-x 1 root root 27104 May 8 2019 /usr/bin/x86_64-linux-gnu-gcc-nm-7
lrwxrwxrwx 1 root root 12 May 20 2019 /usr/bin/x86_64-linux-gnu-gcc-ranlib -> gcc-ranlib-7
-rwxr-xr-x 1 root root 27104 May 8 2019 /usr/bin/x86_64-linux-gnu-gcc-ranlib-7
Versions of tools are listed below:
amy#test-ubuntu18:~/android_test/boringssl/build$ ninja --version
1.8.2
amy#test-ubuntu18:~/android_test/boringssl/build$ cmake --version
cmake version 3.15.2
Tried the suggestions mentioned in this issue, but of no use.
The error says "/home/amy/android_test/android-ndk-r21-beta2/toolchains/llvm/prebuilt/linux-x86_64/bin/clang" is not full path, so I checked what's in the path (I don't see the "linux-x86_64" listed in there):
$ls -l /home/amy/android_test/android-ndk-r21-beta2/toolchains/llvm/prebuilt/
drwxrwxr-x 13 amy amy 4096 Jan 3 15:35 windows-x86_64

react native app crash after splash screen

I am new to React Native. I am created a new blank project in Expo XDE and when I'm trying to run it on my Android device every time it crash after splash screen. It's just a simple blank app.
There is no logs or errors. Expo app just return to first page.
Device: Android 7
XDE: Expo version 2.21.00
app.js
import React from 'react';
import { StyleSheet, Text, View } from 'react-native';
export default class App extends React.Component {
render() {
return (
<View style={styles.container}>
<Text>Open up App.js to start working on your app!</Text>
</View>
);
}
}
const styles = StyleSheet.create({
container: {
flex: 1,
backgroundColor: '#fff',
alignItems: 'center',
justifyContent: 'center',
},
});
Updated
npm start log:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Users\\Pfn\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'start' ]
2 info using npm#5.5.1
3 info using node#v6.11.3
4 verbose stack Error: missing script: start
4 verbose stack at run (C:\Users\Pfn\AppData\Roaming\npm\node_modules\npm\lib\run-script.js:151:19)
4 verbose stack at C:\Users\Pfn\AppData\Roaming\npm\node_modules\npm\lib\run-script.js:61:5
4 verbose stack at C:\Users\Pfn\AppData\Roaming\npm\node_modules\npm\node_modules\read-package-json\read-json.js:115:5
4 verbose stack at C:\Users\Pfn\AppData\Roaming\npm\node_modules\npm\node_modules\read-package-json\read-json.js:402:5
4 verbose stack at checkBinReferences_ (C:\Users\Pfn\AppData\Roaming\npm\node_modules\npm\node_modules\read-package-json\read-json.js:357:45)
4 verbose stack at final (C:\Users\Pfn\AppData\Roaming\npm\node_modules\npm\node_modules\read-package-json\read-json.js:400:3)
4 verbose stack at then (C:\Users\Pfn\AppData\Roaming\npm\node_modules\npm\node_modules\read-package-json\read-json.js:160:5)
4 verbose stack at ReadFileContext.<anonymous> (C:\Users\Pfn\AppData\Roaming\npm\node_modules\npm\node_modules\read-package-json\read-json.js:332:20)
4 verbose stack at ReadFileContext.callback (C:\Users\Pfn\AppData\Roaming\npm\node_modules\npm\node_modules\graceful-fs\graceful-fs.js:78:16)
4 verbose stack at FSReqWrap.readFileAfterOpen [as oncomplete] (fs.js:367:13)
5 verbose cwd F:\react\my-new-project
6 verbose Windows_NT 10.0.15063
7 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Pfn\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "start"
8 verbose node v6.11.3
9 verbose npm v5.5.1
10 error missing script: start
11 verbose exit [ 1, true ]
after adding this:
"scripts": {
"start": "node app.js"
}
to package.json log :
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Users\\Pfn\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'start' ]
2 info using npm#5.5.1
3 info using node#v6.11.3
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle my-new-project#0.0.0~prestart: my-new-project#0.0.0
6 info lifecycle my-new-project#0.0.0~start: my-new-project#0.0.0
7 verbose lifecycle my-new-project#0.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle my-new-project#0.0.0~start: PATH: C:\Users\Pfn\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin;F:\react\my-new-project\node_modules\.bin;C:\Program Files\Expo XDE\resources\app\node_modules\xdl\binaries\windows\adb;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Smart Projects\IsoBuster;C:\Program Files\PuTTY\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;D:\xampp\php;C:\ProgramData\ComposerSetup\bin;C:\Program Files\nodejs\;C:\Users\Pfn\AppData\Roaming\npm;C:\Users\Pfn\AppData\Local\Microsoft\WindowsApps;C:\Users\Pfn\AppData\Roaming\Composer\vendor\bin;C:\Users\Pfn\AppData\Roaming\npm
9 verbose lifecycle my-new-project#0.0.0~start: CWD: F:\react\my-new-project
10 silly lifecycle my-new-project#0.0.0~start: Args: [ '/d /s /c', 'node app.js' ]
11 silly lifecycle my-new-project#0.0.0~start: Returned: code: 1 signal: null
12 info lifecycle my-new-project#0.0.0~start: Failed to exec start script
13 verbose stack Error: my-new-project#0.0.0 start: `node app.js`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Users\Pfn\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:280:16)
13 verbose stack at emitTwo (events.js:106:13)
13 verbose stack at EventEmitter.emit (events.js:191:7)
13 verbose stack at ChildProcess.<anonymous> (C:\Users\Pfn\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at emitTwo (events.js:106:13)
13 verbose stack at ChildProcess.emit (events.js:191:7)
13 verbose stack at maybeClose (internal/child_process.js:920:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
14 verbose pkgid my-new-project#0.0.0
15 verbose cwd F:\react\my-new-project
16 verbose Windows_NT 10.0.15063
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Pfn\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v6.11.3
19 verbose npm v5.5.1
20 error code ELIFECYCLE
21 error errno 1
22 error my-new-project#0.0.0 start: `node app.js`
22 error Exit status 1
23 error Failed at the my-new-project#0.0.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
update2:
npm install warnings :
npm WARN react-native-branch#2.0.0-beta.3 requires a peer of react#>=15.4.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-native-gesture-handler#1.0.0-alpha.28 requires a peer of react#> 15.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: sshpk#1.13.0 (node_modules\fsevents\node_modules\sshpk):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Error: EPERM: operation not permitted, rename 'F:\react\my-new-project\node_modules\fsevents\node_modules\sshpk' -> 'F:\react\my-new-project\node_modules\fsevents\node_modules\.sshpk.DELETE'
added 5 packages and updated 2 packages in 70.53s

Which OS? Mac, Win, or Linux? If you're on Linux, did you open the XDE client using this command?
On Linux, open with chmod a+x xde*.AppImage and ./xde*.AppImage
Regardless of your OS, are you sure you have...
the latest version of node installed?
the latest version of watchman installed?
A shot in the dark, but once you've updated the above, I would start a new project and try again.
UPDATE: Looking more closely at your logs, I can see you're on Windows since the paths are "C:\...", so ignore the linux comment above. I still think your environment isn't setup correctly though. Reinstalling node and/or watchman may help (most likely node). You might also try installing yarn and see if that makes a difference. Sometimes it does for me.

ionic build error code 137

I am trying to build my app for android. It built fine for the first time but there were some typos in first so i edited the html and now i am trying to build the app. It is giving an error with exit status 137. the nodejs is latest so is the npm. I have checked the memory approx 700mb available.
New to ionic so now i cannot figure out the mistake.
Also rebuilded the node-sass. Nothing is working.
it takes too much time after sass started and then gets killed automatically.
Attaching the debug file
14 verbose stack Exit status 137
14 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:279:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:886:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid ionic-hello-world#
16 verbose cwd /home/ubuntu/files/ic2017app
17 verbose Linux 4.4.0-64-generic
18 verbose argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "ionic:build" "--" "--v2"
19 verbose node v6.10.1
20 verbose npm v4.4.4
21 error code ELIFECYCLE
22 error errno 137
23 error ionic-hello-world# ionic:build: `ionic-app-scripts build "--v2"`
23 error Exit status 137
24 error Failed at the ionic-hello-world# ionic:build script 'ionic-app-scripts build "--v2"'.
24 error Make sure you have the latest version of node.js and npm installed.
24 error If you do, this is most likely a problem with the ionic-hello-world package,
24 error not with npm itself.
24 error Tell the author that this fails on your system:
24 error ionic-app-scripts build "--v2"
24 error You can get information on how to open an issue for this project with:
24 error npm bugs ionic-hello-world
24 error Or if that isn't available, you can get their info via:
24 error npm owner ls ionic-hello-world
24 error There is likely additional logging output above.
25 verbose exit [ 137, true ]

700 mb is not enough. Recheck again. It must will be a memory overflow error.

Managing files in Android terminal

Using a terminal emulator in my android phone I accidentally copied /proc directory into another user directory. Now I want to delete the copy but I don't have the permissions to do so. I tried to change ownership and permissions to 777 but with no success. I am using Oneplus 2 and termux application. Any suggestions?
Edit:
The original /proc directory :
dr-xr-xr-x 459 root root 0 Jan 1 1970 proc/
it was copied to /.../line/proc:
Line:
drwxrwxrwx 4 u0_a45 u0_a45 4096 Oct 17 12:23 line/
Line/proc:
dr-xr-xr-x 52 u0_a45 u0_a45 4096 Jan 1 1970
proc/
The new proc directories are not removable:
rm -rf line/proc
rm: can't remove 'line/proc/12159/task/12247': Permission denied
...