X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=UfAWRATysuoGeYhd Yp1Pdi53I8RHC7LQDwGKg8KRtQjTBATGLxpsnn9XDPvUyzVtNFdzND53fXCy1+rU bulgh57mKgEFsCJ6BoXmKbAPQI12Zd12obFCz+HFd6w6IHTDCEfnlsk701EF5phy 60EtiqinRjm35UiRdmMsJH5khAg= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=2tdWS0oVOJqP6dn2NtG5xm DFFmM=; b=LHZUHGodVre8ec1pNPy7wsK3sAoG1A6ZbNSekbvlXjIuP0KOM4vcoo qaBMYO0H5GO7ca9Z3FeWH4o1Vn/JKq3XZ9fLWHVnuIqn1asEm9MUFeclmYsUyZ63 gpe41kWrrUI2FlV3kxiOglPTgLP5uSJ6nHUyd01cZO7SI+wmqQRnA= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.8 required=5.0 tests=AWL,BAYES_05,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=H*i:sk:announc, H*RU:!192.168.1.100!, H*r:ip*192.168.1.100, Hx-spam-relays-external:!192.168.1.100! X-HELO: m0.truegem.net Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.5.0-0.11 To: cygwin AT cygwin DOT com References: From: Mark Geisert Message-ID: <5703531D.9070004@maxrnd.com> Date: Mon, 4 Apr 2016 22:54:37 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit I am running into a problem building Cygwin 2.5.0-0.11 from source on Windows 7 64-bit. This is not new with the latest test release but I believe it is new with 2.5.0 over 2.4.1. When building in winsup/utils, I hit this: c++wrap -pipe -march=haswell -fno-exceptions -fno-rtti -O2 -g -fno-rtti -fno-exceptions -fno-use-cxa-atexit -Wall -Wstrict-aliasing -Wwrite-strings -fno-common -pipe -fbuiltin -fmessage-length=0 -c -o cygwin-console-helper.o /oss/src/winsup/utils/cygwin-console-helper.cc i686-w64-mingw32-g++ -o cygwin-console-helper.exe cygwin-console-helper.o -static cygwin-console-helper.o: file not recognized: File format not recognized collect2: error: ld returned 1 exit status Makefile:153: recipe for target 'cygwin-console-helper.exe' failed make[3]: *** [cygwin-console-helper.exe] Error 1 make[3]: Leaving directory '/oss/build/x86_64-unknown-cygwin/winsup/utils' Makefile:83: recipe for target 'utils' failed make[2]: *** [utils] Error 1 make[2]: Leaving directory '/oss/build/x86_64-unknown-cygwin/winsup' Makefile:8947: recipe for target 'all-target-winsup' failed make[1]: *** [all-target-winsup] Error 2 make[1]: Leaving directory '/oss/build' Makefile:853: recipe for target 'all' failed make: *** [all] Error 2 I found that the generated winsup/utils/Makefile has MINGW_CXX := i686-w64-mingw32-g++ even though I am building on 64-bit. I'm not deeply familiar with autoconf but something about the configuring seems wrong. configure.ac checks for the existence of ${target_cpu}-w64-mingw32-g++ but config.status shows target_cpu isn't initialized until after MINGW_CXX is initialized. I have compilers for both arches installed, if that matters. ..mark -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple