NETWORK@FRSAC11.BITNET (01/15/88)
Date: 15 January 1988, 13:14:47 GMT From: NETWORK at FRSAC11 To: INFO-ATARI16 at SCORE Lately I had to to "make" a quite large program, including assembler and C sources, with the MCC Lattice C 3.04.01 development tools. 1. Make seems to send real fantasy arguments to programs exec'ed from it. (Make does not call a shell, it exec directly the lines...) 2. Link is so picky that it barely works under make... (-nolist bombs the whole thing ... amazing) 3. Link does NOT handle properly the mix assembly/output and C/output. (assemble is with MCC Macro assembler, C is with Lattice, all in GST format) There is a problem with the XDEF & XREF in assembly binaries, only in the "mind" of link... 4. I had to Compile with DRI format output, assemble with AS68, and link with link68... still slow, but it is working flawlessly. (quite a proof that the GST linker is buggy...) 5. MCC Lattice C is totally lacking the signal() thing, I need it. What can I do ??? 6. In C, always with Lattice C, getenv/putenv are not really working, I can not get anything correct from envp or environ after a putenv... Any solution ? 7. The forkv??() function family is not working, I had to write my own. 8. System() does not seems to work, in the manual they talk about a COMSPEC environment variable, this is highly non standard, whatever it is... Does anybody knows what is it ? I use system() in MWC, and it is working very nicely under msh, what the h... is doing msh to have it work ? (shell_p, COMSPEC, SHELL ... ???) Please if you know anything that can help, just make me a mail, I may come up with a product interesting to you, and free. Thank you for listening. Jean-Pierre H. Dumas network@frsac11 (bitnet) network%frsac11.bitnet@mitvma.mit.edu (arpanet) dumas@sumex-aim.stanford.edu (arpanet)