The debian (armhf) package created using source doesn't work on Beaglebone #5964

sakthivel-axim · 2023-01-12T12:50:02Z

sakthivel-axim
Jan 12, 2023

I have followed the below steps to generate the armhf package,

$  git clone [email protected]:coder/code-server.git 
$ git checkout  v4.9.1
$ quilt push -a
$ yarn
$ VERSION="4.9.1" yarn build
$ VERSION=4.9.1 yarn build:vscode
$ yarn release
$ yarn release:standalone
$ yarn test:integration
$ VERSION="4.9.1" yarn package armhf

$ ls release-packages/
        code-server_4.9.1_armhf.deb  code-server-4.9.1-armhf.rpm  code-server-4.9.1-linux-armhf.tar.gz

Error in Beaglebone terminal

root@beaglebone:/home/debian# code-server --version
/usr/lib/code-server/bin/code-server: 28: exec: /usr/lib/code-server/lib/node: Exec format error
root@beaglebone:/home/debian#

Answered by sakthivel-axim

Feb 13, 2023

Hi @im-coder-lg @code-asher , I hvve followed the commands mentioned in release.yaml,. Facing issue in executing code-server in beaglebone with generated package.

The following steps followed to build .deb package as per release.yaml,

$ export AR=arm-linux-gnueabihf-ar 
$ export CC=arm-linux-gnueabihf-gcc 
$ export CXX=arm-linux-gnueabihf-g++ 
$ export LINK=arm-linux-gnueabihf-g++ 
$ export NPM_CONFIG_ARCH=armv7l 
$ export NODE_VERSION=v16.15.1 

$ sudo apt update 
$ sudo apt install g++-arm-linux-gnueabihf 

$ quilt push -a 
$ yarn 
$ VERSION=4.9.1 yarn build 
$ VERSION=4.9.1 yarn build:vscode 

$ KEEP_MODULES=1 yarn release 
$ yarn release:standalone 
$ yarn test:integration 

$ wget [h…

View full answer

im-coder-lg · 2023-01-12T17:51:35Z

im-coder-lg
Jan 12, 2023

I wonder if something is wrong with your commands. Did you check the documentation? I left armhf long ago and would not like to get back into 32-bit, but this intrigues me.

0 replies

im-coder-lg · 2023-01-12T17:55:24Z

im-coder-lg
Jan 12, 2023

Have you checked this thoroughly: https://coder.com/docs/code-server/latest/CONTRIBUTING#build

I think that could be the solution? I don't know, honestly my computer is not powerful to build code-server.

7 replies

im-coder-lg Jan 26, 2023

Hmm... as @jsjoeio sometimes said when these things occurred, it could be glibc. Have you tried using Jammy Jellyfish for this?

code-asher Jan 27, 2023
Maintainer

Also, is the Ubuntu environment where you are building this also armv7l? If not you will need to compile on an armv7l machine or set up cross-compilation.

sakthivel-axim Feb 1, 2023
Author

Thanks @code-asher. The Ubuntu machine's architecture is amd64 where I create the packages. I thought , the cross-compilation was taken care by this command itself VERSION="4.9.1" yarn package armv7l. I will do the compilation in Debian machine. And Please share, if any steps available for setting up cross compilation already.

code-asher Feb 6, 2023
Maintainer

Ahhhh yeah I see how that is confusing. Node requires some extra things in order to do cross-compilation unfortunately. I will say more in the thread below.

code-asher Feb 6, 2023
Maintainer

I bet we could add some checks to the script in order to detect this and print instructions on how to provide the right environment.

sakthivel-axim · 2023-02-02T08:22:24Z

sakthivel-axim
Feb 2, 2023
Author

Hi @im-coder-lg , @code-asher , Could you please share the steps for cross-compilation. I couldn't find the steps for cross compilation in the code-server documentation.

7 replies

sakthivel-axim Feb 6, 2023
Author

Thanks @im-coder-lg , @code-asher. I would like to know, how code-server generating packages for armhf environments ?

https://github.com/coder/code-server/releases

im-coder-lg Feb 6, 2023

Huh. The builds are done via the GitHub Actions workflow. To be precise, this is the file: release.yaml

You can use the Find tool in your browser to find your specific answer. Hope it helps :)

im-coder-lg Feb 6, 2023

Wow there is so much of notes from maintainers, @sakthivel-axim I hope it helps you build ARM standalones.

code-asher Feb 6, 2023
Maintainer

Sorry all, I was out of the office last week.

@im-coder-lg has it right, the release.yaml is the file to look at. The comment here might help.

sakthivel-axim Feb 7, 2023
Author

Thanks @im-coder-lg , @code-asher, I will try build with steps mentioned.

