Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 55498 - current valgrind CVS doesn't build on gentoo
Summary: current valgrind CVS doesn't build on gentoo
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-28 21:01 UTC by Matt Hargett
Modified: 2004-06-28 23:40 UTC (History)
0 users

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 Matt Hargett 2004-06-28 21:01:31 UTC
running the autogen.sh in valgrind's current CVS results in automake failures. updating automake doesn't help.

Reproducible: Always
Steps to Reproduce:
1.get current valgrind CVS
2. cd into valgrind src dir and run autogen.sh
3.

Actual Results:  
it requires version 1.6, but 1.4-p6 is reported: 
bash-2.05b$ ./autogen.sh 
running: aclocal 
running: autoheader 
running: automake -a 
Makefile.am:2: require version 1.6, but have 1.4-p6 
automake: coregrind/Makefile.am: not supported: source file `x86/ume_entry.S' 
is in subdirectory 
automake: coregrind/Makefile.am: not supported: source file `x86/ume_go.c' is 
in subdirectory 
coregrind/Makefile.am: valgrind_OBJECTS should not be defined 
automake: coregrind/Makefile.am: not supported: source file `x86/ume_entry.S' 
is in subdirectory 
automake: coregrind/Makefile.am: not supported: source file `x86/ume_go.c' is 
in subdirectory 
error: while running 'automake -a' 
 

Expected Results:  
should compile out of the box. this looks like a problem with gentoo's 
automake, but it might be valgrind CvS problems. upgrading to the latest 
automake ebuild doesn't help.
Comment 1 Mr. Bones. (RETIRED) gentoo-dev 2004-06-28 23:40:30 UTC
Sorry, we can't support cvs checkouts of valgrind code.  If the valgrind
ebuild doesn't work, go ahead and open a new bug.  Thanks.