public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "costas.argyris at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/109460] Build gcc for win32 failed in gcc13 master branch
Date: Mon, 10 Apr 2023 19:54:13 +0000	[thread overview]
Message-ID: <bug-109460-4-t1PDxk4LbN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109460-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Costas Argyris <costas.argyris at gmail dot com> ---
Can you give some more info on how exactly you are cross-building gcc for
windows host?

Did you add the -fno-PIE flag manually or was it part of the build process you
are following?

Seems like you are trying to compile an executable out of sym-mingw32.cc, but
this shouldn't be happening because this file gets compiled into a simple
object file only.    That's why it would help to know more about the build
process you are following.

  reply	other threads:[~2023-04-10 19:54 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10  3:10 [Bug c/109460] New: " fanghuaqi at vip dot qq.com
2023-04-10 19:54 ` costas.argyris at gmail dot com [this message]
2023-04-10 20:41 ` [Bug c/109460] " ebotcazou at gcc dot gnu.org
2023-04-10 21:41 ` costas.argyris at gmail dot com
2023-04-10 22:07 ` ebotcazou at gcc dot gnu.org
2023-04-10 22:43 ` costas.argyris at gmail dot com
2023-04-11  1:45 ` fanghuaqi at vip dot qq.com
2023-04-11  8:54 ` costas.argyris at gmail dot com
2023-04-11  9:01 ` costas.argyris at gmail dot com
2023-04-11  9:15 ` fanghuaqi at vip dot qq.com
2023-04-11 10:12 ` costas.argyris at gmail dot com
2023-04-11 12:03 ` costas.argyris at gmail dot com
2023-04-12  4:11 ` [Bug bootstrap/109460] " fanghuaqi at vip dot qq.com
2023-04-12  4:13 ` fanghuaqi at vip dot qq.com
2023-04-12  6:54 ` costas.argyris at gmail dot com
2023-04-12  7:09 ` fanghuaqi at vip dot qq.com
2023-04-12  8:21 ` costas.argyris at gmail dot com
2023-04-12  9:32 ` fanghuaqi at vip dot qq.com
2023-04-12 10:00 ` costas.argyris at gmail dot com
2023-04-12 10:01 ` ebotcazou at gcc dot gnu.org
2023-04-12 10:04 ` ebotcazou at gcc dot gnu.org
2023-04-12 10:40 ` fanghuaqi at vip dot qq.com
2023-04-12 10:41 ` fanghuaqi at vip dot qq.com
2023-04-12 10:47 ` ebotcazou at gcc dot gnu.org
2023-04-12 11:17 ` costas.argyris at gmail dot com
2023-04-12 11:33 ` fanghuaqi at vip dot qq.com
2023-04-12 11:37 ` jakub at gcc dot gnu.org
2023-04-12 11:40 ` ebotcazou at gcc dot gnu.org
2023-04-12 11:58 ` costas.argyris at gmail dot com
2023-04-12 13:16 ` costas.argyris at gmail dot com
2023-04-12 14:41 ` burnus at gcc dot gnu.org
2023-04-12 14:45 ` costas.argyris at gmail dot com
2023-04-12 15:09 ` segher at gcc dot gnu.org
2023-04-12 15:17 ` segher at gcc dot gnu.org
2023-04-12 15:30 ` costas.argyris at gmail dot com
2023-04-13  3:09 ` fanghuaqi at vip dot qq.com
2023-04-13  9:12 ` costas.argyris at gmail dot com

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-109460-4-t1PDxk4LbN@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).