Summary: | valgrind-2.2.0 Makefile generation problem $(prefix) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Keef Aragon <keef> |
Component: | New packages | Assignee: | Maurice van der Pot (RETIRED) <griffon26> |
Status: | VERIFIED NEEDINFO | ||
Severity: | normal | CC: | f5d8fd51ed1e804c9e8d0357e8614e0493b06e96, lu_zero |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Keef Aragon
2004-09-15 11:48:22 UTC
May well have misidentified cause of bad path. When running make manually without portage, the path is set up fine... perhaps in a USE flag? emerges and runs fine for me, using it since this versions ebuild is out. just emerged again just to be sure I'm using latest ebuild. so I have no clue what might be going wrong for you... I'm going to mark it worksforme, reopen if you experience and can reproduce the issue I resynced and re-emerged valgrind today... same thing: valgrind: failed to load /var/tmp/portage/valgrind-2.2.0/image//usr/lib/valgrind/stage2: No such file or directory somewhere in the build a static path of /var/tmp/portage/valgrind-2.2.0/image/ is getting prepended onto a build parameter as that is there the files are going temporarily. Could it be a bug which only arises with a certain USE flag? Could you provide the invocation command line of configure? You can get to it by interrupting the emerge and checking near the top of the following file: /var/tmp/portage/valgrind-2.2.0/work/valgrind-2.2.0/config.log I really need more info to do something about this. Not sure what the issue was but since 2.2.0-r1, this no longer seems to be an issue. |