|
From: Lorenzo B. <be...@ds...> - 2009-02-26 09:10:11
|
Earnie Boyd wrote: > Quoting Lorenzo Bettini <be...@ds...>: > >> When compiling a program that uses fopen and run it from msys, it fails >> to open files such as >> >> /usr/local/share/foo.lang >> /home/myself/foo.lang >> >> although the files are there (and I can see them with less from the msys >> shell)... it suceeds to open them only when using the paths >> >> c:/msys/1.0/local/share/foo.lang >> c:/msys/1.0/home/myself/foo.lang >> >> is this the intended behavior? >> > > You haven't given enough to say whether what you perceive is correct or > not. If the path is being passed to the program from the shell on the > command line then MSYS should convert it for you. If the path is being > passed to fopen hardcoded in the source then yes, it is the correct > behavior. MSYS has no idea what fopen is doing; that belongs to the > MSVCRT runtime. > yes, I was actually talking about an hardcoded path, which in turn is retrieved directly from the configure script (the $prefix value); since configure defaults to /usr/local as a prefix, this technique basically does not work correctly in this environment -- Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino ICQ# lbetto, 16080134 (GNU/Linux User # 158233) HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com http://www.myspace.com/supertrouperabba BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com http://www.gnu.org/software/src-highlite http://www.gnu.org/software/gengetopt http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net |