Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 310579 - dev-lang/vala fails to build valid code with USE="coverage" (tries to access build directory)
Summary: dev-lang/vala fails to build valid code with USE="coverage" (tries to access ...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords: InVCS
: 290003 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-03-21 17:56 UTC by Maciej Piechotka
Modified: 2010-12-20 22:39 UTC (History)
5 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Piechotka 2010-03-21 17:56:28 UTC
% valac --help       
Usage:
  valac [OPTION...] FILE... - Vala Compiler

Help Options:
  -?, --help                         Show help options

Application Options:
  --girdir=DIRECTORY...              Look for .gir files in DIRECTORY
  --vapidir=DIRECTORY...             Look for package bindings in DIRECTORY
  --pkg=PACKAGE...                   Include binding for PACKAGE
  --vapi=FILE                        Output VAPI file name
  --library=NAME                     Library name
  --gir=NAME-VERSION.gir             GObject-Introspection repository file name
  -b, --basedir=DIRECTORY            Base source directory
  -d, --directory=DIRECTORY          Output directory
  --version                          Display version number
  -C, --ccode                        Output C code
  -H, --header=FILE                  Output C header file
  --use-header                       Use C header file
  --includedir=DIRECTORY             Directory used to include the C header file
  -h, --internal-header=FILE         Output internal C header file
  --internal-vapi=FILE               Output vapi with internal api
  --symbols=FILE                     Output symbols file
  -c, --compile                      Compile but do not link
  -o, --output=FILE                  Place output in file FILE
  -g, --debug                        Produce debug information
  --thread                           Enable multithreading support
  --enable-mem-profiler              Enable GLib memory profiler
  -D, --define=SYMBOL...             Define SYMBOL
  --main=SYMBOL...                   Use SYMBOL as entry point
  --disable-assert                   Disable assertions
  --enable-checking                  Enable additional run-time checks
  --enable-deprecated                Enable deprecated features
  --enable-experimental              Enable experimental features
  --disable-warnings                 Disable warnings
  --enable-experimental-non-null     Enable experimental enhancements for non-null types
  --disable-dbus-transformation      Disable transformation of D-Bus member names
  --cc=COMMAND                       Use COMMAND as C compiler command
  -X, --Xcc=OPTION...                Pass OPTION to the C compiler
  --dump-tree=FILE                   Write code tree to FILE
  --save-temps                       Keep temporary files
  --profile=PROFILE                  Use the given profile instead of the default
  -q, --quiet                        Do not print messages to the console
  -v, --verbose                      Print additional messages to the console
  --target-glib=MAJOR.MINOR          Target version of glib for code generation

profiling:/var/tmp/paludis/dev-lang-vala-0.7.10:Cannot create directory
profiling:/var/tmp/paludis/dev-lang-vala-0.7.10/work/vala-0.7.10/compiler/valacompiler.gcda:Skip
(,,, over 16K of such messages)
profiling:/var/tmp/paludis/dev-lang-vala-0.7.10:Cannot create directory
profiling:/var/tmp/paludis/dev-lang-vala-0.7.10/work/vala-0.7.10/ccode/.libs/valaccodeparenthesizedexpression.gcda:Skip


Reproducible: Always
Comment 1 Marek Rogalski 2010-04-08 21:12:07 UTC
(In reply to comment #0)
On vala-0.8 same problem.
Comment 2 Steev Klimaszewski (RETIRED) gentoo-dev 2010-04-08 22:26:40 UTC
Are you trying to compile something *with* vala, or are you trying to build vala?
Comment 3 Maciej Piechotka 2010-04-08 22:33:43 UTC
(In reply to comment #2)
> Are you trying to compile something *with* vala, or are you trying to build
> vala?
> 

Something with vala. Or in the example given just 'vala --help'.
Comment 4 Thomas Raschbacher gentoo-dev 2010-04-09 11:18:44 UTC
Mine compiles but gives lots of funny profiling lines (only hello world program):

valac hello.vala
profiling:/var/tmp/portage/dev-lang/vala-0.7.10/work/vala-0.7.10/compiler/valacompiler.gcda:Cannot open
profiling:/var/tmp/portage/dev-lang/vala-0.7.10/work/vala-0.7.10/codegen/.libs/valaccodearraymodule.gcda:Cannot open
profiling:/var/tmp/portage/dev-lang/vala-0.7.10/work/vala-0.7.10/codegen/.libs/valaccodeassignmentmodule.gcda:Cannot open
profiling:/var/tmp/portage/dev-lang/vala-0.7.10/work/vala-0.7.10/codegen/.libs/valaccodebasemodule.gcda:Cannot open
profiling:/var/tmp/portage/dev-lang/vala-0.7.10/work/vala-0.7.10/codegen/.libs/valaccodecompiler.gcda:Cannot open
profiling:/var/tmp/portage/dev-lang/vala-0.7.10/work/vala-0.7.10/codegen/.libs/valaccodecontrolflowmodule.gcda:Cannot open
profiling:/var/tmp/portage/dev-lang/vala-0.7.10/work/vala-0.7.10/codegen/.libs/valaccodedeclarationspace.gcda:Cannot open
profiling:/var/tmp/portage/dev-lang/vala-0.7.10/work/vala-0.7.10/codegen/.libs/valaccodedelegatemodule.gcda:Cannot open
profiling:/var/tmp/portage/dev-lang/vala-0.7.10/work/vala-0.7.10/codegen/.libs/valaccodegenerator.gcda:Cannot open
profiling:/var/tmp/portage/dev-lang/vala-0.7.10/work/vala-0.7.10/codegen/.libs/valaccodememberaccessmodule.gcda:Cannot open
profiling:/var/tmp/portage/dev-lang/vala-0.7.10/work/vala-0.7.10/codegen/.libs/valaccodemethodcallmodule.gcda:Cannot open
..... <cut so comment fits but you get the idea> ...
lordvan@Desktop64X3 ~/Programming/vala $ ls
hello  hello.vala
lordvan@Desktop64X3 ~/Programming/vala $ ./hello
Hello, World
Comment 5 Thomas Raschbacher gentoo-dev 2010-04-09 11:33:50 UTC
oh USE="-coverage" does remove this issue .. seems to be only a 'bug' with the profiling / coverage stuff
Comment 6 Michał Lipski 2010-05-08 10:37:34 UTC
Confirmed.
Comment 7 Maksim 'max_posedon' Melnikau 2010-05-16 11:49:41 UTC
also --enable-coverage brokes cross compilation with vala
Comment 8 Arun Raghavan (RETIRED) gentoo-dev 2010-07-21 09:48:17 UTC
Is the coverage stuff only meant for the Vala developers? If yes, maybe we should drop it and the USE flag.
Comment 9 Daniel Gryniewicz (RETIRED) gentoo-dev 2010-07-21 15:20:14 UTC
The coverage looks like it does coverage for the unit tests on vala itself.  It generates a valac build with, among other things, -lgcov, so it's probably a bad thing to have enabled in portage.
Comment 10 Gilles Dartiguelongue (RETIRED) gentoo-dev 2010-09-29 12:11:07 UTC
Maybe we should implement an out of tree build like what was done for dbus ?
Comment 11 Gilles Dartiguelongue (RETIRED) gentoo-dev 2010-09-29 12:12:02 UTC
*** Bug 290003 has been marked as a duplicate of this bug. ***
Comment 12 Steffen Schaumburg 2010-10-25 23:37:47 UTC
I also had this bug when trying to compile my own vala code. However, it did seem to run just fine (tho it was only a simple hello world).
Comment 13 Gilles Dartiguelongue (RETIRED) gentoo-dev 2010-12-20 22:39:01 UTC
+  20 Dec 2010; Gilles Dartiguelongue <eva@gentoo.org> vala-0.8.1.ebuild,
+  vala-0.9.3.ebuild, -vala-0.9.8.ebuild, -vala-0.10.0.ebuild,
+  vala-0.10.1.ebuild, -vala-0.11.0.ebuild, -vala-0.11.1.ebuild,
+  vala-0.11.2.ebuild:
+  Raise glib dependency for tests for slot :0.10, bug #330527. Drop coverage
+  handling, it is broken and doesn't bring much for now, bug #310579.

Thanks for reporting.