https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119217
--- Comment #25 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- Robert, > I have gotten access, through cfarm.net, to a Solaris system. It happens to > be > a big-endian sparc system: > > LDOM on Oracle SPARC T8-1 (big-endian) > Solaris 11.4 Oracle Solaris 11.4 SPARC 5.11 > > There are six or so Solaris machines; this happened to be the first one that > let me in. while this is fine, I'd start with a Solaris/x86 system (cfarm215) first. cfarm216, being SPARC (big-endian) and strict-alignment has quite a number of additional issues compared to Solaris/x86, so I'd start with the latter to keep things simpler. > I cloned the cobolworx copy of the repository. > > $ mkdir build && cd build && ../configure --disable-bootstrap > $gmake > > It instantly comes back with > > rdubner@s11-sparc:~/repos/gcc-cobol/build$ gmake > gmake[1]: Entering directory '/home/rdubner/repos/gcc-cobol/build' > mkdir ./fixincludes > Configuring in ./fixincludes > /home/rdubner/repos/fixincludes > /bin/sh: /home/rdubner/repos/gcc-cobol: cannot open [Is a directory] > gmake[1]: *** [Makefile:3981: configure-fixincludes] Error 1 > gmake[1]: Leaving directory '/home/rdubner/repos/gcc-cobol/build' > gmake: *** [Makefile:1064: all] Error 2 > > > Any advice for me, before I start reverse engineering several universes about > which I know nothing? Several things to keep in mind: * It's best to prepend /usr/gnu/bin to PATH: while the native tools should work in principle, I only test with the GNU ones myself. In this case, I wonder if /usr/bin/make is used in the fixincludes subdir above, which is *not* GNU make and doesn't understand its extensions. * Although I do test with CONFIG_SHELL=/bin/ksh (which is /bin/sh on Solaris) all the time, in case of problems you may want to use configure CONFIG_SHELL=/bin/bash ... instead to avoid a possible cause of problems. * Be sure to include --enable-languages=cobol --enable-libgcobol in the configure line. Both language and runtime lib are not yet enabled by default on Solaris. If you don't get further with those hints, I can have a look at your build if that's ok with you: I happen to run those two cfarm host :-)
