-
Notifications
You must be signed in to change notification settings - Fork 33
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
installation issue due to "t -> ." symlink in "t"-folder #26
Comments
@dkriegner, the warning message is correct. It is, indeed, a recursive symlink, which I use as a convenience when working with the test suite. I am surprised by your result, though. I've never seen that one before. In fact, I just made a fresh clone on the Ubuntu machine I am sitting at, ran What kind of computer are you using? In any case, as far as i can remember, you can safely remove the symlink and carry on. Doing so (as far as I can remember!) won't even affect the By the way, if you have any comments or suggestions for the installation instructions, please let me know. I find that a particularly hard document to write given that I understand the code so well. It is hard to myself in the shoes of someone coming to it for the first time. |
I am on:
let me know if you need more info. Otherwise the instructions are fine from my perspective. Except of few smaller problems with dependencies of dependencies (e.g. [1]) the only thing I realized was a broken link in this paragraph:
the anchor http://bruceravel.github.io/demeter/pods/installation.pod.html#quot_Installing_Demeter_without_root is missing. |
@bruceravel Actually I should highlight that this was not a warning, but the only output I got! Only after removing the symlink I could get any output from the build script! If the symlink is only needed on your testing machine I think you should consider removing it from the repo. |
Yes, "error" not "warning". Gotcha. Valid point about the symlink. Simply removing the symlink is almost certainly the right thing to do. Still, it would be nice to understand the cause. What does your machine say for
And thanks for pointing out the broken link. |
Happily, that particular problem will be going away entirely soon. That dependence was needed for the documentation system. I am in the middle of a complete rewrite of the document -- using sphinx instead of something home-brewed. |
|
Weird. Same as mine. I'm confused.... |
I think the problem originates in this module
see:
the problematic call to find is
where follow_fast is set, which changed somewhere between 1.63 and 1.70 |
bring test 3 up to date with current number of configuration groups fix the spnotexist Fit sanity check to deal with a path that reads a feffNNNN.dat file directly
Apparently sometime between 1.65 and 1.70. I have 1.65 on my machine. Now it's understood and clearly an upstream issue that I have to live with. Anyway, I removed the symlink and fixed a couple of other small bugs. See 63f2e1c Thank you very much for looking into this. It is pretty uncommon that someone does the footwork to track down a problem for me. I am pleasantly surprised and quite grateful. Cheers, |
During following the "installation from source" instructions [1] I experienced an error at step 3.
Step 3 says: run
perl ./Build.PL
I got:
<PATH>/demeter/t/t is a recursive symbolic link at /usr/lib64/perl5/5.20.2/File/Find.pm line 431.
Removing the symlink I could continue/finish the installation without problems. Is this symlink needed?
[1] http://bruceravel.github.io/demeter/pods/installation.pod.html
The text was updated successfully, but these errors were encountered: