From: Logal N. <log...@gm...> - 2007-08-06 14:29:39
|
Keith: > I've lost count of the number of times this has already been > asked, and answered; please search the archives. I appreciate that, but I have found no such answers that yield a fix. One possible fix I tried right off was to install MSYS and MINGW where the installers want them, but I still see this issue with my build. One suggested downloading the MSYS developer package with GCC 2.95, but Make itself refuse to build under with that active. Still others suggest that it is a problem with the configuration files, but it doesn't happen with just GCC. With what I'm searching (many combinations of: command not found 127 make msys config build configure error) I have read every answer or there have been hundreds of pages going back years and I'm only back to about middle of 2006. Thanks anyway. David: > Hi. Under msys you are supposed to work in a more linux like environment, thus you have to > specifie directories wit '/', because '\' is interpreted inside a makefile like an scape character > sequence. If you want to specify '\', you'll have to use two '\' each time. I'm not using '\'. The source for Make is generating them on its own. The configure file I'm using for GCC only used '/'. I didn't have a clue what was going on until I put a bunch of out statements in various functions. Nearest I can tell one of the woe32 specific functions, the one used to get a full path to specific files, is returning the path with '\'. The thing is, I can't figure out how "$r/gcc/xgcc" gets changed to "C;C:\build\gcc\build\gcc\xgcc". I'm pretty much lost on this front. |