https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119217
--- Comment #29 from rdubner at symas dot com --- > -----Original Message----- > From: ro at CeBiTec dot Uni-Bielefeld.DE <gcc-bugzi...@gcc.gnu.org> > Sent: Tuesday, June 10, 2025 11:43 > To: rdub...@gcc.gnu.org > Subject: [Bug cobol/119217] cobol: build broken on non-linux by unguarded > use of Linux-specific facilities. > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119217 > > --- Comment #28 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot > Uni-Bielefeld.DE> --- > > --- Comment #27 from Robert Dubner <rdubner at gcc dot gnu.org> --- > > I have managed to compile gcobol and libgcobol.so on a i386-pc-solaris > system. > > (Thanks, Richard!) > > Good! (It's Rainer btw.;-) My sincere apologies. I was looking at some other messages from Richard, and I conflated the names. I don't like getting names wrong. > > > Attempting to compile a COBOL source file with the resulting gcobol > executable > > results in this rather intriguing error message: > > > > cobol1: out of memory allocating 150 bytes after a total of 786432 > bytes. > > > > I will be looking into that. > > I found that you can avoid this by putting LANG=C in the environment. > Haven't yet investigated why this happens, though. Well. I tried it. My instant reaction was "Son Of A ......!" Because it worked! Putting LANG=C in front of the compilation not only resulted in the compilation succeeding, the executable created by a "DISPLAY "HELLO" COBOL source code file actually ran. When the time comes to track this down, the error in this case was caused by a call to regcmp() in the course of processing regular expressions. Of course, not much else worked, sadly. Errors abound. But it's hopeful that DISPLAY "HELLO" actually worked! I know I am coming in late here, after a lot of work done by other people. Thank you all. > > > Meanwhile, since it appears that all of the original issues raised in > this PR > > have been addressed to the point where I can compile on an i386-solaris > system, > > I am going to close this PR out. > > I think so, yes. Though there are other issues on other targets, > they're covered by separate PRs. > > Thanks for your help with all this. > > -- > You are receiving this mail because: > You are on the CC list for the bug.
