Julien Pierre wrote: > > client.mk simply isn't part of the components tree (eg. I check out only > mozilla/nsprpub).
client.mk is checked out separately, i.e. you normally check out mozilla/client.mk first and then run "gmake client.mk" for the rest of the checkout. > Apparently the compiler is called with a Unix-like "-o object" syntax, > which does not work for ICC in OS/2. > I don't know anything about how autoconf works so I'm not sure how to > fix the problem. I would like to make this work right though and am > curious why the OS/2 browser uses a different process without configure > and how to patch it up so the components can be built separately from > the browser on OS/2. OS/2 uses the same build process with configure. The reason for deleting configure is because the default one produced for Mozilla is generated by an autoconf without OS/2 support. In other words, we delete configure and run autoconf to create an OS/2-literate configure from configure.in. The icc flags (-Fe|-Fo) are all there, but you have to run configure to get them. If you're just building nspr, try running autoconf in nsprpub and then configure (running autoconf will automatically overwrite the old configure). Haven't tried building it standalone from scratch lately, but the icc support in nspr is ancient. h~
