public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/100238] New: [11/12] Link failure in debug libstdc++ on MinGW due to atomicitiy.cc
@ 2021-04-23 21:06 markus.boeck02 at gmail dot com
  2021-04-26  9:18 ` [Bug libstdc++/100238] [11/12 Regression] " redi at gcc dot gnu.org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: markus.boeck02 at gmail dot com @ 2021-04-23 21:06 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100238

            Bug ID: 100238
           Summary: [11/12] Link failure in debug libstdc++ on MinGW due
                    to atomicitiy.cc
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: markus.boeck02 at gmail dot com
  Target Milestone: ---

Building a shared libstdc++ with --enable-libstdcxx-debug for MinGW currently
fails to link on both trunk and the upcoming GCC 11 branch. 

The precise error as shown in the terminal is:

/mnt/c/GCC-Build/NewestLinux/bin/x86_64-w64-mingw32-ld:
../../src/debug/c++98/.libs/libc++98convenience.a(atomicity.o): in function
`__gnu_cxx::__exchange_and_add(int volatile*, int)':
/mnt/c/GCC-Build-Array/gcc/build-target-x86_64/x86_64-w64-mingw32/libstdc++-v3/src/debug/c++98/atomicity.cc:36:
multiple definition of `__gnu_cxx::__exchange_and_add(int volatile*, int)';
../../libsupc++/.libs/libsupc++convenience.a(atomicity.o):C:/GCC-Build-Array/gcc/build-target-x86_64/x86_64-w64-mingw32/libstdc++-v3/libsupc++/atomicity.cc:36:
first defined here
/mnt/c/GCC-Build/NewestLinux/bin/x86_64-w64-mingw32-ld:
../../src/debug/c++98/.libs/libc++98convenience.a(atomicity.o): in function
`__gnu_cxx::__atomic_add(int volatile*, int)':
/mnt/c/GCC-Build-Array/gcc/build-target-x86_64/x86_64-w64-mingw32/libstdc++-v3/src/debug/c++98/atomicity.cc:41:
multiple definition of `__gnu_cxx::__atomic_add(int volatile*, int)';
../../libsupc++/.libs/libsupc++convenience.a(atomicity.o):C:/GCC-Build-Array/gcc/build-target-x86_64/x86_64-w64-mingw32/libstdc++-v3/libsupc++/atomicity.cc:41:
first defined here

Configure option used was:

../configure --target=x86_64-w64-mingw32 --host=x86_64-w64-mingw32
--disable-bootstrap --enable-libstdcxx-debug --with-tune=znver1
--prefix=/mnt/c/GCC --with-sysroot=/mnt/c/GCC-Build/NewestLinux
--with-build-sysroot=/mnt/c/GCC-Build/NewestLinux --disable-libstdcxx-pch
--disable-multilib --enable-libgomp --with-cross-host
--with-libiconv-prefix=/mnt/c/GCC-Build/NewestLinux/Libraries
--disable-libstdcxx-verbose --enable-languages=c,c++,fortran,lto,objc,obj-c++,d
--disable-nls --disable-win32-registry --enable-shared --with-gnu-as
--with-gnu-ld --enable-threads=posix --program-suffix=-11
--enable-version-specific-runtime-libs --with-gcc-major-version-only
--enable-__cxa_atexit --enable-plugin --program-prefix=
--enable-checking=release

Last tested on revision 886b6c1e8af502b69e3f318b9830b73b88215878 of the master
branch

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libstdc++/100238] [11/12 Regression] Link failure in debug libstdc++ on MinGW due to atomicitiy.cc
  2021-04-23 21:06 [Bug libstdc++/100238] New: [11/12] Link failure in debug libstdc++ on MinGW due to atomicitiy.cc markus.boeck02 at gmail dot com
@ 2021-04-26  9:18 ` redi at gcc dot gnu.org
  2021-04-26 10:44 ` redi at gcc dot gnu.org
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2021-04-26  9:18 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100238

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2021-04-26
   Target Milestone|---                         |11.0
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |ASSIGNED
            Summary|[11/12] Link failure in     |[11/12 Regression] Link
                   |debug libstdc++ on MinGW    |failure in debug libstdc++
                   |due to atomicitiy.cc        |on MinGW due to
                   |                            |atomicitiy.cc

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This will be due to 6c0c7fc6236470a533675cd3cd1ebb1cc3dd112c

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libstdc++/100238] [11/12 Regression] Link failure in debug libstdc++ on MinGW due to atomicitiy.cc
  2021-04-23 21:06 [Bug libstdc++/100238] New: [11/12] Link failure in debug libstdc++ on MinGW due to atomicitiy.cc markus.boeck02 at gmail dot com
  2021-04-26  9:18 ` [Bug libstdc++/100238] [11/12 Regression] " redi at gcc dot gnu.org
