public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc at pdoerfler dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/27950]  New: [4.2 regression] undefined reference when compiling valgrind 3.2.0
Date: Thu, 08 Jun 2006 09:47:00 -0000	[thread overview]
Message-ID: <bug-27950-12708@http.gcc.gnu.org/bugzilla/> (raw)

if /usr/local/4.2/bin/gcc4.2.0 -DHAVE_CONFIG_H -I. -I. -I..  -I../include
-I../VEX/pub -DVGA_x86=1 -DVGO_linux=1 -DVGP_x86_linux=1   -m32
-mpreferred-stack-boundary=2 -O -g -Wmissing-prototypes -Winline -Wall -Wshadow
-Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -O2 -Wno-long-long
-Wno-pointer-sign -Wdeclaration-after-statement -save-temps -v -MT
memcheck_x86_linux-mc_main.o -MD -MP -MF ".deps/memcheck_x86_linux-mc_main.Tpo"
-c -o memcheck_x86_linux-mc_main.o `test -f 'mc_main.c' || echo './'`mc_main.c;
\
then mv -f ".deps/memcheck_x86_linux-mc_main.Tpo"
".deps/memcheck_x86_linux-mc_main.Po"; else rm -f
".deps/memcheck_x86_linux-mc_main.Tpo"; exit 1; fi
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc-4.2-svn/configure --enable-languages=c,c++
--prefix=/usr/local/4.2 --program-suffix=4.2.0
Thread model: posix
gcc version 4.2.0 20060603 (experimental)
 /usr/local/4.2/libexec/gcc/i686-pc-linux-gnu/4.2.0/cc1 -E -quiet -v -I. -I.
-I.. -I../include -I../VEX/pub -MD memcheck_x86_linux-mc_main.d -MF
.deps/memcheck_x86_linux-mc_main.Tpo -MP -MT memcheck_x86_linux-mc_main.o -MQ
memcheck_x86_linux-mc_main.o -DHAVE_CONFIG_H -DVGA_x86=1 -DVGO_linux=1
-DVGP_x86_linux=1 mc_main.c -m32 -mpreferred-stack-boundary=2 -mtune=generic
-Wmissing-prototypes -Winline -Wall -Wshadow -Wpointer-arith
-Wstrict-prototypes -Wmissing-declarations -Wno-long-long -Wno-pointer-sign
-Wdeclaration-after-statement -fworking-directory -O -O2 -fpch-preprocess -o
mc_main.i
ignoring nonexistent directory
"/usr/local/4.2/lib/gcc/i686-pc-linux-gnu/4.2.0/../../../../i686-pc-linux-gnu/include"
ignoring duplicate directory "."
#include "..." search starts here:
#include <...> search starts here:
 .
 ..
 ../include
 ../VEX/pub
 /usr/local/include
 /usr/local/4.2/include
 /usr/local/4.2/lib/gcc/i686-pc-linux-gnu/4.2.0/include
 /usr/include
End of search list.
 /usr/local/4.2/libexec/gcc/i686-pc-linux-gnu/4.2.0/cc1 -fpreprocessed
mc_main.i -quiet -dumpbase mc_main.c -m32 -mpreferred-stack-boundary=2
-mtune=generic -auxbase-strip memcheck_x86_linux-mc_main.o -g -O -O2
-Wmissing-prototypes -Winline -Wall -Wshadow -Wpointer-arith
-Wstrict-prototypes -Wmissing-declarations -Wno-long-long -Wno-pointer-sign
-Wdeclaration-after-statement -version -o mc_main.s
GNU C version 4.2.0 20060603 (experimental) (i686-pc-linux-gnu)
        compiled by GNU C version 4.2.0 20060603 (experimental).
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
Compiler executable checksum: a42b76558fd6d6863486421b7e5252eb
 as -V -Qy -o memcheck_x86_linux-mc_main.o mc_main.s
GNU assembler version 2.16.91.0.2 (i586-suse-linux) using BFD version
2.16.91.0.2 20050720 (SuSE Linux)
/usr/local/4.2/bin/gcc4.2.0  -Wno-long-long -Wno-pointer-sign
-Wdeclaration-after-statement -save-temps -v   -o memcheck-x86-linux -static
-Wl,-defsym,valt_load_address=0x38000000 -nodefaultlibs -nostartfiles -u _start
-m32 -Wl,-T,../valt_load_address_x86_linux.lds
memcheck_x86_linux-mc_leakcheck.o memcheck_x86_linux-mc_malloc_wrappers.o
memcheck_x86_linux-mc_main.o memcheck_x86_linux-mc_translate.o
../coregrind/libcoregrind_x86_linux.a ../VEX/libvex_x86_linux.a -lgcc
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc-4.2-svn/configure --enable-languages=c,c++
--prefix=/usr/local/4.2 --program-suffix=4.2.0
Thread model: posix
gcc version 4.2.0 20060603 (experimental)
 /usr/local/4.2/libexec/gcc/i686-pc-linux-gnu/4.2.0/collect2 -m elf_i386
-static -o memcheck-x86-linux -u _start
-L/usr/local/4.2/lib/gcc/i686-pc-linux-gnu/4.2.0
-L/usr/local/4.2/lib/gcc/i686-pc-linux-gnu/4.2.0/../../.. -defsym
valt_load_address=0x38000000 -T ../valt_load_address_x86_linux.lds
memcheck_x86_linux-mc_leakcheck.o memcheck_x86_linux-mc_malloc_wrappers.o
memcheck_x86_linux-mc_main.o memcheck_x86_linux-mc_translate.o
../coregrind/libcoregrind_x86_linux.a ../VEX/libvex_x86_linux.a -lgcc
memcheck_x86_linux-mc_main.o:(.debug_info+0x9d50): undefined reference to
`hacky_auxmaps'
collect2: ld returned 1 exit status


-- 
           Summary: [4.2 regression] undefined reference when compiling
                    valgrind 3.2.0
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: gcc at pdoerfler dot com
GCC target triplet: i686-pc-linux-gnu


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


             reply	other threads:[~2006-06-08  9:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08  9:47 gcc at pdoerfler dot com [this message]
2006-06-08 11:32 ` [Bug c/27950] " gcc at pdoerfler dot com
2006-06-08 14:46 ` [Bug middle-end/27950] " pinskia at gcc dot gnu dot org
2006-06-23 18:32 ` seongbae dot park at gmail dot com
2006-06-23 18:44 ` seongbae dot park at gmail dot com
2006-06-23 23:59 ` seongbae dot park at gmail dot com
2006-06-26  0:24 ` steven at gcc dot gnu dot org
2006-06-29 19:22 ` pinskia at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-27950-12708@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).