$ ! Bootstrap build script for Jam $ vf = 'f$verify(1)' $ cxx /define=VMS builtins.c $ cxx /define=VMS command.c $ cxx /define=VMS compile.c $ cxx /define=VMS expand.c $ cxx /define=VMS execvms.c $ cxx /define=VMS filevms.c $ cxx /define=VMS glob.c $ cxx /define=VMS hash.c $ cxx /define=VMS headers.c $ cxx /define=VMS jambase.c $ cxx /define=VMS lists.c $ cxx /define=VMS make.c $ cxx /define=VMS make1.c $ cxx /define=VMS newstr.c $ cxx /define=VMS option.c $ cxx /define=VMS parse.c $ cxx /define=VMS pathvms.c $ cxx /define=VMS regexp.c $ cxx /define=VMS rules.c $ cxx /define=VMS scan.c $ cxx /define=VMS search.c $ cxx /define=VMS timestamp.c $ cxx /define=VMS variable.c $ cxx /define=VMS jam.c $ cxx /define=VMS /NOOPTIMIZE jamgram.c $ cxxlink/exe=jam.exe command.obj, compile.obj, execvms.obj, expand.obj, - filevms.obj, glob.obj, hash.obj, headers.obj, lists.obj, make.obj, - make1.obj, newstr.obj, option.obj, parse.obj, pathvms.obj, regexp.obj, - rules.obj, scan.obj, search.obj, timestamp.obj, variable.obj, jam.obj, - jamgram.obj, jambase.obj, builtins.obj $ exit 1 .or. f$verify(vf)
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#3 | 9855 | noahf |
* Build.com: Compile jamgram.c with /NOOPTIMIZE. The V7.2-021 cxx compiler on VMS8.2/IA64 has trouble with the parser produced by either (b)yacc or bison: when jamgram.c is compiled with optimization levels at or above /OPTIMIZE=(LEVEL=2), jam.exe crashes as soon as it begins to parse its internal copy of Jambase. (The default optmization level is /OPTIMIZE=(LEVEL=4), by the way.) * Build.com: Display commands in build.com as they are executed, since there is no other progress notification. * Jambase ($(VMS)): Remove special cases for OS=OPENVMS and OS=VMS; Newer compilers do not accept "vaxc" as a C dialect, and vaxcrtl.olb does not exist on IA64. There is no real difference between VMS and OPENVMS; the latter is just marketingspeak. Having both OS=VMS and OS=OPENVMS switches is probably more confusing than helpful; if in the future these flags need to be restored, consider using some combination of OSPLAT and/or OSVER also. p4transfer.py: Transferred from production |
||
#2 | 1319 | rmg |
Jam 2.3 + Perforce's internal changes. This change is a drop of the Perforce internal Jam changes since the 2.3 public release. The individual changes represented herein are preserved in the //guest/richard_geiger/intjam/ branch. The intent of this drop is to provide a base, from which other contributors' Jam branches may be integrated into. It is not intended to become a packaged release in this state. We will be integrating changes from other users prior to creating the next packaged release. Please refer to the src/RELNOTES file for an overview of the changes present in this integration. - Richard Geiger Open Source Engineer at Perforce |
||
#1 | 2 | laura | Add Jam/MR 2.2 source |