GCC C compiler for MVS 3.8, MVS/XA, OS/390, z/OS and VM, z/VM, DOS/VS, z/VSE IBM mainframe computers. Plus MVS/380, VM/380, VSE/380 from Jujitsu. Note that the latest dev source and PC executables can be found in custom.zip and customb.zip at http://pdos.zip

Project Activity

  • Hi Piotr. Thanks for your feedback. Glad you got it working in the end. Note that using PDPCLIB is optional – you can use any C runtime library, and any C compiler. That’s just what I use, and the only thing that actually gets tested. However if you wish to build MVS etc programs, you have no real choice – you need to use PDPCLIB when you get there. I’m happy to replace the current compile (which I never use) with yours. Or your makefile. It would be good if the makefile worked with pdmake (a fairly...
  • The previous problem was because I didn't change all nul words using vi: %s/ nul / \/dev\/null /g but some nul words are followed by tab char so I have to change also like this: %s/ nul\t/ \dev\/null\t/g Additionally patch file is in MS-DOS format (CRLF in the end of line) and shoud be converted to Unix before use. After this I've received all patched files, also not-existent as gccmvs.txt and compile. You wrote that on the same level like gcc should be also pdos/pdpclib but readme lacks information...
  • Ok, the instructions I provide (in gccmvs.txt) are to run “compile” not “configure”. In addition, I’ve never attempted to target opened. In addition, I’ve only used 32-bit compilers, and much older versions of gcc. It might be worth building an 80386 version of gcc 3.2.3 before using that to build a s370 version of gcc 3.2.3. I do almost all of my 80386 work with gcc 3.2.3, because that is more-or-less the only option for s370 and I want my software to work on both environments. Anyway, I took a...
  • So I've downloaded patch file pointed by you, changed null to /dev/null and I've patched gcc source code (unpacked from gcc-3.2.3.tar.gz). Next i made: ./configure --target=i370-ibm-opened make and receive an error: make[1]: *** [Makefile:649: cp/decl.o] Error 1 make[1]: Leaving directory '/home/nome/projects/gcc-3.2.3/gcc' make: *** [Makefile:1604: all-gcc] Error 2 what is done by: cp/decl.c:13667:7: note: in expansion of macro ‘DECL_MAYBE_IN_CHARGE_CONSTRUCTOR_P’ if (DECL_MAYBE_IN_CHARGE_CONSTRUCTOR_P...
  • So I've downloaded patch file pointed by you, changed null to /dev/null and I've patched gcc source code (unpacked from gcc-3.2.3.tar.gz). Next i made: ./configure --target=i370-ibm-opened make and receive an error: make[1]: *** [Makefile:649: cp/decl.o] Error 1 make[1]: Leaving directory '/home/nome/projects/gcc-3.2.3/gcc' make: *** [Makefile:1604: all-gcc] Error 2 what is done by: cp/decl.c:13667:7: note: in expansion of macro ‘DECL_MAYBE_IN_CHARGE_CONSTRUCTOR_P’ if (DECL_MAYBE_IN_CHARGE_CONSTRUCTOR_P...

See All Activity >

License

Public Domain, GNU General Public License version 2.0 (GPLv2)

Follow GCCMVS

GCCMVS Web Site

You Might Also Like
The Complete PDF SDK The Complete PDF SDK Icon
The Complete PDF SDK

Bring PDF viewing, annotating, editing, creation, and generation to any web, mobile, desktop or server framework or application.

Bring accurate PDF viewing, annotating, editing, creation, and generation to any web, mobile, desktop or server framework or application. Own the full document and data lifecycle by deploying on your own infrastructure without worrying about third-party server dependencies.
Learn More
Rate This Project
Login To Rate This Project

User Reviews

Be the first to post a review of GCCMVS!

Additional Project Details

Operating Systems

Windows

Intended Audience

Developers

User Interface

Command-line

Programming Language

C

Related Categories

C Compilers, C Cross Compilers

Registered

2007-05-02