devel/gdb6* broken with new readline?

Naram Qashat cyberbotx at cyberbotx.com
Wed May 19 21:41:11 UTC 2010


On 05/19/10 10:35, Frank Mayhar wrote:
> I'm trying to do a full upgrade of everything for the first time in a
> while.  After many gyrations, I've run into something that appears to
> not be my fault :-):
>
> cc -O2 -fno-strict-aliasing -pipe -DRL_NO_COMPAT       \
>                  -o gdb gdb.o libgdb.a \
>                     -lreadline ../opcodes/libopcodes.a ../bfd/libbfd.a  ../libiberty/libiberty.a     -lncurses -lm -L/usr/local/lib -liconv /usr/local/lib/libexpat.so -Wl,-rpath -Wl,/usr/local/lib ../libiberty/libiberty.a  -lkvm
> libgdb.a(tui-io.o)(.text+0x2aa): In function `tui_setup_io':
> : undefined reference to `readline_echoing_p'
> libgdb.a(tui-io.o)(.text+0x2b0): In function `tui_setup_io':
> : undefined reference to `readline_echoing_p'
> libgdb.a(tui-io.o)(.text+0x3c0): In function `tui_setup_io':
> : undefined reference to `readline_echoing_p'
> gmake[2]: *** [gdb] Error 1
> gmake[2]: Leaving directory `/usr/ports/devel/gdb66/work/gdb-6.6/gdb'
> gmake[1]: *** [all-gdb] Error 2
> gmake[1]: Leaving directory `/usr/ports/devel/gdb66/work/gdb-6.6'
> gmake: *** [all] Error 2
> *** Error code 1
>
> Stop in /usr/ports/devel/gdb66.
> *** Error code 1
>
> It fails the same way with devel/gdb6.  I did a bit of searching and
> apparently this is a known problem with the latest readline that was
> fixed in gdb 6.8.

I had submitted a patch to update devel/gdb6 to GDB 6.8, and GDB 6.6 was 
repocopied to devel/gdb66, but I haven't seen any updates recently on the 
situation.  Maybe we could look into this again, as well as the possibility of 
adding a devel/gdb7 port to accommodate the GDB 7.x branch?

Thanks,
Naram Qashat


More information about the freebsd-ports mailing list