From: astralchan <astralchan@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: deno-1.32.3
Date: Wed, 12 Apr 2023 13:04:29 +0200 [thread overview]
Message-ID: <20230412110429.MmQKoMNueFk5_DARj-rhCgEfto9I-xfDLRfwRuYKdas@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43368@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
New comment by astralchan on void-packages repository
https://github.com/void-linux/void-packages/pull/43368#issuecomment-1505080638
Comment:
I added a `gn` package for making the ninja build rules. `deno` should get that package.
Current build error log:
```
--- stderr
thread 'main' panicked at 'Path doesn't exist: "/builddir/deno-1.32.3/target/release/gn_out/../../../../../host/cargo/registry/src/index.crates.io-6f17d22bba15001f/v8-0.68.0/v8/tools/builtins-pgo/x64.profile"', /host/cargo/registry/src/index.crates.io-6f17d22bba15001f/v8-0.68.0/build.rs:726:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
=> ERROR: deno-1.32.3_1: do_build: '${make_cmd} build --release --target ${RUST_TARGET} ${configure_args}' exited with 101
=> ERROR: in do_build() at common/build-style/cargo.sh:8
```
next prev parent reply other threads:[~2023-04-12 11:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 4:43 [PR PATCH] " astralchan
2023-04-10 5:30 ` icp1994
2023-04-10 5:44 ` icp1994
2023-04-10 7:34 ` [PR PATCH] [Updated] " astralchan
2023-04-10 7:34 ` astralchan
2023-04-10 11:17 ` astralchan
2023-04-10 13:03 ` astralchan
2023-04-12 10:34 ` [PR PATCH] [Updated] " astralchan
2023-04-12 10:44 ` astralchan
2023-04-12 11:02 ` astralchan
2023-04-12 11:04 ` astralchan [this message]
2023-07-12 2:06 ` github-actions
2023-07-27 1:47 ` [PR PATCH] [Closed]: " github-actions
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=20230412110429.MmQKoMNueFk5_DARj-rhCgEfto9I-xfDLRfwRuYKdas@z \
--to=astralchan@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).