http://developer.kde.org/~sewardj/valgrind-2.1.2.tar.bz2 Reproducible: Always Steps to Reproduce: Expected Results: Valgrind 2.1.2 ebuild.
luca, interested?
*** Bug 57847 has been marked as a duplicate of this bug. ***
I'll take a look this night
Created attachment 35880 [details] my used ebuild Hi, I'm using a linux-2.6.7-gentoo-r11 system with linux26-headers-2.6.7-r3 I made myself a nice valgrind 2.1.2 ebuild based on the 2.1.1 one... but ended up with the following problems during configuring: checking linux/mii.h usability... no checking linux/mii.h presence... yes configure: WARNING: linux/mii.h: present but cannot be compiled configure: WARNING: linux/mii.h: check for missing prerequisite headers? configure: WARNING: linux/mii.h: see the Autoconf documentation configure: WARNING: linux/mii.h: section "Present But Cannot Be Compiled" configure: WARNING: linux/mii.h: proceeding with the preprocessor's result configure: WARNING: linux/mii.h: in the future, the compiler will take precedence configure: WARNING: ## ------------------------------------------ ## configure: WARNING: ## Report this to the AC_PACKAGE_NAME lists. ## configure: WARNING: ## ------------------------------------------ ## checking for linux/mii.h... yes and compiling ended in: In file included from /usr/include/linux/mii.h:12, from vg_unsafe.h:75, from vg_syscalls.c:35: /usr/include/linux/if.h:95: error: redefinition of `struct ifmap' /usr/include/linux/if.h:131: error: redefinition of `struct ifreq' /usr/include/linux/if.h:181: error: redefinition of `struct ifconf' make[4]: *** [vg_syscalls.o] Error 1 I would presume this happens due to 2.6 linux headers being installed (but I need them cause I need epoll support)
I get these errors too.. Not sure what changed between 2.1.1 => 2.1.2, as 2.1.1 builds fine with 2.6.x headers.
tracked down the problem: coregrind/vg_unsafe.h includes #include <net/if.h> and #include <linux/mii.h> ( which includes <linux/if.h> ) for me removal of the first include fixed the problem.... hope this helps
Created attachment 35902 [details] patch to get valgrind 2.1.2 to compile
Created attachment 35903 [details] valgrind 2.1.2 ebuild
with attached ebuild and patch valgrind 2.1.2 compiles and runs fine for me on a first basic test
Committed in cvs a similar patch, thanks to everybody
why you kept the: filter-flags -fPIC in the ebuild? valgrind-2.1.2 should be PIC aware... (as valgrind-2.1.1-r1 was)
No. Take a look at gcc man page on what -fPIC does. And then: [root@karmic:~]# ldd /usr/bin/valgrind not a dynamic executable And read more about what valgrind does to debug your code.
I don't get it yet.... so either valgrind-2.1.1-r1 not striping fPIC is wrong (but why was there this fPIC specific patch and stripping of fPIC flag explictly removed from 2.1.1->2.1.1-r1 ?) or 2.1.2 should work with fPIC set, too... and after taking a look at the gcc man page I still don't know more than I did before. but keep one thing in mind.. valgrind is more than just the valgrind executable - it consists of some libraries itself. Why shouldn't they be build with fPIC ?
