From napa at it-np.de Mon Jan 2 19:30:14 2006 From: napa at it-np.de (Norbert Pausch) Date: Mon Jan 2 13:24:59 2006 Subject: [apluslist] aplus on slackware 9.1 Message-ID: <43B97F46.8020508@it-np.de> Hello, I'm trying to run aplus 4.18 on slackware 9.1. Loading stops with the follwing message: root@afuwe:/# /usr/local/bin/aplus-fsf-4.18/lib/a+ /usr/local/bin/aplus-fsf-4.18/lib/a+: error while loading shared libraries: libIPC.so.0: cannot open shared object file: No such file or directory root@afuwe:/# /usr/local/bin/aplus-fsf-4.18/bin/a+ /usr/local/bin/aplus-fsf-4.18/bin/a+: error while loading shared libraries: libIPC.so.0: cannot open shared object file: No such file or directory root@afuwe:/# ATREE=/usr/local/bin/aplus-fsf-4.18 root@afuwe:/# export ATREE root@afuwe:/# /usr/local/bin/aplus-fsf-4.18/bin/a+ /usr/local/bin/aplus-fsf-4.18/bin/a+: error while loading shared libraries: libIPC.so.0: cannot open shared object file: No such file or directory However the requested file libIPC.so.0 resides in the directory (I copied a+ executable to this driectory too, but this didn't help): What am I doing wrong? root@afuwe:/usr/local/bin/aplus-fsf-4.18/lib# ls a+* libMSIPC.la* libcxc.so.0.0.0* adap.+ libMSIPC.so@ libcxs.a apter.+ libMSIPC.so.0@ libcxs.la* bigs.+ libMSIPC.so.0.0.0* libcxs.so@ disp.+ libMSTypes.a libcxs.so.0@ fsftest.+ libMSTypes.la* libcxs.so.0.0.0* idap.+ libMSTypes.so@ libcxsys.a libAplusGUI.a libMSTypes.so.0@ libcxsys.la* libAplusGUI.la* libMSTypes.so.0.0.0* libcxsys.so@ libAplusGUI.so@ liba.a libcxsys.so.0@ libAplusGUI.so.0@ liba.la* libcxsys.so.0.0.0* libAplusGUI.so.0.0.0* liba.so@ libdap.a libIPC.a liba.so.0@ libdap.la* libIPC.la* liba.so.0.0.0* libdap.so@ libIPC.so@ libcxb.a libdap.so.0@ libIPC.so.0@ libcxb.la* libdap.so.0.0.0* libIPC.so.0.0.0* libcxb.so@ libesf.a libMSGUI.a libcxb.so.0@ libesf.la* libMSGUI.la* libcxb.so.0.0.0* libesf.so@ libMSGUI.so@ libcxc.a libesf.so.0@ libMSGUI.so.0@ libcxc.la* libesf.so.0.0.0* libMSGUI.so.0.0.0* libcxc.so@ s.+ libMSIPC.a libcxc.so.0@ From kutinskyv at obninsk.com Mon Jan 2 23:15:08 2006 From: kutinskyv at obninsk.com (Vladimir N. Kutinsky) Date: Mon Jan 2 15:15:01 2006 Subject: [apluslist] aplus on slackware 9.1 In-Reply-To: <43B97F46.8020508@it-np.de> Message-ID: <200601022014.k02KEvww044809@dolphin.obninsk.com> This error is generated with a Dynamic Linker that can't find at least one library. Im not sure but i think the problem lies in the location of aplus libraries (all aplus files, in fact), which is very unusual (/usr/local/bin/aplus..). When trying to load a library, the linker searches thru a number of known directories that contain shared libraries. If your directory (/usr/local/bin/aplus-fsf-4.18/lib) is not in the search path, the linker won't find the libs even if they are all there. Try to investigate it with the "ldd" utility that prints shared library dependencies for an executable (a+ resides in /usr/bin/ on my system): debian:/usr/bin# ldd a+ libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40027000) libIPC.so.0 => /usr/lib/libIPC.so.0 (0x400ee000) libcxs.so.0 => /usr/lib/libcxs.so.0 (0x4010d000) libcxb.so.0 => /usr/lib/libcxb.so.0 (0x4010f000) libAplusGUI.so.0 => /usr/lib/libAplusGUI.so.0 (0x40113000) libcxsys.so.0 => /usr/lib/libcxsys.so.0 (0x40270000) libcxc.so.0 => /usr/lib/libcxc.so.0 (0x4027c000) libesf.so.0 => /usr/lib/libesf.so.0 (0x40282000) liba.so.0 => /usr/lib/liba.so.0 (0x40296000) libdap.so.0 => /usr/lib/libdap.so.0 (0x403e7000) libMSGUI.so.0 => /usr/lib/libMSGUI.so.0 (0x403f8000) libMSIPC.so.0 => /usr/lib/libMSIPC.so.0 (0x4072d000) libMSTypes.so.0 => /usr/lib/libMSTypes.so.0 (0x4074f000) libpthread.so.0 => /lib/tls/libpthread.so.0 (0x40929000) libnsl.so.1 => /lib/tls/libnsl.so.1 (0x40939000) libdl.so.2 => /lib/tls/libdl.so.2 (0x4094d000) libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x40950000) libm.so.6 => /lib/tls/libm.so.6 (0x40a0a000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40a2c000) libc.so.6 => /lib/tls/libc.so.6 (0x40a35000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) In your case, you will probably see something like this: ... libIPC.so.0 => not found ... You can try to fix this problem by adding your directory to the search path. This can be done by editing "/etc/ld.so.conf" file that contains a list of directories where shared libraries can be found. Hope this helps, Vladimir > -----Original Message----- > From: apluslist-bounces@aplusdev.net [mailto:apluslist- > bounces@aplusdev.net] On Behalf Of Norbert Pausch > Sent: Monday, January 02, 2006 10:30 PM > To: apluslist@aplusdev.net > Subject: [apluslist] aplus on slackware 9.1 > > Hello, > > I'm trying to run aplus 4.18 on slackware 9.1. Loading stops with the > follwing message: > > root@afuwe:/# /usr/local/bin/aplus-fsf-4.18/lib/a+ > /usr/local/bin/aplus-fsf-4.18/lib/a+: error while loading shared > libraries: libIPC.so.0: cannot open shared object file: No such file or > directory > root@afuwe:/# /usr/local/bin/aplus-fsf-4.18/bin/a+ > /usr/local/bin/aplus-fsf-4.18/bin/a+: error while loading shared > libraries: libIPC.so.0: cannot open shared object file: No such file or > directory > root@afuwe:/# ATREE=/usr/local/bin/aplus-fsf-4.18 > root@afuwe:/# export ATREE > root@afuwe:/# /usr/local/bin/aplus-fsf-4.18/bin/a+ > /usr/local/bin/aplus-fsf-4.18/bin/a+: error while loading shared > libraries: libIPC.so.0: cannot open shared object file: No such file or > directory > > However the requested file libIPC.so.0 resides in the directory (I > copied a+ executable to this driectory too, but this didn't help): > What am I doing wrong? > > root@afuwe:/usr/local/bin/aplus-fsf-4.18/lib# ls > a+* libMSIPC.la* libcxc.so.0.0.0* > adap.+ libMSIPC.so@ libcxs.a > apter.+ libMSIPC.so.0@ libcxs.la* > bigs.+ libMSIPC.so.0.0.0* libcxs.so@ > disp.+ libMSTypes.a libcxs.so.0@ > fsftest.+ libMSTypes.la* libcxs.so.0.0.0* > idap.+ libMSTypes.so@ libcxsys.a > libAplusGUI.a libMSTypes.so.0@ libcxsys.la* > libAplusGUI.la* libMSTypes.so.0.0.0* libcxsys.so@ > libAplusGUI.so@ liba.a libcxsys.so.0@ > libAplusGUI.so.0@ liba.la* libcxsys.so.0.0.0* > libAplusGUI.so.0.0.0* liba.so@ libdap.a > libIPC.a liba.so.0@ libdap.la* > libIPC.la* liba.so.0.0.0* libdap.so@ > libIPC.so@ libcxb.a libdap.so.0@ > libIPC.so.0@ libcxb.la* libdap.so.0.0.0* > libIPC.so.0.0.0* libcxb.so@ libesf.a > libMSGUI.a libcxb.so.0@ libesf.la* > libMSGUI.la* libcxb.so.0.0.0* libesf.so@ > libMSGUI.so@ libcxc.a libesf.so.0@ > libMSGUI.so.0@ libcxc.la* libesf.so.0.0.0* > libMSGUI.so.0.0.0* libcxc.so@ s.+ > libMSIPC.a libcxc.so.0@ > > > > _______________________________________________ > apluslist mailing list > apluslist@aplusdev.net > http://aplusdev.net/mailman/listinfo/apluslist From neil at occamsrazor.net Mon Jan 2 15:44:00 2006 From: neil at occamsrazor.net (Neil Roeth) Date: Mon Jan 2 15:44:15 2006 Subject: [apluslist] aplus on slackware 9.1 In-Reply-To: <200601022014.k02KEvww044809@dolphin.obninsk.com> References: <43B97F46.8020508@it-np.de> <200601022014.k02KEvww044809@dolphin.obninsk.com> Message-ID: <17337.37008.692742.876536@ml330.occamsrazor.net> This should work, but you can also try setting the environment variable LD_LIBRARY_PATH, then running a+: export LD_LIBRARY_PATH=/usr/local/bin/aplus-fsf-4.18/lib On Jan 2, Vladimir N. Kutinsky (kutinskyv@obninsk.com) wrote: > > This error is generated with a Dynamic Linker that can't find at least one > library. Im not sure but i think the problem lies in the location of aplus > libraries (all aplus files, in fact), which is very unusual > (/usr/local/bin/aplus..). > When trying to load a library, the linker searches thru a number of known > directories that contain shared libraries. If your directory > (/usr/local/bin/aplus-fsf-4.18/lib) is not in the search path, the linker > won't find the libs even if they are all there. > > Try to investigate it with the "ldd" utility that prints shared library > dependencies for an executable (a+ resides in /usr/bin/ on my system): > debian:/usr/bin# ldd a+ > libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40027000) > libIPC.so.0 => /usr/lib/libIPC.so.0 (0x400ee000) > libcxs.so.0 => /usr/lib/libcxs.so.0 (0x4010d000) > libcxb.so.0 => /usr/lib/libcxb.so.0 (0x4010f000) > libAplusGUI.so.0 => /usr/lib/libAplusGUI.so.0 (0x40113000) > libcxsys.so.0 => /usr/lib/libcxsys.so.0 (0x40270000) > libcxc.so.0 => /usr/lib/libcxc.so.0 (0x4027c000) > libesf.so.0 => /usr/lib/libesf.so.0 (0x40282000) > liba.so.0 => /usr/lib/liba.so.0 (0x40296000) > libdap.so.0 => /usr/lib/libdap.so.0 (0x403e7000) > libMSGUI.so.0 => /usr/lib/libMSGUI.so.0 (0x403f8000) > libMSIPC.so.0 => /usr/lib/libMSIPC.so.0 (0x4072d000) > libMSTypes.so.0 => /usr/lib/libMSTypes.so.0 (0x4074f000) > libpthread.so.0 => /lib/tls/libpthread.so.0 (0x40929000) > libnsl.so.1 => /lib/tls/libnsl.so.1 (0x40939000) > libdl.so.2 => /lib/tls/libdl.so.2 (0x4094d000) > libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x40950000) > libm.so.6 => /lib/tls/libm.so.6 (0x40a0a000) > libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40a2c000) > libc.so.6 => /lib/tls/libc.so.6 (0x40a35000) > /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) > > In your case, you will probably see something like this: > ... > libIPC.so.0 => not found > ... > > You can try to fix this problem by adding your directory to the search path. > This can be done by editing "/etc/ld.so.conf" file that contains a list of > directories where shared libraries can be found. > > Hope this helps, > Vladimir > > > > -----Original Message----- > > From: apluslist-bounces@aplusdev.net [mailto:apluslist- > > bounces@aplusdev.net] On Behalf Of Norbert Pausch > > Sent: Monday, January 02, 2006 10:30 PM > > To: apluslist@aplusdev.net > > Subject: [apluslist] aplus on slackware 9.1 > > > > Hello, > > > > I'm trying to run aplus 4.18 on slackware 9.1. Loading stops with the > > follwing message: > > > > root@afuwe:/# /usr/local/bin/aplus-fsf-4.18/lib/a+ > > /usr/local/bin/aplus-fsf-4.18/lib/a+: error while loading shared > > libraries: libIPC.so.0: cannot open shared object file: No such file or > > directory > > root@afuwe:/# /usr/local/bin/aplus-fsf-4.18/bin/a+ > > /usr/local/bin/aplus-fsf-4.18/bin/a+: error while loading shared > > libraries: libIPC.so.0: cannot open shared object file: No such file or > > directory > > root@afuwe:/# ATREE=/usr/local/bin/aplus-fsf-4.18 > > root@afuwe:/# export ATREE > > root@afuwe:/# /usr/local/bin/aplus-fsf-4.18/bin/a+ > > /usr/local/bin/aplus-fsf-4.18/bin/a+: error while loading shared > > libraries: libIPC.so.0: cannot open shared object file: No such file or > > directory > > > > However the requested file libIPC.so.0 resides in the directory (I > > copied a+ executable to this driectory too, but this didn't help): > > What am I doing wrong? > > > > root@afuwe:/usr/local/bin/aplus-fsf-4.18/lib# ls > > a+* libMSIPC.la* libcxc.so.0.0.0* > > adap.+ libMSIPC.so@ libcxs.a > > apter.+ libMSIPC.so.0@ libcxs.la* > > bigs.+ libMSIPC.so.0.0.0* libcxs.so@ > > disp.+ libMSTypes.a libcxs.so.0@ > > fsftest.+ libMSTypes.la* libcxs.so.0.0.0* > > idap.+ libMSTypes.so@ libcxsys.a > > libAplusGUI.a libMSTypes.so.0@ libcxsys.la* > > libAplusGUI.la* libMSTypes.so.0.0.0* libcxsys.so@ > > libAplusGUI.so@ liba.a libcxsys.so.0@ > > libAplusGUI.so.0@ liba.la* libcxsys.so.0.0.0* > > libAplusGUI.so.0.0.0* liba.so@ libdap.a > > libIPC.a liba.so.0@ libdap.la* > > libIPC.la* liba.so.0.0.0* libdap.so@ > > libIPC.so@ libcxb.a libdap.so.0@ > > libIPC.so.0@ libcxb.la* libdap.so.0.0.0* > > libIPC.so.0.0.0* libcxb.so@ libesf.a > > libMSGUI.a libcxb.so.0@ libesf.la* > > libMSGUI.la* libcxb.so.0.0.0* libesf.so@ > > libMSGUI.so@ libcxc.a libesf.so.0@ > > libMSGUI.so.0@ libcxc.la* libesf.so.0.0.0* > > libMSGUI.so.0.0.0* libcxc.so@ s.+ > > libMSIPC.a libcxc.so.0@ > > > > > > > > _______________________________________________ > > apluslist mailing list > > apluslist@aplusdev.net > > http://aplusdev.net/mailman/listinfo/apluslist > > > _______________________________________________ > apluslist mailing list > apluslist@aplusdev.net > http://aplusdev.net/mailman/listinfo/apluslist -- Neil Roeth From napa at it-np.de Tue Jan 3 09:35:53 2006 From: napa at it-np.de (Norbert Pausch) Date: Tue Jan 3 03:30:31 2006 Subject: [apluslist] aplus on slackware 9.1 References: <43B97F46.8020508@it-np.de> <200601022014.k02KEvww044809@dolphin.obninsk.com> <17337.37008.692742.876536@ml330.occamsrazor.net> Message-ID: <43BA4579.9030000@it-np.de> Hello, thank you very much, the LD_LIBRARY_PATH variant works fine. I'll try the etc/ld.so.conf version as well. I'm an old APL'er coming from IBM APL2 on S390. Norbert Neil Roeth wrote: >This should work, but you can also try setting the environment variable >LD_LIBRARY_PATH, then running a+: > >export LD_LIBRARY_PATH=/usr/local/bin/aplus-fsf-4.18/lib > >On Jan 2, Vladimir N. Kutinsky (kutinskyv@obninsk.com) wrote: > > > > This error is generated with a Dynamic Linker that can't find at least one > > library. Im not sure but i think the problem lies in the location of aplus > > libraries (all aplus files, in fact), which is very unusual > > (/usr/local/bin/aplus..). > > When trying to load a library, the linker searches thru a number of known > > directories that contain shared libraries. If your directory > > (/usr/local/bin/aplus-fsf-4.18/lib) is not in the search path, the linker > > won't find the libs even if they are all there. > > > > Try to investigate it with the "ldd" utility that prints shared library > > dependencies for an executable (a+ resides in /usr/bin/ on my system): > > debian:/usr/bin# ldd a+ > > libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40027000) > > libIPC.so.0 => /usr/lib/libIPC.so.0 (0x400ee000) > > libcxs.so.0 => /usr/lib/libcxs.so.0 (0x4010d000) > > libcxb.so.0 => /usr/lib/libcxb.so.0 (0x4010f000) > > libAplusGUI.so.0 => /usr/lib/libAplusGUI.so.0 (0x40113000) > > libcxsys.so.0 => /usr/lib/libcxsys.so.0 (0x40270000) > > libcxc.so.0 => /usr/lib/libcxc.so.0 (0x4027c000) > > libesf.so.0 => /usr/lib/libesf.so.0 (0x40282000) > > liba.so.0 => /usr/lib/liba.so.0 (0x40296000) > > libdap.so.0 => /usr/lib/libdap.so.0 (0x403e7000) > > libMSGUI.so.0 => /usr/lib/libMSGUI.so.0 (0x403f8000) > > libMSIPC.so.0 => /usr/lib/libMSIPC.so.0 (0x4072d000) > > libMSTypes.so.0 => /usr/lib/libMSTypes.so.0 (0x4074f000) > > libpthread.so.0 => /lib/tls/libpthread.so.0 (0x40929000) > > libnsl.so.1 => /lib/tls/libnsl.so.1 (0x40939000) > > libdl.so.2 => /lib/tls/libdl.so.2 (0x4094d000) > > libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x40950000) > > libm.so.6 => /lib/tls/libm.so.6 (0x40a0a000) > > libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40a2c000) > > libc.so.6 => /lib/tls/libc.so.6 (0x40a35000) > > /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) > > > > In your case, you will probably see something like this: > > ... > > libIPC.so.0 => not found > > ... > > > > You can try to fix this problem by adding your directory to the search path. > > This can be done by editing "/etc/ld.so.conf" file that contains a list of > > directories where shared libraries can be found. > > > > Hope this helps, > > Vladimir > > > > > > > -----Original Message----- > > > From: apluslist-bounces@aplusdev.net [mailto:apluslist- > > > bounces@aplusdev.net] On Behalf Of Norbert Pausch > > > Sent: Monday, January 02, 2006 10:30 PM > > > To: apluslist@aplusdev.net > > > Subject: [apluslist] aplus on slackware 9.1 > > > > > > Hello, > > > > > > I'm trying to run aplus 4.18 on slackware 9.1. Loading stops with the > > > follwing message: > > > > > > root@afuwe:/# /usr/local/bin/aplus-fsf-4.18/lib/a+ > > > /usr/local/bin/aplus-fsf-4.18/lib/a+: error while loading shared > > > libraries: libIPC.so.0: cannot open shared object file: No such file or > > > directory > > > root@afuwe:/# /usr/local/bin/aplus-fsf-4.18/bin/a+ > > > /usr/local/bin/aplus-fsf-4.18/bin/a+: error while loading shared > > > libraries: libIPC.so.0: cannot open shared object file: No such file or > > > directory > > > root@afuwe:/# ATREE=/usr/local/bin/aplus-fsf-4.18 > > > root@afuwe:/# export ATREE > > > root@afuwe:/# /usr/local/bin/aplus-fsf-4.18/bin/a+ > > > /usr/local/bin/aplus-fsf-4.18/bin/a+: error while loading shared > > > libraries: libIPC.so.0: cannot open shared object file: No such file or > > > directory > > > > > > However the requested file libIPC.so.0 resides in the directory (I > > > copied a+ executable to this driectory too, but this didn't help): > > > What am I doing wrong? > > > > > > root@afuwe:/usr/local/bin/aplus-fsf-4.18/lib# ls > > > a+* libMSIPC.la* libcxc.so.0.0.0* > > > adap.+ libMSIPC.so@ libcxs.a > > > apter.+ libMSIPC.so.0@ libcxs.la* > > > bigs.+ libMSIPC.so.0.0.0* libcxs.so@ > > > disp.+ libMSTypes.a libcxs.so.0@ > > > fsftest.+ libMSTypes.la* libcxs.so.0.0.0* > > > idap.+ libMSTypes.so@ libcxsys.a > > > libAplusGUI.a libMSTypes.so.0@ libcxsys.la* > > > libAplusGUI.la* libMSTypes.so.0.0.0* libcxsys.so@ > > > libAplusGUI.so@ liba.a libcxsys.so.0@ > > > libAplusGUI.so.0@ liba.la* libcxsys.so.0.0.0* > > > libAplusGUI.so.0.0.0* liba.so@ libdap.a > > > libIPC.a liba.so.0@ libdap.la* > > > libIPC.la* liba.so.0.0.0* libdap.so@ > > > libIPC.so@ libcxb.a libdap.so.0@ > > > libIPC.so.0@ libcxb.la* libdap.so.0.0.0* > > > libIPC.so.0.0.0* libcxb.so@ libesf.a > > > libMSGUI.a libcxb.so.0@ libesf.la* > > > libMSGUI.la* libcxb.so.0.0.0* libesf.so@ > > > libMSGUI.so@ libcxc.a libesf.so.0@ > > > libMSGUI.so.0@ libcxc.la* libesf.so.0.0.0* > > > libMSGUI.so.0.0.0* libcxc.so@ s.+ > > > libMSIPC.a libcxc.so.0@ > > > > > > > > > > > > _______________________________________________ > > > apluslist mailing list > > > apluslist@aplusdev.net > > > http://aplusdev.net/mailman/listinfo/apluslist > > > > > > _______________________________________________ > > apluslist mailing list > > apluslist@aplusdev.net > > http://aplusdev.net/mailman/listinfo/apluslist > > > From agoyal at coverity.com Thu Jan 19 10:37:25 2006 From: agoyal at coverity.com (Anuj Goyal) Date: Thu Jan 19 13:38:03 2006 Subject: [apluslist] Coverity found 186 potential errors in 4.20 Message-ID: <43CFDC65.50503@coverity.com> Would Morgan Stanley be interested in a free trial to discuss the results? We would leave behind a subset of the bugs that we found in the free trial. I understand that A++ is an important part of Morgan Stanleys' technology infrastructure. We are entering the financial sector and would like to be used by every important application. What software quality tools are you using internally? Do you have any C/C++ code that constantly crashes and can't figure out why? Static source code analysis may be able to find the bug. Analysis summary report: ------------------------ Files analyzed : 1093 Functions analyzed : 18953 Classes/structs analyzed : 1670 Paths analyzed : 416305 New defects found : 186 Total 2 CHECKED_RETURN 13 DEADCODE 2 DELETE_ARRAY 27 FORWARD_NULL 9 NEGATIVE_RETURNS 3 NULL_RETURNS 17 OVERRUN_STATIC 11 RESOURCE_LEAK 16 REVERSE_INULL 29 UNINIT 48 UNUSED_VALUE 9 USE_AFTER_FREE Anuj Goyal Sr. Sales Engineer Coverity, Inc. 185 Berry St., Suite 3600 San Francisco, CA 94107 Email: agoyal@coverity.com Static source analysis involves looking at the source, running it through our frontend compiler and analyzing the call graph. If you want more information you can email me off this list. I assume that everyone on this list is technical and understands a little bit about it. There are no changes to your build tree and the analysis took about 35 min on an old linux box. Here are some linux bugs that we found: http://linuxbugs.coverity.com http://www.kernel.org/git/?p=linux%2Fkernel%2Fgit%2Ftorvalds%2Flinux-2.6.git&a=search&h=HEAD&s=coverity Here is our customer list. http://www.coverity.com/customers/ From wbs at infowest.com Sat Jan 21 15:48:16 2006 From: wbs at infowest.com (Lorin Lund) Date: Sat Jan 21 17:48:34 2006 Subject: [apluslist] few errors when compiling on FreeBSD 6.0 Message-ID: <43D2BA30.4030107@infowest.com> I found some ifdefs that referenced __FreeBSD. I had to change them to __FreeBSD__. Even though nosunos4.h attempts to define howmany() it doesn't get defined for FreeBSD. Also, there was an instance of howmany() in a source file that didn't include nosunos4.h. From wbs at infowest.com Mon Feb 6 14:36:20 2006 From: wbs at infowest.com (Lorin Lund) Date: Mon Feb 6 16:36:44 2006 Subject: [apluslist] Does A+ utilize multiple processors when they are available? In-Reply-To: <43D2BA30.4030107@infowest.com> References: <43D2BA30.4030107@infowest.com> Message-ID: <43E7C154.6060008@infowest.com> Whereas A+ is an array processing language it would be nice if it could transparently harness multiple processors (in an SMP box). Is this capability currently available? From oitzinger at opec.org Mon Feb 13 09:56:00 2006 From: oitzinger at opec.org (Itzinger, Oskar) Date: Mon Feb 13 03:56:19 2006 Subject: [apluslist] A+ 4.20-2 runtime problem... Message-ID: <2AE27CD8C00C3540AF5DCEBE6C3D020B01309E9B@opecexch1.opec.org> Hi, there... Having fixed some errors in the source of A+ 4.20-2, I got it finally to build the binary (under IRIX 6.5.28/MipsPro 7.4.4). However, running a+ produces only the following errors (I'd no such problems with 4.18) - how can I get rid of them??? Thanks much. /oskar 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: doWrite__31MSProtocolConnection__pt__4_P1aGv 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: writeReset__31MSProtocolConnection__pt__4_P1aGv 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: doReadBurst__31MSProtocolConnection__pt__4_P1aGv 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: doWrite__31MSProtocolConnection__pt__4_P1aG9MSBoolean 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: setup__31MSProtocolConnection__pt__4_P1aGv 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: establish__31MSProtocolConnection__pt__4_P1aGv 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: cleanup__31MSProtocolConnection__pt__4_P1aGv 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: syncRead__31MSProtocolConnection__pt__4_P1aGRP1ad 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: __dt__31MSProtocolConnection__pt__4_P1aGv 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: sendTheBuffer__31MSProtocolConnection__pt__4_P1aGP8MSBuffer 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: readTheBuffer__31MSProtocolConnection__pt__4_P1aGP8MSBufferi 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: syncErrorReport__31MSProtocolConnection__pt__4_P1aGv 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: doSyncWrite__31MSProtocolConnection__pt__4_P1aGv 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: writeTheBuffer__31MSProtocolConnection__pt__4_P1aGP8MSBufferi 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: syncSend__31MSProtocolConnection__pt__4_P1aGRCP1aiT29MSBoolean 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: syncSend__31MSProtocolConnection__pt__4_P1aGRCP1ad 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: syncRead__31MSProtocolConnection__pt__4_P1aGRP1aiT29MSBoolean 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: doSyncRead__31MSProtocolConnection__pt__4_P1aGRP1a 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: __T_31MSProtocolConnection__pt__4_P1a 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libIPC.so.1: doRead__31MSProtocolConnection__pt__4_P1aGv 604582:./a+: rld: Error: unresolvable symbol in /disk03/mephisto/languages/aplus/aplus-fsf-4.20-2-src/lib/libAplusGUI.so .1: __dt__70MSTabularTree__pt__49_Q2_34MSTreeView__pt__16_13AplusTreeItem8Tr eeNodeGv 604582:./a+: rld: Fatal Error: this executable has unresolvable symbols -------------- next part -------------- An HTML attachment was scrubbed... URL: http://berdom.net/pipermail/apluslist/attachments/20060213/f59fdaa0/attachment.html From neil at occamsrazor.net Mon Feb 13 06:51:35 2006 From: neil at occamsrazor.net (Neil Roeth) Date: Mon Feb 13 06:51:42 2006 Subject: [apluslist] A+ 4.20-2 runtime problem... In-Reply-To: <2AE27CD8C00C3540AF5DCEBE6C3D020B01309E9B@opecexch1.opec.org> References: <2AE27CD8C00C3540AF5DCEBE6C3D020B01309E9B@opecexch1.opec.org> Message-ID: <17392.29383.561304.705248@ml330.occamsrazor.net> On Feb 13, Itzinger, Oskar (oitzinger@opec.org) wrote: > Hi, there... > > Having fixed some errors in the source of A+ 4.20-2, I got it finally to > build the binary (under IRIX 6.5.28/MipsPro 7.4.4). > > However, running a+ produces only the following errors (I'd no such > problems with 4.18) - how can I get rid of them??? > > Thanks much. > /oskar > [snip] It would help to know the changes you made and the compiler you are using. If not g++, can you try g++, version 4.0? -- Neil Roeth From oitzinger at opec.org Mon Feb 27 10:06:10 2006 From: oitzinger at opec.org (Itzinger, Oskar) Date: Mon Feb 27 04:06:36 2006 Subject: [apluslist] Random link problem Message-ID: <2AE27CD8C00C3540AF5DCEBE6C3D020B013D79F8@opecexch1.opec.org> In all APLs I'd worked with [Sharp APL, APL*PLUS, APL2], quad-RL could be referenced, but, according to the reference manual, in A+ `rl cannot. Since I've a program which does a random search and runs maybe a couple of days before it hits on something I'm looking for, I'd like to be able to get somehow the value of `rl at that time so that I could restart the search just from there on, and I don't have to repeat the whole run first... Am I missing something or can't it really just not be done? Thanks. /oskar -------------- next part -------------- An HTML attachment was scrubbed... URL: http://berdom.net/pipermail/apluslist/attachments/20060227/4f47466a/attachment.html From kutinskyv at obninsk.com Mon Feb 27 12:39:16 2006 From: kutinskyv at obninsk.com (Vladimir N. Kutinsky) Date: Mon Feb 27 04:39:00 2006 Subject: [apluslist] Random link problem In-Reply-To: <2AE27CD8C00C3540AF5DCEBE6C3D020B013D79F8@opecexch1.opec.org> Message-ID: <200602270938.k1R9cvsi045933@dolphin.obninsk.com> Oskar, If I get you right, your problem can be solved using both a random-link variable (`rl) and a random-link command ($rl). Here's an example: myRL<-`rl $rl myRL ?10 10 10 3 6 7 $rl myRL ?10 10 10 3 6 7 ?10 10 10 5 3 5 Hope this helps, Vladimir ________________________________________ From: apluslist-bounces@aplusdev.net [mailto:apluslist-bounces@aplusdev.net] On Behalf Of Itzinger, Oskar Sent: Monday, February 27, 2006 12:06 PM To: apluslist@aplusdev.net Subject: [apluslist] Random link problem In all APLs I'd worked with [Sharp APL, APL*PLUS, APL2], quad-RL could be referenced, but, according to the reference manual, in A+ `rl cannot. ? Since I've a program which does a random search and runs maybe a couple of days before it hits on something I'm looking for, I'd like to be able to get somehow the value of `rl at that time so that I could restart the search just from there on, and I don't have to repeat the whole run first... ? Am I missing something or can't it really just not be done? ? Thanks. /oskar ?