Re: Two observations using GDB 13 snapshot

Eli Zaretskii via Gdb-patches
2023-01-07T16:15:57Z

> Date: Sat, 07 Jan 2023 18:10:26 +0200
> Cc: gdb-patches@sourceware.org
> From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
>
> > >> That does not happen for me. Did you configure with --enable-shared?
> > >
> > > No. Why would I need to?
> >
> > Without it, libtool should have no reason to put gdb in .libs.
>
> I see. Well, here it is.

Could it be related to the warnings I got from libtool during the
build:

/bin/sh ./libtool --tag=CC --mode=link gcc -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Wstack-usage=262144 -Wno-format -Werror -O2 -gdwarf-4 -g3 -release `cat libtool-soversion` -Wl,--stack,12582912 -o libbfd.la -rpath d:/usr/lib archive.lo archures.lo bfd.lo bfdio.lo bfdwin.lo cache.lo coff-bfd.lo compress.lo corefile.lo elf-properties.lo format.lo hash.lo init.lo libbfd.lo linker.lo merge.lo opncls.lo reloc.lo section.lo simple.lo stab-syms.lo stabs.lo syms.lo targets.lo binary.lo ihex.lo srec.lo tekhex.lo verilog.lo `cat ofiles` d:/usr/lib/libintl.a d:/usr/lib/libiconv.a -lz

*** Warning: Trying to link with static lib archive d:/usr/lib/libintl.a.
*** I have the capability to make that library automatically link in when
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because the file extensions .a of this argument makes me believe
*** that it is just a static archive that I should not use here.

*** Warning: Trying to link with static lib archive d:/usr/lib/libiconv.a.
*** I have the capability to make that library automatically link in when
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because the file extensions .a of this argument makes me believe
*** that it is just a static archive that I should not use here.
libtool: link: warning: undefined symbols not allowed in i686-pc-mingw32 shared libraries

Same warning in opcodes and in ibctf.

I ignored those, because they don't prevent the build, but maybe
libtool acted as if --enable-shared was specified, without me saying
so?