[Bug compile/26117] New: Link failure on windows due to invalid library order

[Bug compile/26117] New: Link failure on windows due to invalid library order

[markus.boeck02 at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=26117

            Bug ID: 26117
           Summary: Link failure on windows due to invalid library order
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: compile
          Assignee: unassigned at sourceware dot org
          Reporter: markus.boeck02 at gmail dot com
  Target Milestone: ---

Linking gdb currently yields following linker error when compiling with
x86_64-w64-mingw32-gcc:

/mnt/c/GCC-Build/NewestLinux/lib/gcc/x86_64-w64-mingw32/10/../../../../x86_64-w64-mingw32/bin/ld:
../gnulib/import/libgnu.a(inet_ntop.o): in function `rpl_inet_ntop':
C:/GDB-Build/binutils-gdb/build/gnulib/import/../../../gnulib/import/inet_ntop.c:58:
undefined reference to `__imp_inet_ntop'

The symbol __imp_inet_ntop is contained in ws2_32 which is correctly specified
on the command line to the linker but is specified in the wrong order for
libgnu.a

Excerpt from the linker command for gdb.exe:
/mnt/c/GDB-Build/libexpat/expat/install/lib/libexpat.a -lws2_32
../gnulib/import/libgnu.a -lstdc++ -lmingw32 -lgcc -lgcc_eh

When putting -lws2_32 behind libgnu.a instead of in front the link succeeds.
When using -fuse-ld=lld (an order insensitive linker) the link also succeeds.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug compile/26117] Link failure on windows due to invalid library order

[simark at simark dot ca]

https://sourceware.org/bugzilla/show_bug.cgi?id=26117

Simon Marchi <simark at simark dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |simark at simark dot ca

--- Comment #1 from Simon Marchi <simark at simark dot ca> ---
Is this a duplicate of 26068
(https://sourceware.org/bugzilla/show_bug.cgi?id=26068)?

There is a patch posted here:

  https://sourceware.org/pipermail/gdb-patches/2020-June/169314.html

I think the patch is fine, but I've asked the author to put a bit more details
to explain the issue and the solution in the commit message.  What you have
written here would be a very good start actually.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug build/26117] Link failure on windows due to invalid library order

[keiths at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=26117

Keith Seitz <keiths at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |keiths at redhat dot com
          Component|compile                     |build

--- Comment #2 from Keith Seitz <keiths at redhat dot com> ---
Moving to build component. Compile is for the compile feature.
["compile/* command and machinery"]

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug build/26117] Link failure on windows due to invalid library order

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=26117

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org
         Resolution|---                         |DUPLICATE
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
I think this is a dup.

*** This bug has been marked as a duplicate of bug 26068 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.