Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

on Cygwin ECL does not handle case-sensitve paths well #13343

Closed
dimpase opened this issue Aug 5, 2012 · 6 comments
Closed

on Cygwin ECL does not handle case-sensitve paths well #13343

dimpase opened this issue Aug 5, 2012 · 6 comments

Comments

@dimpase
Copy link
Member

dimpase commented Aug 5, 2012

ECLs call

> (directory "")

must always return the current directory. On Cygwin, sometimes one gets NIL. One example is like this: say, a user John has Windows (domain) login name John, but Cygwin will create for him home directory "/home/john".
At this point, one might hit the Win32 case-sensitivity weirdness, and in particular installation scripts for Maxima spkg will fail in a subdirectory containing "/home/john". If one switches on case-sensitivity, as described in the link just cited, the problem goes away.

In a nutshell, while this remains unfixed, avoid building Sage in directories with names containing capitals. This was uncovered and mentioned here.

Upstream: Reported upstream. No feedback yet.

Component: porting: Cygwin

Issue created by migration from https://trac.sagemath.org/ticket/13343

@dimpase dimpase added this to the sage-5.11 milestone Aug 5, 2012
@jpflori
Copy link
Contributor

jpflori commented Aug 5, 2012

comment:1

Could this be related to #9167?

@jpflori
Copy link
Contributor

jpflori commented Aug 5, 2012

comment:2

I've mentioned the uppercase path problem on the CygwinPort page, just in case someone else wants to join the experience.

@dimpase
Copy link
Member Author

dimpase commented Aug 5, 2012

comment:3

Replying to @jpflori:

Could this be related to #9167?

I think one cannot rule this out just by reading comments on #9167.
Note capitals (e.g. SageUser) in some paths mentioned there.

@kcrisman
Copy link
Member

kcrisman commented Oct 5, 2012

comment:4

I decided not to use a an uppercase path this time, on the same machine, and didn't encounter any problems. I won't have the chance to try #9167 until after the weekend, but at any rate that's a positive sign.

I think it would be ok to even put this in prereq for a first start (i.e. ban such paths at the start of a build), since Cygwin would not be a typical building platform, but rather one we would specially use to create binaries only.

@jpflori
Copy link
Contributor

jpflori commented Mar 1, 2013

comment:5

Just for the report, the build I did recently on a 32 bits Windows 7 (Intel Atom something) took place in the home dir of a user with a capital first letter "/cygwin/home/Toto/sage-5.7" and I had no problems whatsoever.
It was even the more functional build I ever got so easily! (In part because I had no memory leaks on this machine.)

@jdemeyer jdemeyer modified the milestones: sage-5.11, sage-5.12 Aug 13, 2013
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.1, sage-6.2 Jan 30, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.2, sage-6.3 May 6, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.3, sage-6.4 Aug 10, 2014
@embray
Copy link
Contributor

embray commented Apr 19, 2019

comment:10

I'm pretty sure this is no longer an issue. Lots has changed since this was first reported, and among other things Cygwin does not force your home directory to be lower-case.

I've never seen the problem either, though I do usually mount my Cygwin home directory to an all lower-case, no-space name. So feel free to reopen if it recurs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants