Search Results

Search found 3 results on 1 pages for 'footy'.

Page 1/1 | 1 

• playonlinux is unable to find 32bits / 64bits OpenGL library

  - by footy

  When I open a fresh instalation of playonlinux, it gives 2 dialog box as mentioned in title: playonlinux is unable to find 32bits OpenGL library playonlinux is unable to find 64bits OpenGL library I am using Ubuntu 12.04 (and new to it) and would like to know how to solve this problem EDIT TERMINAL OUTPUT ~$ playonlinux [main] Message: PlayOnLinux (4.1.8) is starting [clean_tmp] Message: Cleaning temp directory Xlib: extension "GLX" missing on display ":0". Xlib: extension "GLX" missing on display ":0". [Check_OpenGL] Warning: Xlib: extension "GLX" missing on display ":0". Xlib: extension "GLX" missing on display ":0". [Check_OpenGL] Warning: [main] Message: Filesystem is compatible [install_plugins] Message: Checking plugin: Capture... [maj_check] Message: Web version : 1349866727 [maj_check] Message: Current local version : 1349563245 [maj_check] Message: Updating list [install_plugins] Message: Checking plugin: ScreenCap... [install_plugins] Message: Checking plugin: PlayOnLinux Vault... /usr/share/playonlinux/bash/startup_after_server: line 38: [: : integer expression expected /usr/share/playonlinux/bash/startup_after_server: line 38: [: : integer expression expected [POL_Config_Write] Message: Config write: LAST_TIMESTAMP 1349866727

  Read the article

• Error while compiling Hello world program for CUDA

  - by footy

  I am using Ubuntu 12.10 and have sucessfully installed CUDA 5.0 and its sample kits too. I have also run sudo apt-get install nvidia-cuda-toolkit Below is my hello world program for CUDA: #include <stdio.h> /* Core input/output operations */ #include <stdlib.h> /* Conversions, random numbers, memory allocation, etc. */ #include <math.h> /* Common mathematical functions */ #include <time.h> /* Converting between various date/time formats */ #include <cuda.h> /* CUDA related stuff */ __global__ void kernel(void) { } /* MAIN PROGRAM BEGINS */ int main(void) { /* Dg = 1; Db = 1; Ns = 0; S = 0 */ kernel<<<1,1>>>(); /* PRINT 'HELLO, WORLD!' TO THE SCREEN */ printf("\n Hello, World!\n\n"); /* INDICATE THE TERMINATION OF THE PROGRAM */ return 0; } /* MAIN PROGRAM ENDS */ The following error occurs when I compile it with nvcc -g hello_world_cuda.cu -o hello_world_cuda.x /tmp/tmpxft_000033f1_00000000-13_hello_world_cuda.o: In function `main': /home/adarshakb/Documents/hello_world_cuda.cu:16: undefined reference to `cudaConfigureCall' /tmp/tmpxft_000033f1_00000000-13_hello_world_cuda.o: In function `__cudaUnregisterBinaryUtil': /usr/include/crt/host_runtime.h:172: undefined reference to `__cudaUnregisterFatBinary' /tmp/tmpxft_000033f1_00000000-13_hello_world_cuda.o: In function `__sti____cudaRegisterAll_51_tmpxft_000033f1_00000000_4_hello_world_cuda_cpp1_ii_b81a68a1': /tmp/tmpxft_000033f1_00000000-1_hello_world_cuda.cudafe1.stub.c:1: undefined reference to `__cudaRegisterFatBinary' /tmp/tmpxft_000033f1_00000000-1_hello_world_cuda.cudafe1.stub.c:1: undefined reference to `__cudaRegisterFunction' /tmp/tmpxft_000033f1_00000000-13_hello_world_cuda.o: In function `cudaError cudaLaunch<char>(char*)': /usr/lib/nvidia-cuda-toolkit/include/cuda_runtime.h:958: undefined reference to `cudaLaunch' collect2: ld returned 1 exit status I am also making sure that I use gcc and g++ version 4.4 ( As 4.7 there is some problem with CUDA)

  Read the article

• Function behaviour on shell(ksh) script

  - by footy

  Here are 2 different versions of a program: this Program: #!/usr/bin/ksh printmsg() { i=1 print "hello function :)"; } i=0; echo I printed `printmsg`; printmsg echo $i Output: # ksh e I printed hello function :) hello function :) 1 and Program: #!/usr/bin/ksh printmsg() { i=1 print "hello function :)"; } i=0; echo I printed `printmsg`; echo $i Output: # ksh e I printed hello function :) 0 The only difference between the above 2 programs is that printmsg is 2times in the above program while printmsg is called once in the below program. My Doubt arises here: To quote Be warned: Functions act almost just like external scripts... except that by default, all variables are SHARED between the same ksh process! If you change a variable name inside a function.... that variable's value will still be changed after you have left the function!! But we can clearly see in the 2nd program's output that the value of i remains unchanged. But we are sure that the function is called as the print statement gets the the output of the function and prints it. So why is the output different in both?

  Read the article

1