Github messages for voidlinux
 help / color / mirror / Atom feed
From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: chronograf: update to 1.10.0, makedepends on nodejs, python3
Date: Wed, 15 Mar 2023 00:06:03 +0100	[thread overview]
Message-ID: <20230314230603.7vfVs2sV8ewq6vRL_2txRWdnlvp-homu_19q1gpRZLI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42644@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]

New comment by dkwo on void-packages repository

https://github.com/void-linux/void-packages/pull/42644#issuecomment-1468984146

Comment:
still trying to fix cross compilation: I think I made some progress, now stuck at
```
yarn run v1.22.18
$ APP_VERSION=$npm_package_version GIT_SHA=$(git rev-parse HEAD) parcel build --log-level error
fatal: not a git repository (or any of the parent directories): .git
Error: Error relocating /builddir/chronograf-1.10.0/node_modules/@parcel/watcher/build/Release/watcher.node: unsupported relocation type 1026
    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 (/builddir/chronograf-1.10.0/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
    at load (/builddir/chronograf-1.10.0/node_modules/node-gyp-build/index.js:22:10)
    at Object.<anonymous> (/builddir/chronograf-1.10.0/node_modules/@parcel/watcher/index.js:1:104)
    at Module._compile (/builddir/chronograf-1.10.0/node_modules/v8-compile-cache/v8-compile-cache.js:192:30)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1219:10)
    at Module.load (node:internal/modules/cjs/loader:1043:32) {
  code: 'ERR_DLOPEN_FAILED'
}
error Command failed with exit code 1.
```

  parent reply	other threads:[~2023-03-14 23:06 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07 16:49 [PR PATCH] " dkwo
2023-03-07 16:49 ` dkwo
2023-03-07 17:51 ` dkwo
2023-03-07 18:07 ` [PR PATCH] [Updated] " dkwo
2023-03-07 18:09 ` dkwo
2023-03-08 18:11 ` [PR REVIEW] " paper42
2023-03-08 21:23 ` dkwo
2023-03-08 21:24 ` dkwo
2023-03-09 18:57 ` paper42
2023-03-09 18:59 ` paper42
2023-03-09 18:59 ` paper42
2023-03-09 20:37 ` dkwo
2023-03-09 20:37 ` dkwo
2023-03-09 20:38 ` [PR PATCH] [Updated] " dkwo
2023-03-09 20:47 ` dkwo
2023-03-09 21:15 ` dkwo
2023-03-09 21:33 ` dkwo
2023-03-10 16:36 ` dkwo
2023-03-10 20:17 ` [PR PATCH] [Updated] " dkwo
2023-03-14 23:00 ` dkwo
2023-03-14 23:06 ` dkwo [this message]
2023-03-15 18:13 ` dkwo
2023-03-15 18:24 ` dkwo
2023-03-15 18:26 ` dkwo
2023-03-15 21:43 ` dkwo
2023-03-15 21:48 ` dkwo
2023-03-16 22:46 ` [PR PATCH] [Updated] " dkwo
2023-04-17 20:04 ` dkwo
2023-04-24 15:46 ` dkwo
2023-04-24 15:48 ` dkwo
2023-04-24 18:14 ` [PR PATCH] [Updated] " dkwo
2023-04-24 21:10 ` dkwo
2023-04-26 14:12 ` dkwo
2023-04-26 15:33 ` dkwo
2023-05-10 14:47 ` dkwo
2023-05-11 14:35 ` [PR PATCH] [Updated] " dkwo
2023-05-11 14:41 ` dkwo
2023-05-11 14:58 ` [PR PATCH] [Updated] " dkwo
2023-06-02 19:02 ` [PR PATCH] [Merged]: " paper42
2023-06-02 19:02 ` paper42

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230314230603.7vfVs2sV8ewq6vRL_2txRWdnlvp-homu_19q1gpRZLI@z \
    --to=dkwo@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).