public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Bug Report: Regression in Cygwin 2.11.0-1
Date: Sat, 01 Sep 2018 09:07:00 -0000	[thread overview]
Message-ID: <86baef13-6a0d-e341-d7e6-d8109d5fd2f7@towo.net> (raw)
In-Reply-To: <6a50c529-f611-0c60-d95c-8dadd7459f06@gmail.com>

Am 01.09.2018 um 10:10 schrieb Marco Atzeri:
> 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 ?
> This mixed "../stdlib\libcamlrun.a" slash looks strange
It does, but remember, we're running on a mixed system. Also the problem 
is not caused by mixed syntax, the following do not work anymore:
     cd /usr; ls '..\bin'
     cd /; ls 'usr\include'
I think it's good that cygwin used to support this and it should be 
reestablished.
Note the following did not even work before, due to mount point issues:
     cd /; ls 'usr\bin'
Not sure whether it's worth fixing that seeming inconsistence as well.

Checking the change log, it might be a side effect of

- Fix a buffer underrun problem in Win32 path normalization.
   Addresses:https://cygwin.com/ml/cygwin/2018-05//msg00017.html


Checking the commit diff
https://cygwin.com/git/gitweb.cgi?p=newlib-cygwin.git;a=commitdiff;h=35998fc2fa6cbb7d761f6d88346246bd3627552b
this might be a starting point to analyse...

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


--
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

      parent reply	other threads:[~2018-09-01  9:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-01  1:25 Bryan Phelps
2018-09-01  7:58 ` Andreas Hauptmann
2018-09-01 15:54   ` Corinna Vinschen
2018-09-01 16:42     ` David Allsopp
2018-09-01 19:22       ` Corinna Vinschen
2018-09-02  8:38         ` David Allsopp
2018-09-03  7:39           ` Corinna Vinschen
2018-09-03 19:13             ` Achim Gratz
2018-09-03 20:31               ` Corinna Vinschen
2018-09-01 22:05       ` Andrey Repin
2018-09-02  3:36         ` cyg Simple
2018-09-02  7:32           ` David Allsopp
2018-09-01 18:08     ` Houder
2018-09-01 19:24       ` Corinna Vinschen
2018-09-01 21:25         ` Houder
2018-09-01 20:08     ` Bryan Phelps
2018-09-01  8:03 ` Marco Atzeri
2018-09-01  8:11 ` Marco Atzeri
2018-09-01  8:31   ` David Allsopp
2018-09-01  9:07   ` Thomas Wolff [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=86baef13-6a0d-e341-d7e6-d8109d5fd2f7@towo.net \
    --to=towo@towo.net \
    --cc=cygwin@cygwin.com \
    /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).