On 14-Feb-2006, Eric Blake wrote:
| so it is a
| bug in octave if it is mis-optimizing traversal in the presence of a
| directory link count of 1. It might make sense, though, for cygwin to set
| the link count to 0 on remote directories (rather than 1), to make it
| obvious that the link count r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 2/14/2006 7:18 AM:
>>>
>>>The code checks for two links (the %h) given that a subdirectory should
>>>have a "." and a ".." entry. But for some reason, network drives
>>>created using windows within cygwin report 1.
>
> Beca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ugh - top-posting reformatted http://cygwin.com/acronyms/#TOFU
According to Larrie Carr on 2/11/2006 11:25 PM:
>>> Probably the code you are looking for is the function do_subdir in
>>> liboctave/kpse.cc. This file contains a stripped-down version of
So the punch line is that octave will not work with network drives due to
the difference on how "stat" returns the number of hard links. Octave uses
stat to determine if the directory is recusible. But you can replicate the
problem with using stat on the command line.
$stat -c "%h %f" /cygdr
John W. Eaton wrote
Probably the code you are looking for is the function do_subdir in
liboctave/kpse.cc. This file contains a stripped-down version of the
kpathsearch library. Most modifications were to remove TeX-specific
stuff and to convert it to use std::string instead of plain C strings
w
As I said earlier, the functionality works for me, no matter how deeply nested
the subdirectories. Since I cannot reproduce the problem, I have to assume it
is something related to your particular setup. This does not mean it there is
no bug. It just means I don't know what conditions must exist
| In short, octave-forge is non-functional as it uses multiple
subdirectories.
If that's true for everyone, then I'm surprised as I think you are the
first to report it.
Sorry about the tone - it's not functional for me, while everyone else is
happy. I've tried a clean new cygwin installat
On 9-Feb-2006, Larrie Carr wrote:
| In short, octave-forge is non-functional as it uses multiple subdirectories.
If that's true for everyone, then I'm surprised as I think you are the
first to report it.
| I've been looking through the sources and nothing has sprung up. Did find a
| cut-and-p
Your attachments don't seem to be available, so I am not able to see the
structure of your test.
However, a test of my own indicates the functionality does work. What I do
is
create a file called .octaverc in my own home directory, with the contents
LOADPATH=[LOADPATH,':~/.octave/
On 09 February 2006 17:04, James R. Phillips wrote:
> Your attachments don't seem to be available, so I am not able to see the
> structure of your test.
WJFFM. Handy workaround: If your mailer doesn't like the format of an
attachment to a mailing list post, you can probably download it from th
Your attachments don't seem to be available, so I am not able to see the
structure of your test.
However, a test of my own indicates the functionality does work. What I do is
create a file called .octaverc in my own home directory, with the contents
LOADPATH=[LOADPATH,':~/.octave//];
++
In 2.1.72-1, the LOADPATH or DEFAULT_LOADPATH use of the "//" path ending
only appears to recurse 1 subdirectory level. I've attach a test_recurse.m
that shows how the "butter.m" file appears as the path is "lowered".
According to the octave documentation, all subdirectories are supposed to be
12 matches
Mail list logo
