bug-gdb
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gdb-6.1


From: Pieter Donche
Subject: gdb-6.1
Date: Tue, 27 Apr 2004 09:59:59 +0200 (CEST)

Hi,

I have a SUN Blade 2000, Solaris 9. I have gcc-3.2.
Downloaded gdb-6.1 and tried to build it.

# # /home/wins/builds/src/gnu/gdb-6.1/configure
loading site script /usr/local/share/config.site
creating cache ./config.cache
checking host system type... sparc-sun-solaris2.9
checking target system type... sparc-sun-solaris2.9
checking build system type... sparc-sun-solaris2.9
checking for a BSD compatible install... /usr/local/bin/install -c
cc1: warning: changing search order for system directory
"/usr/local/include"
cc1: warning:   as it has already been specified as a non-system directory
...
etc...
OK

Then tried
# make
did a lot of 'checking ...' too, then started make'ing, but ends with:
...
gcc -c -DHAVE_CONFIG_H -g -O2 -I.
-I/home/wins/builds/src/gnu/gdb-6.1/libiberty/../include  -W -Wall
-Wtraditional -pedantic
/home/wins/builds/src/gnu/gdb-6.1/libiberty/fibheap.c -o fibheap.o
In file included from
/home/wins/builds/src/gnu/gdb-6.1/libiberty/fibheap.c:35:
/home/wins/builds/src/gnu/gdb-6.1/include/fibheap.h:63: warning: bit-field
`degree' type invalid in ISO C
/home/wins/builds/src/gnu/gdb-6.1/include/fibheap.h:64: warning: bit-field
`mark' type invalid in ISO C
/home/wins/builds/src/gnu/gdb-6.1/libiberty/fibheap.c: In function
`fibheap_union':
/home/wins/builds/src/gnu/gdb-6.1/libiberty/fibheap.c:166: warning:
implicit declaration of function `free'
/home/wins/builds/src/gnu/gdb-6.1/libiberty/fibheap.c:171: warning:
function `free' was previously declared within a block
/home/wins/builds/src/gnu/gdb-6.1/libiberty/fibheap.c:187: warning:
function `free' was previously declared within a block
/home/wins/builds/src/gnu/gdb-6.1/libiberty/fibheap.c: In function
`fibheap_extract_min':
/home/wins/builds/src/gnu/gdb-6.1/libiberty/fibheap.c:206: warning:
function `free' was previously declared within a block
/home/wins/builds/src/gnu/gdb-6.1/libiberty/fibheap.c: In function
`fibheap_delete_node':
/home/wins/builds/src/gnu/gdb-6.1/libiberty/fibheap.c:285: `LONG_MIN'
undeclared (first use in this function)
/home/wins/builds/src/gnu/gdb-6.1/libiberty/fibheap.c:285: (Each
undeclared identifier is reported only once
/home/wins/builds/src/gnu/gdb-6.1/libiberty/fibheap.c:285: for each
function it appears in.)
/home/wins/builds/src/gnu/gdb-6.1/libiberty/fibheap.c: In function
`fibheap_delete':
/home/wins/builds/src/gnu/gdb-6.1/libiberty/fibheap.c:297: warning:
function `free' was previously declared within a block
/home/wins/builds/src/gnu/gdb-6.1/libiberty/fibheap.c: In function
`fibheap_consolidate':
/home/wins/builds/src/gnu/gdb-6.1/libiberty/fibheap.c:395: warning:
implicit declaration of function `memset'
make[1]: *** [fibheap.o] Error 1
make[1]: Leaving directory
`/home/wins/builds/src/gnu/gdb-6.1/build/libiberty'
make: *** [all-libiberty] Error 2

I tried also using a newly created build subdirectory, but this makes no
difference. I browsed the Problem Report database for fibheap.c but
didn't find a problem report...

Then I tried again this time with our /usr/local/share/config.site
not active (I renamed it to config.site0). This file contains:
CC=gcc
CXX=c++
CPPFLAGS='-I/usr/local/include'
LDFLAGS='-L/usr/local/lib -R/usr/local/lib'

Started all over, and this time make did it ...
Is this normal ??

2. I noticed that the newly created gdb binary (6,8 Mb) is much smaller than
our previou gdb version 5.2.1 (=18 Mb)
# ls -la /usr/local/bin/gdb*
-rwxr-xr-x    1 root     other    18880360 Aug 22  2002 /usr/local/bin/gdb
-rwxr-xr-x    1 root     other     6821062 Apr 27 09:33 /usr/local/bin/gdb-6.1

Is this normal ?

Thanks for any help..

Pieter
  _______________
 / Pieter Donche \____________________________________________
 | ITC Manager                  e-mail address@hidden \
 | Dept. Mathem. & Computer Science, University of Antwerp    |
 | (UA) Middelheimlaan 1, B 2020 Antwerpen,      BELGIUM (EU) |
 | room G1.16,      tel +32 03.265.3870, fax +32 03.265.3777  |
 |____________________________________________________________|




reply via email to

[Prev in Thread] Current Thread [Next in Thread]