From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: two@envs.net
Cc: 56467@debbugs.gnu.org
Subject: bug#56467: vala command compiles files instead of running them
Date: Fri, 15 Jul 2022 15:35:44 -0400 [thread overview]
Message-ID: <87edymuq27.fsf@gmail.com> (raw)
In-Reply-To: <87ilnyuq9y.fsf@gmail.com> (Maxim Cournoyer's message of "Fri, 15 Jul 2022 15:31:05 -0400")
Hi,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
[...]
> lrwxrwxrwx 1 nixbld nixbld 9 Jul 15 19:18 vala -> vala-0.54
> lrwxrwxrwx 1 nixbld nixbld 10 Jul 15 19:18 vala-0.54 -> valac-0.54
> lrwxrwxrwx 1 nixbld nixbld 10 Jul 15 19:18 valac -> valac-0.54
> -rwxr-xr-x 1 nixbld nixbld 147248 Jul 15 19:18 valac-0.54
> lrwxrwxrwx 1 nixbld nixbld 12 Jul 15 19:18 valadoc -> valadoc-0.54
> -rwxr-xr-x 1 nixbld nixbld 451032 Jul 15 19:18 valadoc-0.54
> lrwxrwxrwx 1 nixbld nixbld 24 Jul 15 19:18 vala-gen-introspect -> vala-gen-introspect-0.54
> -rwxr-xr-x 1 nixbld nixbld 1067 Jul 15 19:18 vala-gen-introspect-0.54
> lrwxrwxrwx 1 nixbld nixbld 12 Jul 15 19:18 vapigen -> vapigen-0.54
> -rwxr-xr-x 1 nixbld nixbld 720128 Jul 15 19:18 vapigen-0.54
>
> If you read attentively, you'll see there's no proper 'vala' binary,
> vala, vala-0.54 and valac are all symbolic links to valac-0.54, which is
> the compiler.
>
> Perhaps upstream changed the behavior? Or it could be that they use
> arg0 (the program name) to infer different behaviors, which gets mangled
> by our wrappers.
I just confirmed the later in #vala on the gnome IRC server. Let's see
what we can do.
Maxim
next prev parent reply other threads:[~2022-07-15 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 14:38 bug#56467: vala command compiles files instead of running them two--- via Bug reports for GNU Guix
2022-07-15 19:31 ` Maxim Cournoyer
2022-07-15 19:35 ` Maxim Cournoyer [this message]
2022-07-15 21:46 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edymuq27.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=56467@debbugs.gnu.org \
--cc=two@envs.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).