public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "brechtsanders at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/91595] Version (Windows) is not defined in GCC D Compiler
Date: Sun, 21 Mar 2021 09:56:42 +0000	[thread overview]
Message-ID: <bug-91595-4-mJfHFPAqHg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91595-4@http.gcc.gnu.org/bugzilla/>

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

Brecht Sanders <brechtsanders at users dot sourceforge.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |brechtsanders at users dot sourcef
                   |                            |orge.net

--- Comment #4 from Brecht Sanders <brechtsanders at users dot sourceforge.net> ---
I tried to build gcc 10 snapshot 20210320 for Windows 64-bit with the proposed
patch.

First I got this error:

make[2]: Entering directory
'/R/winlibs64_stage/gcc-10-20210320/build_mingw/gcc'make[2]: *** No rule to
make target 'config/winnt-d.c', needed by 'winnt-d.o'.
Stop.

After copying the file manually there like this:

mkdir -p build_mingw/gcc/config
cp -u gcc/config/i386/winnt-d.c build_mingw/gcc/config/

I got this error:

d:/prog/winlibs64_stage/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/11.0.1/../../../../x86_64-w64-mingw32/bin/ld.exe:
winnt-d.o:R:\winlibs64_stage\gcc-10-20210320\build_mingw\gcc/config/winnt-d.c:60:
multiple definition of `targetdm';
winnt-d.o:R:\winlibs64_stage\gcc-10-20210320\build_mingw\gcc/config/winnt-d.c:60:
first defined here
collect2.exe: error: ld returned 1 exit status

  parent reply	other threads:[~2021-03-21  9:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-91595-4@http.gcc.gnu.org/bugzilla/>
2020-03-22  0:08 ` ibuclaw at gdcproject dot org
2020-03-22  0:09 ` ibuclaw at gdcproject dot org
2020-03-22  0:16 ` ibuclaw at gdcproject dot org
2021-03-21  9:56 ` brechtsanders at users dot sourceforge.net [this message]
2021-03-21 10:30 ` ibuclaw at gdcproject dot org
2021-03-21 13:11 ` brechtsanders at users dot sourceforge.net
2021-03-21 13:20 ` ibuclaw at gdcproject dot org
2021-03-21 13:27 ` brechtsanders at users dot sourceforge.net
2021-03-21 13:44 ` ibuclaw at gdcproject dot org
2021-03-21 13:51 ` brechtsanders at users dot sourceforge.net
2021-03-21 14:18 ` ibuclaw at gdcproject dot org
2021-03-26 15:15 ` cvs-commit at gcc dot gnu.org
2021-03-26 15:50 ` ibuclaw at gdcproject dot org

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=bug-91595-4-mJfHFPAqHg@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).