Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: MinGW build failure for GDB 8.2.90 with source-highlight
Date: Thu, 07 Mar 2019 14:36:00 -0000	[thread overview]
Message-ID: <83r2bibvlv.fsf@gnu.org> (raw)

I've rebuilt the 8.2.90 pretest today on MinGW with source-highlight,
and the link step failed with this error message:

       CXXLD  gdb.exe
     d:/usr/bin/../lib/gcc/mingw32/6.3.0/../../../../mingw32/bin/ld.exe: source-cache.o: in function `ZNSt13basic_filebufIcSt11char_traitsIcEED4Ev':
     d:/usr/lib/gcc/mingw32/6.3.0/include/c++/fstream:239: undefined reference to `std::basic_filebuf<char, std::char_traits<char> >::rpl_close()'
     d:/usr/bin/../lib/gcc/mingw32/6.3.0/../../../../mingw32/bin/ld.exe: source-cache.o: in function `ZNSt14basic_ifstreamIcSt11char_traitsIcEE8rpl_openEPKcSt13_Ios_Openmode':
     d:/usr/lib/gcc/mingw32/6.3.0/include/c++/fstream:597: undefined reference to `std::basic_filebuf<char, std::char_traits<char> >::rpl_open(char const*, std::_Ios_Openmode)'
     d:/usr/bin/../lib/gcc/mingw32/6.3.0/../../../../mingw32/bin/ld.exe: source-cache.o: in function `ZNSt13basic_filebufIcSt11char_traitsIcEED4Ev':
     d:/usr/lib/gcc/mingw32/6.3.0/include/c++/fstream:239: undefined reference to `std::basic_filebuf<char, std::char_traits<char> >::rpl_close()'
     collect2.exe: error: ld returned 1 exit status
     Makefile:1888: recipe for target `gdb.exe' failed
     make[2]: *** [gdb.exe] Error 1
     make[2]: Leaving directory `/d/usr/eli/utils/gdb-8.2.90/gdb'
     Makefile:8831: recipe for target `all-gdb' failed
     make[1]: *** [all-gdb] Error 2
     make[1]: Leaving directory `/d/usr/eli/utils/gdb-8.2.90'
     Makefile:856: recipe for target `all' failed
     make: *** [all] Error 2

The rpl_open and rpl_close thingies come from Gnulib: in the MinGW
build it replaces 'open' and 'close' with its versions by using
#define.  Then when we include <fstream> in source-cache.c, the C++
compiler barfs.

Is this a Gnulib bug that I should report to its developers, or is
this our problem?  Perhaps we should simply #undef these two symbols
before including <fstream>?


             reply	other threads:[~2019-03-07 14:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 14:36 Eli Zaretskii [this message]
2019-03-07 16:59 ` Simon Marchi
2019-03-07 17:11   ` Pedro Alves
2019-03-07 18:09     ` Simon Marchi
2019-03-07 18:20       ` Pedro Alves
2019-03-07 18:24         ` Simon Marchi
2019-03-07 20:29         ` Eli Zaretskii
2019-03-07 20:13   ` Eli Zaretskii
2019-03-11 14:18 ` Eli Zaretskii
2019-03-12  2:31   ` Simon Marchi
2019-03-12 10:52     ` Pedro Alves
2019-03-12 13:43       ` Simon Marchi
2019-03-12 15:49     ` Eli Zaretskii
2019-03-12 16:29       ` Simon Marchi
2019-03-12 17:53         ` 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=83r2bibvlv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.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