Github messages for voidlinux
 help / color / mirror / Atom feed
From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] quickjs: compilation using `qjsc` fails with `gcc: error: /usr/lib/quickjs/libquickjs.a: No such file or directory`
Date: Sun, 07 Nov 2021 18:13:56 +0100	[thread overview]
Message-ID: <20211107171356.yE32B6N1LYVHR9hT_NxyLoPg0Y83nDZAUVV9Cbhdbu4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33935@inbox.vuxu.org>

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

Closed issue by ackalker on void-packages repository

https://github.com/void-linux/void-packages/issues/33935

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  Void 5.13.19_1 x86_64 GenuineIntel uptodate rrrrmdFFFFFFF
* package:  
  quickjs-2021.03.27_2

### Expected behavior

`qjsc <file.js>` should successfully compile a JavaScript script or module into a self-contained executable

### Actual behavior

Compilation fails with the following error:
```
gcc: error: /usr/lib/quickjs/libquickjs.a: No such file or directory
```

### Steps to reproduce the behavior

1. Ensure that both `quickjs` _and_ `quickjs-devel` packages are installed
2. Create a small JS file for testing: `echo 'console.log("Hello, world!")' > hello.js`
3. Try and compile using `qjsc`: `qjsc hello.js`

### Analysis

Neither the `quickjs` nor the `quickjs-devel` package contains the file mentioned in the error message. `quickjs-devel` does contain a file `/usr/lib/libquickjs.a` (note the missing intermediate directory `quickjs`).

      reply	other threads:[~2021-11-07 17:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-07 10:27 [ISSUE] quickjs: ackalker
2021-11-07 17:13 ` leahneukirchen [this message]

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=20211107171356.yE32B6N1LYVHR9hT_NxyLoPg0Y83nDZAUVV9Cbhdbu4@z \
    --to=leahneukirchen@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).