On Mon, 04 Feb 2002 12:16:19 -0500, Henry Sobotka wrote: >Michael Kaply wrote: >> >> This sounds like an PWD problem with the GCC build.
Actually this has turned out to be a shell problem. pwd -D is an internal gbash command option to show the drive letter. I have a bin directory on my build partition which contained sh from ksh, configure was picking this up and using it. I have replaced the ksh sh with sh from bash and also added bash to /bin and now everything seems to be working, or at least configure finished and now is compiling. Should finish sometime tonight <gr> > >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. Actually if you follow the web page instructions for setting up a build enviroment you do end up with this F:\glibidl\glib\emx\bin>dir glib-config glib.dll I decided to follow the porting instructions just to be sure I had a supported build enviroment. > 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. The only bad thing that setmozenv.cmd did here was putting e:\emx\bin at the begining of the path. At that it added /emx/bin twice. I did do a set EMX=e:\emx before running setmozenv.cmd. The bad code is /* REM *** EMX settings **** */ if buildtype = 'gcc' then /* GCC */ DO 'SET PATH=%EMX%\bin;%GLIB%\emx\bin;%LIBIDL%\emx\bin;%PATH%' I just removed the %EMX\bin; > >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. This can be solved by requesting the user to put setmozenv.cmd in their \moztools directory. > >> Henry, which PWD build are you using and do you do objdir and srcdir >> builds? > pwd -D only seems to work with gbash's builtin pwd. >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. > Henry how do you setup an object directory without using client.mk? Dave
