On Sun, 2018-05-20 at 14:49 -0400, Jeffrey Walton wrote: > I'm working on Fedora 27 x86_64 from Master trying to sidestep > https://bugs.kde.org/show_bug.cgi?id=387773. > > I configured Valgrind with the following: > > PKGCONFIG: /usr/local/lib64/pkgconfig > CPPFLAGS: -I/usr/local/include -DNDEBUG > CFLAGS: -g2 -O2 -m64 -march=native -fPIC > CXXFLAGS: -g2 -O2 -m64 -march=native -fPIC > LDFLAGS: -L/usr/local/lib64 -m64 -Wl,-R,/usr/local/lib64 > -Wl,--enable-new-dtags > LDLIBS: -ldl -lpthread
Not too sure what you did/how you obtained the above. The valgrind configure machinery is very special. Unless you dig into the deep gory details of this machinery, you should not try to set any variable yourself. In particular, on dual arch systems (32 and 64 bits), changing CFLAGS like the above are very likely to give problems. Also, the valgrind core/tools cannot be linked with any library, so it is unclear why LDLIBS is set above. I suggest to start with a very basic configure, e.g. ./configure --prefix=<somewhere> and if that works, then that is a good start :). If after that, you have problems, you might try to solve them by playing with configure setup/args/env var, but that is very fragile. Philippe ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