sakthivel-axim · 2023-02-13T10:50:15Z

sakthivel-axim
Feb 13, 2023
Author

Hi @im-coder-lg @code-asher , I hvve followed the commands mentioned in release.yaml,. Facing issue in executing code-server in beaglebone with generated package.

The following steps followed to build .deb package as per release.yaml,

$ export AR=arm-linux-gnueabihf-ar 
$ export CC=arm-linux-gnueabihf-gcc 
$ export CXX=arm-linux-gnueabihf-g++ 
$ export LINK=arm-linux-gnueabihf-g++ 
$ export NPM_CONFIG_ARCH=armv7l 
$ export NODE_VERSION=v16.15.1 

$ sudo apt update 
$ sudo apt install g++-arm-linux-gnueabihf 

$ quilt push -a 
$ yarn 
$ VERSION=4.9.1 yarn build 
$ VERSION=4.9.1 yarn build:vscode 

$ KEEP_MODULES=1 yarn release 
$ yarn release:standalone 
$ yarn test:integration 

$ wget [https://nodejs.org/dist/${NODE_VERSION}/node-${NODE_VERSION}-linux-${NPM_CONFIG_ARCH}.tar.xz](https://nodejs.org/dist/$%7BNODE_VERSION%7D/node-$%7BNODE_VERSION%7D-linux-$%7BNPM_CONFIG_ARCH%7D.tar.xz) 

$ tar -xf node-${NODE_VERSION}-linux-${NPM_CONFIG_ARCH}.tar.xz node-${NODE_VERSION}-linux-${NPM_CONFIG_ARCH}/bin/node --strip-components=2 

$ mv ./node ./release-standalone/lib/node  

$ export VERSION=4.9.1 
$ yarn package ${NPM_CONFIG_ARCH}

I'm using 64-bit machine to generated package for 32-bit Beaglebone. Able to generate package with above commands and installed in Beabglebone. But, failed to execute and showing following error, Looks something I miss here. Could please let me know, any idea on this issue.

root@beaglebone:/home/debian# dpkg -i code-server_4.9.1_armhf.deb 
Selecting previously unselected package code-server.
(Reading database ... 73119 files and directories currently installed.)
Preparing to unpack code-server_4.9.1_armhf.deb ...
Unpacking code-server (4.9.1) ...
Setting up code-server (4.9.1) ...
root@beaglebone:/home/debian# code-server --help
node:internal/modules/cjs/loader:1249
  return process.dlopen(module, path.toNamespacedPath(filename));
                 ^

Error: /usr/lib/code-server/node_modules/argon2/lib/binding/napi-v3/argon2.node: wrong ELF class: ELFCLASS64
    at Object.Module._extensions..node (node:internal/modules/cjs/loader:1249:18)
    at Module.load (node:internal/modules/cjs/loader:1043:32)
    at Function.Module._load (node:internal/modules/cjs/loader:878:12)
    at Module.require (node:internal/modules/cjs/loader:1067:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at Object.<anonymous> (/usr/lib/code-server/node_modules/argon2/argon2.js:6:25)
    at Module._compile (node:internal/modules/cjs/loader:1165:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1219:10)
    at Module.load (node:internal/modules/cjs/loader:1043:32)
    at Function.Module._load (node:internal/modules/cjs/loader:878:12) {
  code: 'ERR_DLOPEN_FAILED'
}
root@beaglebone:/home/debian#

6 replies

code-asher Feb 13, 2023
Maintainer

Although we set npm_config_build_from_source=true in the standalone release script. Possibly because you have KEEP_MODULES=1 it is using the existing module which did not build from source and used a prebuild.

So maybe add export npm_config_build_from_source=true to your script or remove KEEP_MODULES=1.

sakthivel-axim Feb 15, 2023
Author

Great. It works. Thanks @code-asher.

I just removed KEEP_MODULES=1 and followed steps which I have mentioned above. Able to create Package, installed in Beaglebone and it's working.

Observed Two issues,

code-server version is not displaying properly. It displays 0.0.0 instead of 4.9.1

    root@beaglebone:/home/debian# code-server --version
    0.0.0 afc7a0ea98ed10a36103fe1079075d230ca50148 with Code 1.73.1

Got an error while building release:standalone, still standalone package got created. Error in keytar module, does it impact anything or any idea on this ?

code-server((v4.9.1))$ yarn release:standalone
yarn run v1.22.18
$ ./ci/build/build-standalone-release.sh

> [email protected] postinstall
> sh ./postinstall.sh

curl: (22) The requested URL returned error: 404 
Failed to download cloud agent; --link will not work
Installing Code dependencies...
User agent: yarn/1.22.18 npm/? node/v16.15.1 linux x64
warning npm-shrinkwrap.json found. This will not be updated or respected. See https://yarnpkg.com/en/docs/migrating-from-npm for more information.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning "@microsoft/1ds-core-js > @microsoft/[email protected]" has unmet peer dependency "tslib@*".
[4/4] Building fresh packages...
[1/6] ⠐ @parcel/watcher
[2/6] ⠐ @vscode/ripgrep
[3/6] ⠐ keytar
[6/6] ⠐ spdlog
error /var/www/IDEs/code-server/release-standalone/lib/vscode/node_modules/keytar: Command failed.
Exit code: 1
Command: prebuild-install || npm run build
Arguments: 
Directory: /var/www/IDEs/code-server/release-standalone/lib/vscode/node_modules/keytar
Output:
> [email protected] build
> node-gyp rebuild

gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp info find Python using Python version 3.6.9 found at "/usr/bin/python3"
gyp info spawn /usr/bin/python3
gyp info spawn args [
gyp info spawn args   '/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/var/www/IDEs/code-server/release-standalone/lib/vscode/node_modules/keytar/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/usr/local/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/test/.cache/node-gyp/16.15.1/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/home/test/.cache/node-gyp/16.15.1',
gyp info spawn args   '-Dnode_gyp_dir=/usr/local/lib/node_modules/npm/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/home/test/.cache/node-gyp/16.15.1/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/var/www/IDEs/code-server/release-standalone/lib/vscode/node_modules/keytar',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.'
gyp info spawn args ]
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make: Entering directory '/var/www/IDEs/code-server/release-standalone/lib/vscode/node_modules/keytar/build'
  CXX(target) Release/obj.target/keytar/src/async.o
  CXX(target) Release/obj.target/keytar/src/main.o
  CXX(target) Release/obj.target/keytar/src/keytar_posix.o
In file included from /usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9:0,
                 from /usr/include/glib-2.0/glib/gtypes.h:32,
                 from /usr/include/glib-2.0/glib/galloca.h:32,
                 from /usr/include/glib-2.0/glib.h:30,
                 from /usr/include/libsecret-1/libsecret/secret.h:18,
                 from ../src/keytar_posix.cc:6:
/usr/include/glib-2.0/glib/gtypes.h: In function ‘gboolean _GLIB_CHECKED_ADD_U64(guint64*, guint64, guint64)’:
/usr/include/glib-2.0/glib/gmacros.h:145:29: error: size of array ‘_GStaticAssertCompileTimeAssertion_0’ is negative
   __attribute__((__unused__))
                             ^
/usr/include/glib-2.0/glib/gmacros.h:241:120: note: in expansion of macro ‘G_GNUC_UNUSED’
 #define G_STATIC_ASSERT(expr) typedef char G_PASTE (_GStaticAssertCompileTimeAssertion_, __COUNTER__)[(expr) ? 1 : -1] G_GNUC_UNUSED
                                                                                                                        ^~~~~~~~~~~~~
/usr/include/glib-2.0/glib/gtypes.h:423:3: note: in expansion of macro ‘G_STATIC_ASSERT’
   G_STATIC_ASSERT(sizeof (unsigned long long) == sizeof (guint64));
   ^~~~~~~~~~~~~~~
keytar.target.mk:119: recipe for target 'Release/obj.target/keytar/src/keytar_posix.o' failed
make: *** [Release/obj.target/keytar/src/keytar_posix.o] Error 1
make: Leaving directory '/var/www/IDEs/code-server/release-standalone/lib/vscode/node_modules/keytar/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (node:events:527:28)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
gyp ERR! System Linux 5.4.0-137-generic
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /var/www/IDEs/code-server/release-standalone/lib/vscode/node_modules/keytar




User agent: yarn/1.22.18 npm/? node/v16.15.1 linux x64
warning npm-shrinkwrap.json found. This will not be updated or respected. See https://yarnpkg.com/en/docs/migrating-from-npm for more information.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
warning Your current version of Yarn is out of date. The latest version is "1.22.19", while you're on "1.22.18".
info To upgrade, run the following command:
$ curl --compressed -o- -L https://yarnpkg.com/install.sh | bash
$ node ./postinstall.mjs
Removed /var/www/IDEs/code-server/release-standalone/lib/vscode/extensions/node_modules/typescript/AUTHORS.md
Removed /var/www/IDEs/code-server/release-standalone/lib/vscode/extensions/node_modules/typescript/CODE_OF_CONDUCT.md
Removed /var/www/IDEs/code-server/release-standalone/lib/vscode/extensions/node_modules/typescript/CopyrightNotice.txt
Removed /var/www/IDEs/code-server/release-standalone/lib/vscode/extensions/node_modules/typescript/LICENSE.txt
Removed /var/www/IDEs/code-server/release-standalone/lib/vscode/extensions/node_modules/typescript/README.md
Removed /var/www/IDEs/code-server/release-standalone/lib/vscode/extensions/node_modules/typescript/SECURITY.md
Removed /var/www/IDEs/code-server/release-standalone/lib/vscode/extensions/node_modules/typescript/ThirdPartyNoticeText.txt
Removed /var/www/IDEs/code-server/release-standalone/lib/vscode/extensions/node_modules/typescript/bin
Removed /var/www/IDEs/code-server/release-standalone/lib/vscode/extensions/node_modules/typescript/loc
removed '/var/www/IDEs/code-server/release-standalone/lib/vscode/extensions/node_modules/typescript/lib/tsc.js'
removed '/var/www/IDEs/code-server/release-standalone/lib/vscode/extensions/node_modules/typescript/lib/tsserverlibrary.d.ts'
removed '/var/www/IDEs/code-server/release-standalone/lib/vscode/extensions/node_modules/typescript/lib/tsserverlibrary.js'
removed '/var/www/IDEs/code-server/release-standalone/lib/vscode/extensions/node_modules/typescript/lib/typescriptServices.d.ts'
removed '/var/www/IDEs/code-server/release-standalone/lib/vscode/extensions/node_modules/typescript/lib/typescriptServices.js'

code-asher Feb 16, 2023
Maintainer

We actually update the version in the GitHub workflow.

code-server/.github/workflows/release.yaml

Lines 303 to 311 in e0ece19

    
                   run: | 
        
                     echo "Updating version in root package.json" 
        
                     npm version --prefix release "$VERSION" 
        
                     echo "Updating version in lib/vscode/product.json" 
        
                     tmp=$(mktemp)  
        
                     jq ".codeServerVersion = \"$VERSION\"" release/lib/vscode/product.json > "$tmp" && mv "$tmp" release/lib/vscode/product.json 
        
                     # Ensure it has the same permissions as before 
        
                     chmod 644 release/lib/vscode/product.json

Maybe we can think about moving this to the package script although we also need it for the NPM publish step which does not use the package script.

Keytar seems to always fail on arm but I have no idea why unfortunately. The consequence is that secret storage will not work. So if you log in with GitHub for example the next time you restart code-server you will have to log in again.

code-asher Feb 16, 2023
Maintainer

One possible workaround for secret storage is to replace it: #5072 (comment)

sakthivel-axim Mar 1, 2023
Author

Thanks @code-asher .

THe code server version displays properly after changing the version in package.json.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

The debian (armhf) package created using source doesn't work on Beaglebone #5964

{{title}}

Replies: 4 comments 20 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

The debian (armhf) package created using source doesn't work on Beaglebone #5964

sakthivel-axim Jan 12, 2023

Replies: 4 comments · 20 replies

im-coder-lg Jan 12, 2023

im-coder-lg Jan 12, 2023

im-coder-lg Jan 26, 2023

code-asher Jan 27, 2023 Maintainer

sakthivel-axim Feb 1, 2023 Author

code-asher Feb 6, 2023 Maintainer

code-asher Feb 6, 2023 Maintainer

sakthivel-axim Feb 2, 2023 Author

sakthivel-axim Feb 6, 2023 Author

im-coder-lg Feb 6, 2023

im-coder-lg Feb 6, 2023

code-asher Feb 6, 2023 Maintainer

sakthivel-axim Feb 7, 2023 Author

sakthivel-axim Feb 13, 2023 Author

code-asher Feb 13, 2023 Maintainer

sakthivel-axim Feb 15, 2023 Author

code-asher Feb 16, 2023 Maintainer

code-asher Feb 16, 2023 Maintainer

sakthivel-axim Mar 1, 2023 Author

sakthivel-axim
Jan 12, 2023

Replies: 4 comments 20 replies

im-coder-lg
Jan 12, 2023

im-coder-lg
Jan 12, 2023

code-asher Jan 27, 2023
Maintainer

sakthivel-axim Feb 1, 2023
Author

code-asher Feb 6, 2023
Maintainer

code-asher Feb 6, 2023
Maintainer

sakthivel-axim
Feb 2, 2023
Author

sakthivel-axim Feb 6, 2023
Author

code-asher Feb 6, 2023
Maintainer

sakthivel-axim Feb 7, 2023
Author

sakthivel-axim
Feb 13, 2023
Author

code-asher Feb 13, 2023
Maintainer

sakthivel-axim Feb 15, 2023
Author

code-asher Feb 16, 2023
Maintainer

code-asher Feb 16, 2023
Maintainer

sakthivel-axim Mar 1, 2023
Author