Coreutils build used to require a managed mount?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Coreutils build used to require a managed mount?

Igor Peshansky
This is not an issue with coreutils-5.93, but the coreutils-5.3.0 source
won't extract without a managed mount due to some files that differ only
in filename case in the source tarball.  There are workarounds, of course,
but for the future, this is something that needs to be put in the package
announcement, at least.
        Igor
--
                                http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_    [hidden email] | [hidden email]
ZZZzz /,`.-'`'    -.  ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-' old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"
Reply | Threaded
Open this post in threaded view
|

Re: Coreutils build used to require a managed mount?

Eric Blake-2
> This is not an issue with coreutils-5.93, but the coreutils-5.3.0 source
> won't extract without a managed mount due to some files that differ only
> in filename case in the source tarball.  There are workarounds, of course,
> but for the future, this is something that needs to be put in the package
> announcement, at least.

It was fixed upstream post-5.3.0 because I packaged 5.3.0, noticed
the problem, and complained.  The only files affected by case clash
in 5.3.0 are test scripts, so you can still run configure and make
without issues.  But I never got errors from tar, even though I was
not using a managed mount.  My guess is that you must be using
an explicit setting of CYGWIN=check_case: that makes tar complain,
whereas I don't use that, so I just see tar creating the contents of
the second file in the spelling of the first.  That's why I never thought
to document it as a limitation.

--
Eric Blake
volunteer cygwin coreutils maintainer
Reply | Threaded
Open this post in threaded view
|

Re: Coreutils build used to require a managed mount?

Igor Peshansky
On Thu, 19 Jan 2006, Eric Blake wrote:

> > This is not an issue with coreutils-5.93, but the coreutils-5.3.0
> > source won't extract without a managed mount due to some files that
> > differ only in filename case in the source tarball.  There are
> > workarounds, of course, but for the future, this is something that
> > needs to be put in the package announcement, at least.
>
> It was fixed upstream post-5.3.0 because I packaged 5.3.0, noticed the
> problem, and complained.  The only files affected by case clash in 5.3.0
> are test scripts, so you can still run configure and make without
> issues.

Right.

> But I never got errors from tar, even though I was not using a managed
> mount.  My guess is that you must be using an explicit setting of
> CYGWIN=check_case: that makes tar complain, whereas I don't use that, so
> I just see tar creating the contents of the second file in the spelling
> of the first.  That's why I never thought to document it as a
> limitation.

Exactly.  I use check_case:strict (since I don't like tar, etc, to just
silently overwrite unrelated files).  One of the workarounds I mentioned
was explicitly setting "check_case:relaxed" before running the "prep"
step.  This was more of a "something to watch for in the future" kind of
thing...
        Igor
--
                                http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_    [hidden email] | [hidden email]
ZZZzz /,`.-'`'    -.  ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-' old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"