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

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#56467: closed (vala command compiles files instead of running
 them)
Date: Fri, 15 Jul 2022 21:47:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Fri, 15 Jul 2022 17:46:00 -0400
with message-id <871qumuk13.fsf <at> gmail.com>
and subject line Re: bug#56467: vala command compiles files instead of running them
has caused the debbugs.gnu.org bug report #56467,
regarding vala command compiles files instead of running them
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
56467: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56467
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

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!

[Message part 3 (message/rfc822, inline)]

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

Previous Next

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