[M3devel] m3gdb status?

Rodney M. Bates rodney_bates at lcwb.coop
Tue Aug 19 18:14:13 CEST 2014

It's very dusty: looks unchanged since brought into the M3 repository from
gdb 6.4, in 2006.  However, I have built m3gdb many times since then, with
neither build failures nor bugs that are likely to have anything to do with
bfd/archive.c.  It looks like a harmless warning, from the original gdb,
turned into an error by the -Werror flag to gcc.

I last successfully compiled archive.c on 2013-10-21 for AMD64_LINUX and on
2014-6-23  for LINUXLIBC6.  Perhaps the -Werror flag has became a default
in gcc since.  In a quick scan using grep, I didn't see anywhere in the M3
distribution or installation that would have set it.

Changing -Werror to -Wno-error in variable WARN_CFLAGS in AMD64_LINUX/bfd/Makefile
and AMD64_LINUX/opcodes/Makefile got me through all the compile problems (hit
unrelated link problems).  But that's the wrong solution, as these Makefiles
are, I am sure, mechanically generated from somewhere else, no doubt configure.
I haven't figured out where it comes from originally.

On 08/19/2014 03:13 AM, mika at async.caltech.edu wrote:
> What is the status of m3gdb?
> I am on AMD64_LINUX here...head from CVS.
> The error looks pedantic but the fact that things aren't building makes me think maybe this code is pretty dusty...?
> /bin/sh ../../gdb/bfd/../move-if-change bfd-tmp.h bfd.h
> rm -f bfd-tmp.h
> touch stmp-bfd-h
> /bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../gdb/bfd -I. -I. -I../../gdb/bfd -I../../gdb/bfd/../include  -I../../gdb/bfd/../intl -I../intl   -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2  -c -o archive.lo ../../gdb/bfd/archive.c
> gcc -DHAVE_CONFIG_H -I. -I../../gdb/bfd -I. -I. -I../../gdb/bfd -I../../gdb/bfd/../include -I../../gdb/bfd/../intl -I../intl -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -c ../../gdb/bfd/archive.c -o archive.o
> ../../gdb/bfd/archive.c: In function 'bfd_generic_archive_p':
> ../../gdb/bfd/archive.c:669:16: error: variable 'fail' set but not used [-Werror=unused-but-set-variable]
> cc1: all warnings being treated as errors
> make[4]: *** [archive.lo] Error 1
> make[4]: Leaving directory `/big/home2/mika/2/cm3-cvs/cm3/m3-sys/m3gdb/AMD64_LINUX/bfd'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory `/big/home2/mika/2/cm3-cvs/cm3/m3-sys/m3gdb/AMD64_LINUX/bfd'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory `/big/home2/mika/2/cm3-cvs/cm3/m3-sys/m3gdb/AMD64_LINUX/bfd'
> make[1]: *** [all-bfd] Error 2
> make[1]: Leaving directory `/big/home2/mika/2/cm3-cvs/cm3/m3-sys/m3gdb/AMD64_LINUX'
> make: *** [all] Error 2
> "/big/home2/mika/2/cm3-cvs/cm3/m3-sys/m3gdb/src/m3makefile", line 40: quake runtime error: exit 2: make  MAKE=make  MAKEINFO=:
> --procedure--  -line-  -file---
> exec               --  <builtin>
> m3gdb_Run          40  /big/home2/mika/2/cm3-cvs/cm3/m3-sys/m3gdb/src/m3makefile
> include_dir        85  /big/home2/mika/2/cm3-cvs/cm3/m3-sys/m3gdb/src/m3makefile
>                      4  /big/home2/mika/2/cm3-cvs/cm3/m3-sys/m3gdb/AMD64_LINUX/m3make.args
> Fatal Error: package build failed
> (326)truffles:~/bsd/cm3-cvs-anon/cm3/m3-sys/m3gdb>

Rodney Bates
rodney.m.bates at acm.org

More information about the M3devel mailing list