public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: schwab@linux-m68k.org
Cc: gdb-patches@sourceware.org
Subject: Re: Two observations using GDB 13 snapshot
Date: Sat, 07 Jan 2023 18:15:55 +0200	[thread overview]
Message-ID: <83y1qeqq10.fsf@gnu.org> (raw)
In-Reply-To: <83zgauqqa5.fsf@gnu.org> (message from Eli Zaretskii via Gdb-patches on Sat, 07 Jan 2023 18:10:26 +0200)

> 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?

  reply	other threads:[~2023-01-07 16:15 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-17 17:42 Eli Zaretskii
2022-12-19 10:07 ` Luis Machado
2022-12-19 12:48   ` Eli Zaretskii
2022-12-19 14:08     ` Luis Machado
2022-12-19 14:45       ` Eli Zaretskii
2022-12-19 21:18         ` Tom Tromey
2022-12-20  3:26           ` Eli Zaretskii
2022-12-23  3:34             ` Simon Marchi
2022-12-23  8:05               ` Eli Zaretskii
2022-12-24 17:57             ` Tom Tromey
2022-12-24 18:13               ` Eli Zaretskii
2022-12-27 17:19                 ` Tom Tromey
2022-12-27 18:00                   ` Eli Zaretskii
2022-12-28 12:35                     ` Luis Machado
2022-12-28 16:35                     ` Tom Tromey
2022-12-28 17:35                       ` Eli Zaretskii
2022-12-28 22:47                         ` Tom Tromey
2022-12-29 15:18                           ` Eli Zaretskii
2022-12-29 18:17                             ` Tom Tromey
2022-12-29 18:36                               ` John Baldwin
2022-12-29 19:13                               ` Eli Zaretskii
2022-12-29 20:22                                 ` Simon Marchi
2022-12-30 14:31                                   ` Eli Zaretskii
2023-01-03 19:44                                     ` Christian Biesinger
2023-01-03 20:18                                       ` Eli Zaretskii
2023-01-03 20:34                                         ` Christian Biesinger
2023-01-03 21:34                                           ` Simon Marchi
2023-01-03 21:43                                             ` Christian Biesinger
2023-01-04  1:03                                             ` Tom Tromey
2023-01-04 18:10                                             ` Eli Zaretskii
2023-01-04 22:33                                               ` Tom Tromey
2023-01-05  7:11                                                 ` Eli Zaretskii
2023-01-05 14:49                                                   ` Christian Biesinger
2023-01-05 15:12                                                     ` Eli Zaretskii
2023-01-06 20:55                                                   ` Tom Tromey
2023-01-05 18:06                                               ` Torbjorn SVENSSON
2023-01-07  6:30 ` Eli Zaretskii
2023-01-07  9:14   ` Andreas Schwab
2023-01-07  9:32     ` Eli Zaretskii
2023-01-07 10:00       ` Andreas Schwab
2023-01-07 10:51         ` Eli Zaretskii
2023-01-07 13:04           ` Andreas Schwab
2023-01-07 13:54             ` Eli Zaretskii
2023-01-07 13:59               ` Andreas Schwab
2023-01-07 14:12                 ` Eli Zaretskii
2023-01-07 14:23                   ` Andreas Schwab
2023-01-07 14:29                     ` Eli Zaretskii
2023-01-07 14:40                       ` Andreas Schwab
2023-01-07 15:07                         ` Eli Zaretskii
2023-01-07 15:40                           ` Andreas Schwab
2023-01-07 16:10                             ` Eli Zaretskii
2023-01-07 16:15                               ` Eli Zaretskii [this message]
2023-01-07 16:16                               ` Hannes Domani
2023-01-07 16:22                                 ` Eli Zaretskii
2023-01-07 17:39                                 ` Andreas Schwab
2023-01-07 18:08                                   ` Eli Zaretskii
2023-01-07 18:26                                     ` Andreas Schwab
2023-01-07 18:38                                       ` Eli Zaretskii
2023-01-07 19:26                                         ` Andreas Schwab
2023-01-07 19:35                                           ` Eli Zaretskii
2023-01-07 18:28                                     ` Hannes Domani
2023-01-07 19:25                                       ` Andreas Schwab
2023-01-07 15:07                       ` Eli Zaretskii

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=83y1qeqq10.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=schwab@linux-m68k.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).