NetCOBOL on Mandriva
in [Cobol]
|
Prev: Companys using Cobol in London
Next: oracle10g SQLBEX giving 114 with Oracle Dynamic SQL Method 4(ora9 works well)
From: charles.goodman on 25 Jan 2008 16:27 I am trying an eval of NetCOBOL for Linux. I am using Mandriva 2008. Installation is complete and I am able to compile, but I am getting a link error: "ld: No such file or directory". Fujitsu support are trying to help, but are a bit slow. Have any of you had luck getting Fujitsu's Linux compiler working on newer Linux distros? Best Regards, Charlie
From: Richard on 26 Jan 2008 23:37 On Jan 26, 10:27 am, charles.good...(a)bell.ca wrote: > I am trying an eval of NetCOBOL for Linux. > I am using Mandriva 2008. It should work fine on Mandriva. I run my copy of Fujitsu on that, though it has not been updated to 2008. > Installation is complete and I am able to compile, but I am getting a > link error: "ld: No such file or directory". > Fujitsu support are trying to help, but are a bit slow. > Have any of you had luck getting Fujitsu's Linux compiler working on > newer Linux distros? The problem is most likely case sensitivity. While DOS/Windows files are case insensitive under Unix and Linux file names with different case are distinct files. However, to setting of various compiler options can lead to confusing. The ALPHAL setting may change the case of program names and especially of literals used in a CALL. If you have a CALL "xxxx" then the linker may want to find a file: libXXXX.so and will fail if it doesn't exist, or has been named libxxx.so.
From: Vince Coen on 27 Jan 2008 06:37 Hello charles! 25 Jan 08 21:27, you wrote to All: cg> I am trying an eval of NetCOBOL for Linux. cg> I am using Mandriva 2008. cg> Installation is complete and I am able to compile, but I am getting a cg> link error: "ld: No such file or directory". cg> Fujitsu support are trying to help, but are a bit slow. cg> Have any of you had luck getting Fujitsu's Linux compiler working on cg> newer Linux distros? Having installed cobol have you run ldconfig ? If not do a man ldconfig and run it. Vince
From: C Goodman on 27 Jan 2008 07:43 Richard wrote: > On Jan 26, 10:27 am, charles.good...(a)bell.ca wrote: >> I am trying an eval of NetCOBOL for Linux. >> I am using Mandriva 2008. > > It should work fine on Mandriva. I run my copy of Fujitsu on that, > though it has not been updated to 2008. That's good news. >> Installation is complete and I am able to compile, but I am getting a >> link error: "ld: No such file or directory". >> Fujitsu support are trying to help, but are a bit slow. >> Have any of you had luck getting Fujitsu's Linux compiler working on >> newer Linux distros? > > The problem is most likely case sensitivity. While DOS/Windows files > are case insensitive under Unix and Linux file names with different > case are distinct files. However, to setting of various compiler > options can lead to confusing. The ALPHAL setting may change the case > of program names and especially of literals used in a CALL. If you > have a CALL "xxxx" then the linker may want to find a file: libXXXX.so > and will fail if it doesn't exist, or has been named libxxx.so. I don't think that is the problem. My test program simply uses DISPLAY and ACCEPT for hello world. This may be a problem once I start working on my full system of 1000 programs.
From: C Goodman on 27 Jan 2008 08:03
Vince Coen wrote: > Hello charles! > > 25 Jan 08 21:27, you wrote to All: > > cg> I am trying an eval of NetCOBOL for Linux. > cg> I am using Mandriva 2008. > cg> Installation is complete and I am able to compile, but I am getting a > cg> link error: "ld: No such file or directory". > cg> Fujitsu support are trying to help, but are a bit slow. > cg> Have any of you had luck getting Fujitsu's Linux compiler working on > cg> newer Linux distros? > > Having installed cobol have you run ldconfig ? > > If not do a man ldconfig and run it. > > Vince > > Thanks Vince, I will try ldconfig on Monday. LD_LIBRARY_PATH is set with pointers to NetCOBOL. The first suggestion from support was to add the location of my source to both LD_LIBRARY_PATH and PATH. |