Re: [Gnu-arch-users] Planned move to Arch (cygwin issue) ...

[Davide Libenzi]

On Sun, 5 Oct 2003, Karl Waclawek wrote:

>
> > the build mysteriously fail the first of second time, and then it succeed!?
> > The `make test` fails in the test suite that perform fs-related thingies.
> > I ran a `make install` in any case hoping that those tests were a little
> > bit too aggressive, but they weren't. Arch indeed fails during the tagging
> > method selection by saying that the file ,,tagging-method cannot be moved
> > onto =tagging-method (that exist in the first place). Looking at Cygwin's
> > syscall.cc it seems that they use the correct function (MoveFileEx()) in
> > my system (XP), so I am running out of options. Is it possible to have
> > Arch correctly working on Cygwin?
>
> Look at recent archive messages:
> - You have to force use of bash on Cygwin (as sh is ash).
>   (I renamed sh to ash and turned sh into a soft link pointing to bash)

Already done, thx.



> - You have to apply Matthias Hoelzls patch for the tagging-method issue
>   (it somehow didn't make it into the release)

Ouch, missed.



> - There is till a Windows only problem with the fact that for any file
>   your total path length must not exceed 260 characters (MAX_PATH)

Is it a Cygwin limitation? Don't they use the "\\?\" prefix for paths,
that enable them to go up to 32000 chars?



> The steps above should get you going.
> make test will still fail at .../hackerlab/tests/unidata-tests,
> but the reason seems that the files ,tmp and ,tmp2 have different
> kinds of line breaks, but are otherwise identical (as the test requires)

Do you have an usable version after those fixes?



- Davide