From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 113966 invoked by alias); 1 Sep 2018 01:25:15 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 113790 invoked by uid 89); 1 Sep 2018 01:25:00 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,KAM_NUMSUBJECT,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.2 spammy=importantly, (unknown), Hreceived-spf:outlook.com, meantime X-HELO: NAM02-CY1-obe.outbound.protection.outlook.com Received: from mail-oln040092004083.outbound.protection.outlook.com (HELO NAM02-CY1-obe.outbound.protection.outlook.com) (40.92.4.83) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 01 Sep 2018 01:24:58 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vn5sA1GaeIq00dk5zhQkdY2KH+2YtCkDcP67O7eTZDg=; b=csB+DBDizyIvTmqPScuWD7K4WxQGle7acOLhQg6Dwmi40TozztwVKdq2vg+fybPO3uyV6NBcahr+Mi5SIiKmgs7FztrFXWHdL0OweIifsTVHTRg6PTKjrwlAKjcwR3QAYDOszZ0DJ1H/79qdIXHbjtkZlXyNb4ciTXWJWIe0fku4KF2d/5ti8w1fFykor/ssxXc/5tIwFuMGjoiobOPGPgHUC3UX1Sc1+OscehECTjtnHkt8Y5OdQPMl1XwDhJInJVwYYzEYYvOaQZXdktXgA8vUqrGcjD1s9ZL5AOjudyzkAd+t4nzxr+zzskbjM9SADJ7gRQ3vztIeAgTDkNEDjw== Received: from SN1NAM02FT050.eop-nam02.prod.protection.outlook.com (10.152.72.59) by SN1NAM02HT210.eop-nam02.prod.protection.outlook.com (10.152.73.61) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.1101.10; Sat, 1 Sep 2018 01:24:49 +0000 Received: from BL2PR16MB0961.namprd16.prod.outlook.com (10.152.72.60) by SN1NAM02FT050.mail.protection.outlook.com (10.152.72.128) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.1101.10 via Frontend Transport; Sat, 1 Sep 2018 01:24:49 +0000 Received: from BL2PR16MB0961.namprd16.prod.outlook.com ([fe80::7c16:eb74:4302:4a0e]) by BL2PR16MB0961.namprd16.prod.outlook.com ([fe80::7c16:eb74:4302:4a0e%8]) with mapi id 15.20.1080.015; Sat, 1 Sep 2018 01:24:49 +0000 From: Bryan Phelps To: "cygwin@cygwin.com" Subject: Bug Report: Regression in Cygwin 2.11.0-1 Date: Sat, 01 Sep 2018 01:25:00 -0000 Message-ID: received-spf: None (protection.outlook.com: outlook.com does not designate permitted sender hosts) authentication-results: spf=none (sender IP is ) smtp.mailfrom=bryphe@outlook.com; MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-SW-Source: 2018-09/txt/msg00000.txt.bz2 Hello, Thank you for all the work on Cygwin! I've been using it to spin up an envi= ronment to build the OCaml compiler / toolchain, and it was working great. However, today, all our CI builds mysteriously started failing - at first, = I suspected it was a problem with AppVeyor, but I also failures with VSTS. = We use an NPM package (`esy-bash`) to spin up a Cygwin environment, and the= n use that to build the OCaml toolchain. The error message we started receiving today is: OCAML_FLEXLINK=3D"../boot/ocamlrun ../flexdll/flexlink.exe" ../byterun/ocam= lrun ../ocamlc -g -nostdlib -I ../utils -I ../parsing -I ../stdlib -I ../co= mpilerlibs -strict-sequence -safe-string -strict-formats -w +a-4-9-41-42-44= -45-48 -warn-error A -custom ocamlcommon.cma -o ocamltest.exe run_win32.o r= un_stubs.o ocamltest_config.cmo testlib.cmo run_command.cmo filetype.cmo fi= lecompare.cmo backends.cmo variables.cmo environments.cmo builtin_variables= .cmo builtin_modifiers.cmo actions.cmo builtin_actions.cmo tests.cmo builti= n_tests.cmo tsl_ast.cmo tsl_parser.cmo tsl_lexer.cmo tsl_semantics.cmo opti= ons.cmo main.cmo x86_64-w64-mingw32-gcc: error: ../stdlib\libcamlrun.a: No such file or dire= ctory The complete build log is here: https://gist.github.com/bryphe/58603ab752ecd988f78ee383fa9c9e78 After some investigation, I was able to isolate the issue - environments wi= th the 2.10.0-1 version of Cygwin built successfully, whereas newer environ= ments with the 2.11.0-1 version exhibit this failure. The remaining package= s are in parity - importantly, all the mingw packages we install are at the= same version. Results of cygcheck -c on both environments: - Working environment: https://gist.github.com/bryphe/b11f72f60d9d7c04a8e70= 9e6a8eb20ff - Failing environment: https://gist.github.com/bryphe/7cf4e6216030781eb273a= c45d36590cd I'll continue to look around for a more minimal repro, but I suspect there = may be other manifestations of it. It looks like there were a few path-rela= ted patches that came in to 2.11.0-1, so perhaps this scenario was impacted. In the meantime - is there a way we can pin the cygwin package to the 2.10.= 0-1 version, to unblock our builds? Thank you! Bryan Sent from Outlook -- 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