Hi Suzanne,
Isn't the mainframe world fun? ;-) The problem with too many characters
can be solved by doing your build in a directory which is closer to the
root of the file system (perhaps using a symlink). You can also copy the
screen dump of the link line to a shell script, remove the directory part
from all of the .o files, then run the shell script from the obj directory.
The latest version of Xalan supports building outside of the source tree,
so this is no longer a problem.
Dave
Suzanne Dirkers
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
com> cc: (bcc: David N
Bertoni/Cambridge/IBM)
Subject: Re: XalanTemplate.cpp on
mvs-uss
02/20/2003 06:46
AM
Please respond
to xalan-dev
Hi ,
This is not good news. I was able to get around it by having our
system guy devote an entire 3390 pack just to this job. And now that I've
got XalanTemplate.cpp and all the other files comiled into .o's, I find
that the zOS compiler linkage editor thinks there are too many characters
in the input buffer when we were still 2 directories of .o files from the
end. Now I guess I have to find how to fix that or get around that one.
Suzanne
David N
Bertoni/Cambridge To:
[EMAIL PROTECTED]
/IBM@Lotus cc:
Subject: Re:
XalanTemplate.cpp on mvs-uss
02/19/2003 11:46
AM
Please respond to
xalan-dev
Hi Suzanne,
That module exists solely to work around the very broken compiler you're
forced to use on zOS. Without it, the compiler will instantiate too many
template copies, which bloats the size of the executable tremendously. For
example, without it, building Xalan on AIX with the same broken compiler
front-end, the shared library is about 60MB.
The reason it's written that way is so fewer duplicate template
instantiations will occur. You can break it up, but for every separate
file, the compiler will generate duplicate instantiations, which will bloat
the executable. The latest version of the compiler fixes this problem, but
to use it, you need a particular level of zOS and you must use the new
linker technology.
You may want to see if you can temporarily bump up your memory limit.
Since that file is necessary only on zOS, we don't have any plans to modify
it any more. You're certainly welcome to experiment, but it's not for the
faint of heart...
Dave
Suzanne Dirkers
<[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
com> cc: (bcc: David N
Bertoni/Cambridge/IBM)
Subject: XalanTemplate.cpp
on mvs-uss
02/19/2003 07:46
AM
Please respond
to xalan-dev
Folks,
It appears that mvs-uss at V2R10 cannot compile Xalan 1.4 's
XalanTemplate.cpp without running out of virtual storage. And this is with
optimization of any level turned OFF. Any suggestions? Is it possible
to break this module up so that it doesn't become so huge it exhausts
virtual storage on mvs? Why is this written to be so huge anyway?
Thanks,
Suzanne
