On Sun, 24 Aug 2003, [EMAIL PROTECTED] wrote:
> g++: ./out-/dev/vc//../../flower/out-/dev/vc//library.a: No such file or > directory After compiling with an another computer the result was g++-3.2.2: ./out-/dev/vc//../../flower/out-/dev/vc//library.a: No such file or directory which should be the same error. Here the parent directory of the three-level directory structure out-/dev/vc/ is referred just with ../ In the other computer the same test produced directory: ./out/../../flower/out/library.a So, there should not be that `out-/dev/vc' stuff at all! This leads to a conclusion that the error should be in some file which produces these directories. So what produces thos `out-/dev/vc' directories instead of just `out'? Invoking grep -R vc * gave four hits which showed that the error comes outside LilyPond source tree. Directory `/dev/vc' refers to virtual console devices. Let's find them -- in the the variables given by `set': In the other machine, one test gave $ set | grep out that is nothing, but in the other machine it gave $ set | grep out out=/dev/vc/ which means that this `out' variable should not be set. So, that's it! One should invoke unset out before starting compile things. If you press "C-A-F1" and login in to the virtual console in text mode, invoking $ set | grep out gives nothing. So, this is related somehow to desktop in Mandrake, which set the `out' variable. The same variable is later used by the compilation scripts. To conclude: Either - by compiling outside the desktop, in the text-mode consoles, it should be to compile lilypond with mandrake, or - invoking `unset out'. THE BUG in lilypond is that it uses `out', but does not take in to account the directory structure it may contain. Greetings, Heikki Junes _______________________________________________ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
