Mark Healey wrote: > On Wed, 29 May 2002 13:40:08, Michael Kaply > <[EMAIL PROTECTED]> wrote: > > >>In that same window, type ICC and make sure ICC runs. >> >>There is a file config.log in the obj directory that should give you an >>idea of what the error is. > > > I fixed that. It turns out I neglected to re-cvs after fixing another > error. > > Now when I try I get > > *** Could not run libIDL test program, checking why... > *** The test program failed to compile or link. See the file > config.log for the > *** exact error that occured. This usually means libIDL was > incorrectly installed > *** or that you have moved libIDL since it was installed. In the > latter case, you > *** may want to edit the libIDL-config script: > e:\glibidl\emx\bin\libIDL-config > checking for orbit-config... no > configure: error: libIDL not found. > libIDL 0.6.3 or higher is required. > *** Fix above errors and then restart with "gmake.exe -f client.mk > build" > gmake: *** [f:/mozilla/obj/Makefile] Error 1 > > It looks like it expects a different directory structure than what is > in the zip > file. > > which is: > > glibidl > glib > emx > bin > include > lib > vacpp > libidl > emx > bin > include > lib > vacpp > > Should I just rearrange the directories? > > Mark Healey > marknews(the 'at' thing)healeyonline.com
My directory structure for glibidl is the same as the one you have listed above (which is how it came out of the .zip file). Initially I was having some trouble with with ../configure successfully recognising glib and libidl correctly... and it would happen in and on-and-off fashion. From my notes I have listed that when mucking with GLIB/LIBIDL you have to make certain that your GLIB2/LIBIDL2 environmental variables are the same as GLIB/LIBIDL but with the Unix-style forward slashes instead of OS/2 style back-slashes. Also, and I don't know if this is unique to my system or not, but I found that if I am using Java (1.1.8) at the same time that I try to compile, it will almost always cause the build to terminate with an error or cause configure to grow unhappy. And with this, the only way to sort've "clear" things was to do a reboot and then run ./configure or try to build again. Even if I closed down gbash and cmd.exe the error would persist, so I'd have to do the reboot-thing. Hope this helps, Jeff -- ---------------- Whatza JamochaMUD? http://jamochamud.anecho.mb.ca Or other stuff: http://www.anecho.mb.ca/~jeffnik -----------------------------------------------------------
