GNU bug report logs - #56467
vala command compiles files instead of running them

Previous Next

Package: guix;

Reported by: two <at> envs.net

Date: Sat, 9 Jul 2022 16:53:02 UTC

Severity: normal

Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 56467 in the body.
You can then email your comments to 56467 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#56467; Package guix. (Sat, 09 Jul 2022 16:53:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to two <at> envs.net:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Sat, 09 Jul 2022 16:53:03 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: two <at> envs.net
To: bug-guix <at> gnu.org
Subject: vala command compiles files instead of running them
Date: Sat, 09 Jul 2022 14:38:48 -0000
the bin/vala-0.54 shell script executes bin/valac-0.54 which executes bin/.valac-0.54-real.
it should execute bin/.vala-0.54-real instead.

expected (was the case before guix's update):
$ vala hello.vala
Hello, World!
$ ls
hello.vala

actual:
$ vala hello.vala
$ ls 
hello hello.vala
$ ./hello
Hello, World!




Information forwarded to bug-guix <at> gnu.org:
bug#56467; Package guix. (Fri, 15 Jul 2022 19:32:01 GMT) Full text and rfc822 format available.

Message #8 received at 56467 <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: two <at> envs.net
Cc: 56467 <at> debbugs.gnu.org
Subject: Re: bug#56467: vala command compiles files instead of running them
Date: Fri, 15 Jul 2022 15:31:05 -0400
Hi,

two <at> envs.net writes:

> the bin/vala-0.54 shell script executes bin/valac-0.54 which executes bin/.valac-0.54-real.
> it should execute bin/.vala-0.54-real instead.
>
> expected (was the case before guix's update):
> $ vala hello.vala
> Hello, World!
> $ ls
> hello.vala
>
> actual:
> $ vala hello.vala
> $ ls 
> hello hello.vala
> $ ./hello
> Hello, World!

That's indeed confusing, but it stems from the odd symbolic links layout
that upstream installs:

--8<---------------cut here---------------start------------->8---
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
--8<---------------cut here---------------end--------------->8---

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.

Do you have another build of vala to compare against, preferably at the
same version?

Thanks,

Maxim




Information forwarded to bug-guix <at> gnu.org:
bug#56467; Package guix. (Fri, 15 Jul 2022 19:36:01 GMT) Full text and rfc822 format available.

Message #11 received at 56467 <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: two <at> envs.net
Cc: 56467 <at> debbugs.gnu.org
Subject: Re: bug#56467: vala command compiles files instead of running them
Date: Fri, 15 Jul 2022 15:35:44 -0400
Hi,

Maxim Cournoyer <maxim.cournoyer <at> 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




Reply sent to Maxim Cournoyer <maxim.cournoyer <at> gmail.com>:
You have taken responsibility. (Fri, 15 Jul 2022 21:47:02 GMT) Full text and rfc822 format available.

Notification sent to two <at> envs.net:
bug acknowledged by developer. (Fri, 15 Jul 2022 21:47:02 GMT) Full text and rfc822 format available.

Message #16 received at 56467-done <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: two <at> envs.net
Cc: 56467-done <at> debbugs.gnu.org
Subject: Re: bug#56467: vala command compiles files instead of running them
Date: Fri, 15 Jul 2022 17:46:00 -0400
Hi,

Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:

> Hi,
>
> Maxim Cournoyer <maxim.cournoyer <at> 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.

Simple deleting the problematic wrap phase seems a good enough solution,
done in commit 154d270012.

I've also taken the opportunity to upgrade the package to version 0.56.2
and fixed a small usability issue (it would require the user to have
'cc' on their PATH).

Enjoy,

Maxim




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Sat, 13 Aug 2022 11:24:10 GMT) Full text and rfc822 format available.

This bug report was last modified 1 year and 247 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.