After upgrading vala to version 0.7.7 (newest available) compiler gives set of warinings about missing files. It looks like the files are not correctly installed in the system. I've compiled simple hello world example from: http://live.gnome.org/Vala/Tutorial and get: $ valac hello.vala profiling:/var/tmp/portage/dev-lang/vala-0.7.7/work/vala-0.7.7/compiler/valacompiler.gcda:Cannot open profiling:/var/tmp/portage/dev-lang/vala-0.7.7/work/vala-0.7.7/codegen/.libs/valaccodearraymodule.gcda:Cannot open anyway binary file is created and is working Reproducible: Always
Created attachment 207814 [details] Full valac hello.vala log
vala-0.7 is a development branch and as such is a moving target. It is most likely that the example is simply outdated.
1. Same output is while compiling _any_ vala code. 2. I believe that compiler should not look for any files in /var/tmp/portage/... But of course maybe I'm wrong.
emerge -pv vala ? (to check supports)
Created attachment 208045 [details] emerge --info # emerge -pv vala These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] dev-lang/vala-0.7.7 USE="coverage vapigen -test" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB I'm attaching emerge --info just in case. Most of the system is STABLE Gentoo x86
I went to the wiki page, copy/pasted the hello world code and it builds and runs just fine here. Could you rebuild vala and see if that fixes the problem ?
(In reply to comment #6) > I went to the wiki page, copy/pasted the hello world code and it builds and > runs just fine here. Could you rebuild vala and see if that fixes the problem ? Did you compile the example as a user or root? I've just reemerged vala-0.7.7 here, compiled example and there is no change. Compilation works fine, executable is working but there is strange output like in attached file. But if I'm compiling same code as root there is NO strange "error" output. So please if you compiled example as root try to do same as unprivileged user.
I compiled with my regular user. Please note that I never built vala stuff with that user previously so maybe if there is some patch cache or whatever.
(In reply to comment #8) > I compiled with my regular user. Please note that I never built vala stuff with > that user previously so maybe if there is some patch cache or whatever. Strange, very strange. What i did now: emerge -aC vala valide emerge -a --depclean rm -rf /var/tmp/portage/dev-lang/vala-0.7.7/ rm -rf /var/tmp/portage/dev-util/valide-0.5.1/ emerge -avD vala same problem, valac produces working binary AND few kilobytes of warnings about write privileges emerge -avD =dev-lang/vala-0.7.4 it's the version i had here before, and NO PROBLEMS AT ALL. emerge -avu vala back to old problem... What i did than, i've installed vala-0.7.7 on FRESHLY installed Gentoo on new computer (eeeBox for my office). And there I have the same error output about.
(In reply to comment #8) > I compiled with my regular user. Please note that I never built vala stuff with > that user previously so maybe if there is some patch cache or whatever. Can you please tell me if your user is in portage group, and maybe you have read/write access to directory and files(!) in directories: /var/tmp/portage/dev-lang/vala-0.7.7/work/vala-0.7.7/codegen/.libs/ /var/tmp/portage/dev-lang/vala-0.7.7/work/vala-0.7.7/vala/.libs/ /var/tmp/portage/dev-lang/vala-0.7.7/work/vala-0.7.7/gee/.libs/ /var/tmp/portage/dev-lang/vala-0.7.7/work/vala-0.7.7/ccode/.libs/ Maybe if your user is in portage group, and you emerged vala as this user you can modify this files, and this way you have no strange errors/warnings.
my user is indeed in portage group, but those files (/var/tmp/...) do not exist after successful build obviously.
OK one step forward. Once again i've unmerged vala and valide than: 1. # emerge vala 2. directory /var/tmp/portage/dev-lang/vala-0.7.7/ does NOT exist 3. # emerge valide 4. directory /var/tmp/portage/dev-lang/vala-0.7.7/ owned by root is created. valide is written in vala, and root is the user who compiled it using valac 5. # rm -rf /var/tmp/portage/dev-lang/vala-0.7.7/ 6. now i've compiled hello.vala as regular user 7. directory is created now the owner of it is my user, and of course there is no warnings/errors while using valac So now the questions are: Why this (temporary?) folder is created in /var/tmp/portage not just /tmp/? Is it a bug of vala (upstream)/portage (ebuild)? We have to remember that upstream probably don't know about /var/tmp/portage/ directory ;-) Why compiler does not clean this directory after compilation, and this is probably upstream bug.
*** Bug 297875 has been marked as a duplicate of this bug. ***
I don't see this bug as fixed or resolved. Please reopen it.
If I recompile vala with USE="-coverage", the bug goes away. Please remove "+coverage" from IUSE, as it only breaks things.
I can confirm the errors/warnings do not occur anymore after recompiling without coverage use flag. Probably, removing the flag altogether should be helpful if it doesn't work anyway.
reopening to set proper status.
*** This bug has been marked as a duplicate of bug 310579 ***
