I am recompiling some cython files in python 3.7 that I was used to compile with python 2.7.x For some reasons I ignore, compiled files are now ending with .cpython-37m-darwin.so instead of .so simply.
any explanation for that ? can i avoid having this extra .cpython-37m-darwin
thanks
Related
I'm attempting to get some code running in Google Cloud Functions with the Python 3.7 runtime. Function deploy is failing when I include scipy in my requirements.txt. I'm guessing this is because scipy contains C code that needs compilation, but I can't find anything in the documentation about support for code compilation.
Do all of dependencies have to be pure-python code? If so, would it be possible to include a binary version of the lib instead?
I am trying to generate a standalone executable from a single tcl file. I am using the method using tclkit.exe mentioned in http://wiki.tcl.tk/11861.
The problem is the tcl file uses 3 packages.
package require Tk
package require tcom
package require Img
I was not able to successfully add the packages in lib folder of the generated vfs folder. Whenever I click the exe it says, failed to load tcom.dll.
Btw, there are lot of different version of activestate tcl and tclkit.exe based on x86 and x64 system. I am doing the whole thing in a 64 bit win7 system. What am I doing wrong? please help.
I have installed Octave 3.6.1 along with packages including "signal 1.1.2" but when i run a simple example of "sigmoid_train" function an error appears "sigmoid_train function is undefined".
Can any body tell me what is the problem?
The problem is that you didn't load the signal package. When you type pkg list you can find which ones are loaded by an asterisk in front of their names. Load a package with pkg load signal.
Having to load a packages is that thing that many users coming from Matlab find strange but if you compare with other languages, such as Python, Perl, or C++, would you expect them to import, use, or #include every libraries available in the system by default? See Octave's FAQ for more details.
If you want a package to be loaded automatically by default, the recommended action is to add the line pkg load signal to your ~/.octaverc file.
Finally, you have just started with Octave, you should had installed Octave 3.8.1.
I would like to generate the header dependencies for my CUDA source files to include it into a makefile.
I tried to use the following code:
g++ -MM my_cuda_file.cu
This is working for .cpp and for .h files, but for .cu files I just get the following error:
g++: warning: my_cuda_file.cu: linker input file unused because linking not done
How can I make it work?
I tried the following codes too, but neither of them working:
nvcc -MM my_cuda_file.cu
nvcc -Xcompiler "-MM" my_cuda_file.cu
Quoting the CUDA compiler driver nvcc reference guide:
2.4. Supported Phases
make dependency generation `-M`
3.2.1. Options for Specifying the Compilation Phase
--generate-dependencies -M Generate for the one .c/.cc/.cpp/.cxx/.cu
input file (more than one are not allowed
in this step) a dependency file that can
be included in a make file.
3.2.2. File and Path Specifications
--output-directory -odir Specify the directory of the output file.
This option is intended for letting the
dependency generation step (--generate-dependencies)
generate a rule that defines the target
object file in the proper directory.
3.2.5. Options for Guiding the Compiler Driver
--dependency-drive-prefix -ddp On Windows platforms, when generating
dependency files (option -M), all file names
must be converted to whatever the used
instance of make will recognize. Some
instances of make have trouble with the
colon in absolute paths in native Windows
format, which depends on the environment in
which this make instance has been compiled.
Use -ddp /cygwin/ for a CygWin make, and -ddp /
for Mingw. Or leave these file names in native
Windows format by specifying nothing.
In Chapter 5 of that guide you could find some usage examples.
I went forward and compiled an existing c code via llvm-gcc -emit-llvm -c to llvm bitcode. The c program consisted of four modules which I built to one big bitcode each via llvm-ld. Then I tried to merge these 4 bitcode files to one via llvm-ld GE.bc GA.bc SD.bc SH.bc -o prog which works without complaint.
Trying to execute the bitcode though it complains:
LLVM ERROR: Program used external function 'myFunction' which could not be resolved!
The thing is myFunction should be defined in SD.bc and used also in GA.bc.
But it's not to find in SD.bc - does llvm-ld skip all definitions that are not used!?
My OS is Linux and I use llvm version 2.6.
As a note llvm is on version 2.9 with 3.0 approaching. You should really upgrade.