public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: fortran@gcc.gnu.org
Subject: Re: Build fails - configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES
Date: Mon, 30 Jul 2018 07:28:00 -0000	[thread overview]
Message-ID: <fd81c0d1-618f-184f-3086-c4d87efaa953@gmail.com> (raw)
In-Reply-To: <6ED57818-CA53-46AF-A485-83356CB390C0@yahoo.com>

Am 30.07.2018 um 00:24 schrieb Darrell Reich via fortran:
> Does anyone know what this build error means and how to fix it? I’ve successfully built gfortran 8 in the past.
> 
> checking for _wfopen... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
> make[1]: *** [Makefile:10799: configure-target-libstdc++-v3] Error 1
> make[1]: Leaving directory '/cygdrive/c/work/compiler/build-gcc'
> make: *** [Makefile:914: all] Error 2
> 
> Here’s more context of the commands I’ve typed and the log leading up to the error:
> 
> svn update
> cd ../build
> configure…
> make
> ...
> checking for sys/param.h... (cached) yes
..
> checking for memalign... (cached) yes
> checking for _aligned_malloc... (cached) no
> checking for _wfopen... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
> make[1]: *** [Makefile:10799: configure-target-libstdc++-v3] Error 1
> make[1]: Leaving directory '/cygdrive/c/work/compiler/build-gcc'
> make: *** [Makefile:914: all] Error 2
> 
> I’m using Cygwin on a Windows 7 PC configured to build c,c++,fortran...
> 

1) try removing "config.cache" before "configure"
2) looks on details for failed test in "config.log"

Regards
Marco

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

      reply	other threads:[~2018-07-30  7:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-29 22:24 Darrell Reich via fortran
2018-07-30  7:28 ` Marco Atzeri [this message]

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=fd81c0d1-618f-184f-3086-c4d87efaa953@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=fortran@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).