Michael Kaply wrote: > > This sounds like an PWD problem with the GCC build.
I got and answered the email version of Dave's post before the NG copy arrived. Suggested he try not running setmozenv.cmd, just make sure SHELL=gbash and the three configure.in's have been autoconf'd. No news since, and don't know if that's good news. Just looking at setmozenv.cmd now I see how it can cause problems. For instance, GLIB is set to %ROOT%\GLIBIDL\GLIB and then GLIB_CONFIG to %GLIB%\emx\bin\glib-config, which resolves to %ROOT%\GLIBIDL\GLIB\emx\bin\glib-config. I doubt whether anyone has emx installed in that location. For someone like Dave who already has a healthy emx+gcc environment according to the PS in his first post, setmozenv.cmd may do more harm than good. Similarly, given that ROOT is derived from the drive setmozenv.cmd is run from, I think the build instructions should emphasize that it has to be run from the drive on which emx and all the tools are installed. Otherwise people might run it immediately upon opening an OS/2 window or full-screen session, in which case ROOT is set to their boot drive, or on whatever drive they happened to install the src on, or even wherever they saved setmozenv.cmd which could be a downloads subdirectory on yet another partition. > Henry, which PWD build are you using and do you do objdir and srcdir > builds? The GNU sh-utils 1,12 version is first in PATH, but gbash also has one in its bin directory and an internal one that may run under certain circumstances. Haven't done a srcdir build since autoconf builds came along in late '98. h~