@ 2021-04-26 10:44 ` redi at gcc dot gnu.org
  2021-04-27 11:40 ` jakub at gcc dot gnu.org
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2021-04-26 10:44 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100238

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |WAITING

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I can't reproduce this using a x86_64-w64-mingw32 cross compiler on a linux
host.

Are you sure you did a clean build, not an incremental re-build? 

(In reply to Markus Böck from comment #0)
> /mnt/c/GCC-Build-Array/gcc/build-target-x86_64/x86_64-w64-mingw32/libstdc++-
> v3/src/debug/c++98/atomicity.cc:36: multiple definition of
> `__gnu_cxx::__exchange_and_add(int volatile*, int)';

This file should no longer exist. It looks like you didn't build in a clean
directory, and have an old symlink around from before the functions moved from
libc++98convenience.a to libsupc++.a

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libstdc++/100238] [11/12 Regression] Link failure in debug libstdc++ on MinGW due to atomicitiy.cc
  2021-04-23 21:06 [Bug libstdc++/100238] New: [11/12] Link failure in debug libstdc++ on MinGW due to atomicitiy.cc markus.boeck02 at gmail dot com
  2021-04-26  9:18 ` [Bug libstdc++/100238] [11/12 Regression] " redi at gcc dot gnu.org
  2021-04-26 10:44 ` redi at gcc dot gnu.org
@ 2021-04-27 11:40 ` jakub at gcc dot gnu.org
  2021-05-01 13:43 ` markus.boeck02 at gmail dot com
  2021-05-01 22:45 ` redi at gcc dot gnu.org
  4 siblings, 0 replies; 6+ messages in thread
From: jakub at gcc dot gnu.org @ 2021-04-27 11:40 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100238

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|11.0                        |11.2

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
GCC 11.1 has been released, retargeting bugs to GCC 11.2.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libstdc++/100238] [11/12 Regression] Link failure in debug libstdc++ on MinGW due to atomicitiy.cc
  2021-04-23 21:06 [Bug libstdc++/100238] New: [11/12] Link failure in debug libstdc++ on MinGW due to atomicitiy.cc markus.boeck02 at gmail dot com
                   ` (2 preceding siblings ...)
  2021-04-27 11:40 ` jakub at gcc dot gnu.org
@ 2021-05-01 13:43 ` markus.boeck02 at gmail dot com
  2021-05-01 22:45 ` redi at gcc dot gnu.org
  4 siblings, 0 replies; 6+ messages in thread
From: markus.boeck02 at gmail dot com @ 2021-05-01 13:43 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100238

Markus Böck <markus.boeck02 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|WAITING                     |RESOLVED

--- Comment #4 from Markus Böck <markus.boeck02 at gmail dot com> ---
Clean build fixed this. Closing

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libstdc++/100238] [11/12 Regression] Link failure in debug libstdc++ on MinGW due to atomicitiy.cc
  2021-04-23 21:06 [Bug libstdc++/100238] New: [11/12] Link failure in debug libstdc++ on MinGW due to atomicitiy.cc markus.boeck02 at gmail dot com
                   ` (3 preceding siblings ...)
  2021-05-01 13:43 ` markus.boeck02 at gmail dot com
@ 2021-05-01 22:45 ` redi at gcc dot gnu.org
  4 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2021-05-01 22:45 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100238

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |INVALID

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
N.B. the "FIXED" status means gcc was fixed, which wasn't the case here (there
was nothing to fix).

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2021-05-01 22:45 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-23 21:06 [Bug libstdc++/100238] New: [11/12] Link failure in debug libstdc++ on MinGW due to atomicitiy.cc markus.boeck02 at gmail dot com
2021-04-26  9:18 ` [Bug libstdc++/100238] [11/12 Regression] " redi at gcc dot gnu.org
2021-04-26 10:44 ` redi at gcc dot gnu.org
2021-04-27 11:40 ` jakub at gcc dot gnu.org
2021-05-01 13:43 ` markus.boeck02 at gmail dot com
2021-05-01 22:45 ` redi at gcc dot gnu.org

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).