BUG: directory creation error in smpeg activation

[jyrki.wahlstedt@…]

While building smpeg, it stops with the following: ---> Activating smpeg 0.4.4_4+darwin_8 Error: Activating smpeg 0.4.4_4 failed: can't create directory "": no such file or directory

The environment is OS X 10.4.1, gcc 4.0.

[mww@…]

would you mind providing a full log? $ port clean smpeg $ port install -vd smpeg > ~/Desktop/smpeg.log 2>&1 will do the trick

[jyrki.wahlstedt@…]

build log

[mww@…]

sorry, can't reproduce nor explain this error :(

maybe (!) this is a problem with /usr/local (though I doubt it)

[jyrki.wahlstedt@…]

Some new information: I built it after doing some file system manipulation. It seems that in some cases fake directories are created during the process and they cause problems or existing directories are corrupted for some reason. E.g. for smpeg, the directory ${prefix}/var/db/dports/build/file.+_multimedia_smpeg contained the following (from od -c): 0000000 \0 K 210 213 \0 \f 004 001 . \0 \0 \0 \0 K 210 212 0000020 003 364 004 002 . . \0 \0 \0 N 244 017 003 350 004 004 0000040 w o r k \0 \0 \0 \0 o r t s . l i b 0000060 s d l . s t a t e \0 * X \0 K 210 215 0000100 \0 024 004 \t S D L - 1 . 2 . 8 \0 \0 \0 0000120 \0 K 326 N 003 260 004 \b d e s t r o o t 0000140 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0002000 Moving this to another name and installing the port anew worked. Now the question is: how and why are these odd files/directories created (this is not the first and only) or get corrupt? The secondary problem is to get rid of these (not trivial). Should probably run fsck

[mww@…]

did running fsck make the problem go away? - I still have no idea why this happens;

[jyrki.wahlstedt@…]

(In reply to comment #5)

did running fsck make the problem go away? - I still have no idea why this happens;

Yes. I had a post-sleep freeze and had to restart and currently there are no corrupted directories present. The cause is not obvious. I have not experienced it otherwise in the system, maybe the TCL primitives have something?! Anyhow it is not reproducible (at least not reliably), so it is hard to get to.

[mww@…]

If this did not go away with the fixed FS, please reopen!