public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: THOMAS Paul Richard 169137 <prthomas@drfccad.cea.fr>
To: "'François-Xavier Coudert'" <fxcoudert@gmail.com>
Cc: gcc-bugs@gcc.gnu.org, fortran@gcc.gnu.org
Subject: RE: [Bug bootstrap] [4.1 regression] Build fails on Cygwin
Date: Wed, 03 Aug 2005 13:08:00 -0000	[thread overview]
Message-ID: <756DFD3DE8F1D411A59A00306E06E84702C427CB@drfccad.cad.cea.fr> (raw)

Thanks Francois-Xavier,

I saw your message and assumed that Cygwin was in the same state.  I looked
for but did not see the

+ #undef  COMMON_ASM_OP
+ #define COMMON_ASM_OP	"\t.comm\t"

in the patches.  It's strange, I was searching on COMMON_ASM_OP; perhaps
fingers trouble.

Paul T

> -----Message d'origine-----
> De : François-Xavier Coudert [mailto:fxcoudert@gmail.com]
> Envoyé : mercredi 3 août 2005 14:54
> À : THOMAS Paul Richard 169137
> Cc : gcc-bugs@gcc.gnu.org; fortran@gcc.gnu.org
> Objet : Re: [Bug bootstrap] [4.1 regression] Build fails on Cygwin
> 
> 
> Patches needed to build on mingw32 include
> http://gcc.gnu.org/ml/gcc-patches/2005-08/msg00009.html and
> http://gcc.gnu.org/ml/gcc-patches/2005-08/msg00097.html . The first
> one contains the fix to your problem, the second one is the latest
> version of the patch to fix dllimport.
> 
> However, on mingw32, this is not enough to build (see PR 
> 23210, for example).
> 
> FX
> 


             reply	other threads:[~2005-08-03 13:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03 13:08 THOMAS Paul Richard 169137 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-03 12:43 THOMAS Paul Richard 169137
2005-08-03 12:53 ` François-Xavier Coudert

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=756DFD3DE8F1D411A59A00306E06E84702C427CB@drfccad.cad.cea.fr \
    --to=prthomas@drfccad.cea.fr \
    --cc=fortran@gcc.gnu.org \
    --cc=fxcoudert@gmail.com \
    --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).