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:from:to:subject:date:message-id:references :in-reply-to:content-type:content-transfer-encoding :mime-version; q=dns; s=default; b=IoeX9RyF/lgfKHpkGMnXU/LLACOf8 lZHsV34NlBNUbNfkejgIVIJPLhGDm6UljEp0Z0Eb2OnkF/cM8qGsUezBICE9bJdk pdxaNzP8HtzjUsmBgBjhCm5WG/PZ/8rrKHtzJU0O8eLgAIIr36LmXSvtL8K7Bbzv ze9PnHhgcm17hU= 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:from:to:subject:date:message-id:references :in-reply-to:content-type:content-transfer-encoding :mime-version; s=default; bh=C03DbvFpywxBfDTot1Dg3FAsEnU=; b=DSL D0z1hCLumf4l8lTHFq7x0+T/BSaWiNqKMmXLlhRP+6Abx9hNrY7i9mcvCzipZ8hu ve2Vo+qzxCMzdicGRI47EvQLn1pxH/dAGPuggzi33YYVG5QQ0fUxg28Ma74+xzZ3 +fEHXfCiHKAylX8UHyakYE+pyqxyzkYvCh33f97c= 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-Spam-SWARE-Status: No, score=2.3 required=5.0 tests=BAYES_60,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,MIME_BASE64_BLANKS,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=Question, Phelps, bryan, Bryan X-HELO: outmail149084.authsmtp.net From: David Allsopp To: Marco Atzeri , "cygwin AT cygwin DOT com" Subject: RE: Bug Report: Regression in Cygwin 2.11.0-1 Date: Sat, 1 Sep 2018 08:28:58 +0000 Message-ID: References: <6a50c529-f611-0c60-d95c-8dadd7459f06 AT gmail DOT com> In-Reply-To: <6a50c529-f611-0c60-d95c-8dadd7459f06@gmail.com> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 X-Server-Quench: 145839da-adc1-11e8-9efd-0015176ca198 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd1ZAARAlZ5RRob BmUtCCtbTh09DhZI RxQKKE1TKxwUVhJU L0JGL0JXPR1GBEcB AnloDhRLUl1wUXN1 YgBTZA9dYwRMXgZ0 UUhMXFBTFhtpABge BBsBU1c1fwROHH4N MEZqWXNZXwpycEN5 DE9QEGUFbDMxdTFL A0FFdgIBeB5DK0kR d1B/VXYMZmNUN3tp TxkJEmJ5FyhQYB5Y WgYXMQBae0sEBDMn XBEFG30uGwUuVios LhpucBhFRQBJdxxa X-Authentic-SMTP: 61633634383431.1038:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 213.105.212.114/25 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id w818XIX3001707 Marco Atzeri wrote: > Am 01.09.2018 um 03:24 schrieb Bryan Phelps: > > Hello, > > > > > > Thank you for all the work on Cygwin! I've been using it to spin up an > environment 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 then > use that to build the OCaml toolchain. > > > > > > The error message we started receiving today is: > > > > OCAML_FLEXLINK="../boot/ocamlrun ../flexdll/flexlink.exe" > ../byterun/ocamlrun ../ocamlc -g -nostdlib -I ../utils -I ../parsing -I ../stdlib -I > ../compilerlibs -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 > run_stubs.o ocamltest_config.cmo testlib.cmo run_command.cmo filetype.cmo > filecompare.cmo backends.cmo variables.cmo environments.cmo > builtin_variables.cmo builtin_modifiers.cmo actions.cmo builtin_actions.cmo > tests.cmo builtin_tests.cmo tsl_ast.cmo tsl_parser.cmo tsl_lexer.cmo > tsl_semantics.cmo options.cmo main.cmo > > x86_64-w64-mingw32-gcc: error: ../stdlib\libcamlrun.a: No such file or > directory > > > > Question: > is libcamlrun.a built correctly and in the same directory than before ? I haven't double-checked, but the build cannot have got this far if the file were really missing. > This mixed "../stdlib\libcamlrun.a" slash looks strange Yeah, our build system is not terribly hygienic when it comes to mixing forward and backslashes in the Windows builds (the Windows shell of course is mostly forgiving of the mixture). It's not immediately clear to me from the announcement whether this change in behaviour is a regression or an intentional change? Only asking in terms of how quickly we need to make OCaml's build system cleaner. It's worth noting in this instance that x86_64-w64-mingw32-gcc would be being invoked by a non-Cygwin executable here (i.e. which IIRC is slightly different path normalisation than when it's invoked from bash). David -- 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