Re: Compilation listings on the "new" ILE C compiler

Yeah, but it won't hurt anything. (At least it won't in other unix
shells.)

Thanks so much, I had no idea this was possible. Maybe it's at a version
beyond the systems on which I am working (v5r3) since I cannot find it. But
you've given me something to research and/or look forward to.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"I find that a great part of the information I have was acquired by looking
up something and finding something else on the way."
-- Franklin P. Adams

Ooops, of course there shouldn't be a // in the path name, well you get
the
idea.

/Erik

2010/9/24 Erik Olsson <erik.eo.olsson@xxxxxxxxx>

My pleasure, here's an example of a CRTBNDC:

ixlc /path/to//sourcefile.c -oMYLIB/MYPGM -qdbgview=source

There must not be a space between -o and the program name, took a

while to

figure out the first time.



2010/9/24 Dennis Lovelady <iseries@xxxxxxxxxxxx>

Thanks, Erik.

Would you mind sharing an example compile command that you'd issue

from

QSH?
Is it as simple (?) as /qsys.lib/crtcmod.cmd ... ?

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Money is what you'd get on beautifully without if only other people
weren't
so crazy about it."
-- Margaret Case Harriman

A propos the compiler listing: I've found that when using

output(*print)

sometimes vital info is cut off due to formatting so to be sure I

get

everything I normally output to a named textfile instead. For

shorter

programs I also favor invoking the compiler from Qshell as it will

echo

just
the error messages to stdout which can be time saving (don't have

to

scan
through a whole file for a single error).