public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug bootstrap/15039] New: using --enable-checking=valgrind with non-standard installation
@ 2004-04-21 11:20 Tobias dot Schlueter at physik dot uni-muenchen dot de
  2004-04-21 12:25 ` [Bug bootstrap/15039] " pinskia at gcc dot gnu dot org
  2004-04-21 12:40 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
  0 siblings, 2 replies; 3+ messages in thread
From: Tobias dot Schlueter at physik dot uni-muenchen dot de @ 2004-04-21 11:20 UTC (permalink / raw)
  To: gcc-bugs

there is no documentation on how to use --enable-checking=valgrind, when
valgrind is installed, but can't be found during configuration. Something like
--with-valgrind=... or --valgrind-includes=... doesn't work. Setting
C_INCLUDE_PATH to the appropriate directory works, but IMHO there should be an
option to configure.

My configure-command is:
tobi@marktplatz build-valgrind]$ ../gcc/configure --prefix=/home/tobi/usr
--enable-languages=c,f95 --with-gmp=/home/tobi/usr --enable-checking=valgrind
when building it fails (not surprisingly) with:
...
checking for unistd.h... yes
checking valgrind.h usability... no
checking valgrind.h presence... no
checking for valgrind.h... no
checking for VALGRIND_DISCARD in <valgrind/memcheck.h>... no
checking for VALGRIND_DISCARD in <memcheck.h>... no
checking for valgrind... /home/tobi/usr/bin/valgrind
configure: error: *** Can't find both valgrind and valgrind/memcheck.h,
memcheck.h or valgrind.h
make: *** [configure-gcc] Error 1
[tobi@marktplatz build-valgrind]$

-- 
           Summary: using --enable-checking=valgrind with non-standard
                    installation
           Product: gcc
           Version: tree-ssa
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: Tobias dot Schlueter at physik dot uni-muenchen dot de
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15039


^ permalink raw reply	[flat|nested] 3+ messages in thread
* [Bug bootstrap/15039] using --enable-checking=valgrind with non-standard installation
  2004-04-21 11:20 [Bug bootstrap/15039] New: using --enable-checking=valgrind with non-standard installation Tobias dot Schlueter at physik dot uni-muenchen dot de
@ 2004-04-21 12:25 ` pinskia at gcc dot gnu dot org
  2004-04-21 12:40 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
  1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2004-04-21 12:25 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-04-21 11:42 -------
Confirmed.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
           Keywords|                            |build, documentation
   Last reconfirmed|0000-00-00 00:00:00         |2004-04-21 11:42:50
               date|                            |
            Version|tree-ssa                    |3.5.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15039


^ permalink raw reply	[flat|nested] 3+ messages in thread
* [Bug bootstrap/15039] using --enable-checking=valgrind with non-standard installation
  2004-04-21 11:20 [Bug bootstrap/15039] New: using --enable-checking=valgrind with non-standard installation Tobias dot Schlueter at physik dot uni-muenchen dot de
  2004-04-21 12:25 ` [Bug bootstrap/15039] " pinskia at gcc dot gnu dot org
@ 2004-04-21 12:40 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
  1 sibling, 0 replies; 3+ messages in thread
From: Tobias dot Schlueter at physik dot uni-muenchen dot de @ 2004-04-21 12:40 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From Tobias dot Schlueter at physik dot uni-muenchen dot de  2004-04-21 12:36 -------
I should add that there is no documentation at all on how to use the valgrind
enabled compiler. Running the compiler driver does the right thing, but there
doesn't seem to be a way to find out, how the compiler driver invokes valgrind
on the compiler proper. 'gfortran -v' provides the same information a
non-valgrind-enabled compiler gives. 'valgrind f951' seems to do the trick, but
I don't know if that's all that has to be done. I'm specifically interested in
this because I found a crash in f951 which only triggers when input is read from
stdin (PR15032), so I can't use the compiler driver.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15039


^ permalink raw reply	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-04-21 12:36 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-04-21 11:20 [Bug bootstrap/15039] New: using --enable-checking=valgrind with non-standard installation Tobias dot Schlueter at physik dot uni-muenchen dot de
2004-04-21 12:25 ` [Bug bootstrap/15039] " pinskia at gcc dot gnu dot org
2004-04-21 12:40 ` Tobias dot Schlueter at physik dot uni-muenchen dot de

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).