NWRFCSDK causing issue with Ubuntu 12.10, 13.04 and Mac Mavericks - ruby-on-rails

For our project we want to communicate with SAP and for that we are planning to use following:
RUBY1.9, sapnwrfc gem and NWRFCSDK
We have download the Linux x86_64 bit version of NWRFCSDK. As Ubuntu and Mac both works on Linux and Unix base operating system. We have expected that 'nwrfcsdk' will work with the above mentioned OSes.
During installation process we have followed these steps:
`
ruby setup.rb config --with-nwrfcsdk-dir=/usr/sap/nwrfcsdk
ruby setup.rb setup`
We are getting various errors. In Ubuntu when we run ruby setup.rb config command it fails.
Whereas in Mac it completes the Config command execution, however it fails on SETUP step and it shows this error
setup.rb:658: warning: Insecure world writable dir /usr/local in PATH, mode 040777
linking shared-object nwsaprfc.bundle
ld: warning: ignoring file /usr/sap/nwrfcsdk/lib/libsapucum.so, file was built for unsupported file format which is not the architecture being linked (x86_64)
ld: warning: ignoring file /usr/sap/nwrfcsdk/lib/libsapnwrfc.so, file was built for unsupported file format which is not the architecture being linked (x86_64)`
We have tried all possible ways and problem is coming with libsap files. Because it creates a nwrfcsdk.bundle for ruby which application is not able to load due to failure of libsapucum.so and libsapnwrfc.so

We got confirmation from the SAP team that they do not support Mac OSX and that is the reason it is not working in Mavericks.
However to make it work in Ubuntu 32bit we have got the other installer and that worked perfectly for the Ubuntu.
NWRFCSDK for 32 bit, SAP RFC SDK 6.40 Linux on IA32 32bit
I hope this will help others.

Related

compatibility problem between FEniCS and Paraview on Mac

I am using FEniCS on mac trough Docker but I have a problem visualizing the result of an analysis using a Paraview version installed on mac. These are the steps I follow:
I obtain the solution of my problem using FEniCS; then send the .vtu file that FEniCS has generated from Docker to the desktop using
sudo docker cp fenics-container:/home/fenics/shared/nameoffile.vtu Users/User/Desktop
Subsequently, I open ParaView (which I directly installed on my mac and not on Docker) and open the file nameoffile.vtu. I press Apply and then an error appears:
ERROR: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/VTK/IO/XML/vtkXMLUnstructuredDataReader.cxx, line 649
vtkXMLUnstructuredGridReader (0x7fc30ff7c440): Error reading cell offsets: Unsupported array type: vtkUnsignedIntArray
Can anyone explain what this error means?
when I tried open the file using Paraview on a Linux machine it worked just fine with no error. Am I missing some compatibility package?
Solved.
I installed a previous version of ParaView. Apparently latest ones are not fully compatible with all versions of FEniCS

Freeradius running debug mode libssl version mismatch

I'm trying to build and install Freeradius version 3.0.8 using these instructions. But after starting Freeradius in debug mode using command radiusd -X shows following error.
libssl version mismatch. built: 1000207f linked: 1000114f
I tried removing libssl-dev and reinstall, But no luck.
Appreciate any help to resolve this version mismatch error. My os is Ubuntu 16.4
If you're building/installing on the same server you have multiple versions of OpenSSL installed. When you built the server it found version 1.0.2, when the server runs however, it's linked against 1.0.1. The server refuses to start because 1.0.2 and 1.0.1 are ABI incompatible and allowing the server to start may cause subtle errors in any code that called OpenSSL.
As a workaround you can use the LD_PRELOAD environmental variable to specify the path to OpenSSL 1.0.2.
If you're building/installing on two different systems you must ensure both systems have the same version of OpenSSL.

PyScripter always says: "Python could not be properly initialized. We must quit."

I've googled for a solution, and based on that, let me report a few details:
I've tried 32-bit PyScripter-v2.6.0-Setup.exe with 32-bit python-3.6.1.exe; and 64-bit PyScripter-v2.6.0-x64-Setup.exe with 64-bit python-3.6.1-amd64-webinstall.exe.
I'm on a 64-bit Windows 10 machine.
I uninstalled other versions of Python on the machine.
Tried unzipping rpyc in the \Lib\ folder, as someone suggested that here.
What else should I be looking at?
Here is a tested Solution
Remove old PyScripter
Install Python from Python website. I installed mine from:
http://www.python.org/ftp/python/3.3.2/python-3.3.2.amd64.msi (and it worked)
Now install PyScripter-v2.6.0-x64-Setup.exe from https://sourceforge.net/projects/pyscripter/files/
This should solve the problem.
I got this solution from https: //github.com/pyscripter/pyscripter/issues/715
You are using an old version of Pyscripter. Version 3.4 from https://sourceforge.net/projects/pyscripter/ provides support for all released python versions, virtual environments, conda distibutions and the ability to switch between them without exiting Pyscripter.

Can't install Phidgets ROS driver

I have installed the Phidgets libraries following the following link and the "Hello World" example was working, but when I install the Phidgets ROS driver, I get this error:
fatal error: libphidgets/phidget21.h: No such file or directory compilation terminated.
What's causing this? The libraries have been installed by the Linux driver, right?
Phidgets, in their infinite wisdom desired to abandon the "phidget21" architecture and now have a completely different and incompatible phidgets22 driver architecture. When you installed the libraries from their web site, you can only get the version 22 driver architecture :( -- hint, version 21 is still out there on GitHub, so if you go find it, download and install everything should work as expected. Someone will need to migrate all the ROS code to the newer version 22 architecture for this to work as expected.

In cxfreeze, can I specify the python version I want the executable to use?

Situation:
In my Mac Os 10.8.5 I have available python2.7 and python2.7-32 with latest cx_freeze(-4.3.2).
I need cx_freeze to pick the python2.7-32 version so my executable app can use a 32-bit version of OpenCV.
So far, all attempts to use cx_freeze script suggest that it bundles python2.7(which is 64bit) and the app fails to execute with: "cv2.so: mach-o, but wrong architecture"
(This is the same error you would get if you try to import OpenCV built in 32 bits, with a python interpreter of 64)
Is there a way to "force" cxfreeze to bundle a specific python version installed (in this case python2.7-32) in the executable it produces?
Edit:
I've also tried to build cx-freeze from source in 32-bit using:
python2.7-32 setup.py build;
python2.7-32 setup.py install
No matter what, the app generated is still a 64bit version:
$ python2.7-32 setup.py bdist_dmg
$ file capturebasic
capturebasic: Mach-O 64-bit executable x86_64
$ arch -i386 ./capturebasic
arch: posix_spawnp: ./capturebasic: Bad CPU type in executable
Edit2:
It seems that Mac's cx_freeze you download from sourceforge is only 64-bit:
http://sourceforge.net/projects/cx-freeze/files/4.3.2/
If you want to create 32-bit apps, you need the 32-bit version of cx_freeze.
I'm confirming if there's any way to install the 32bit version in Mac in cx_freeze's mailing list.
I believe you do not have to touch your setup script, but just change the command used to build it. For instance instead of using python setup.py build, you would use the command python2.7-32 setup.py build. You may have to specify the path to the python2.7-32 exe. so something like path\to\python2.7-32.exe setup.py build. Note: I use windows so the example commands I used might be a little different on mac, like instead of .exe it's .app.
Hope this helped.

Resources