openSUSE Programming December 2011

programming@lists.opensuse.org

5 participants
3 discussions

[opensuse-programming] Bayer Pattern image -> RGB -> Display
by Roger Oberholtzer 20 Dec '11

20 Dec '11

I will be collecting Bayer Pattern images from firewire cameras on an openSUSE 12.1 system. These systems have Nvidia GT520 (ASUS) graphics cards, and 1 GB of DDR3 memory. I am curious if anyone has used used the nvidia compiler to run code in the GPU on such a system. I have seen info (such as http://visionexperts.blogspot.com/2010/06/gpu-5x5-bayer-conversion.html) that is interesting. Is the nvidia app that I have seen floating about for openSUSE the tool for doing this sort of thing? I would like to show the resulting image in the application (in an X widget), as well as encode it to a disk file. Any openSUSE-specific pointers are welcome. Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer(a)ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-programming+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-programming+owner(a)opensuse.org

2 1

[opensuse-programming] perl expert needed
by Greg Freemyer 16 Dec '11

16 Dec '11

All, I've spent several hours on this, but it is apparently more involved than I can handle. = I have a perl app I want to send to factory, but it depends on perl(Net::Pcap). Which means I need to push perl-Net-Pcap to factory first. As it turns out perl(Net::Pcap) fails to build for i586 for both 12.1 and Factory. I'm looking for help (or a new volunteer maintainer) in getting it to build. Note the package builds fine for 64-bit, and it builds fine for older versions of openSUSE. It's just newer 32-bit versions that fail. For the original package see https://build.opensuse.org/package/show?package=perl-Net-Pcap&project=devel… I branched it to see if I could figure it out. In particular in my local spec file I added a couple "ls" commands just before Makefile.PL is called in the specfile. And the results look right to me: ============== + ls -l /usr/lib/libpcap* -rw-r--r-- 1 root root 350862 Dec 16 01:43 /usr/lib/libpcap.a lrwxrwxrwx 1 root root 12 Dec 16 01:49 /usr/lib/libpcap.so -> libpcap.so.1 lrwxrwxrwx 1 root root 16 Dec 16 01:49 /usr/lib/libpcap.so.1 -> libpcap.so.1.2.0 -rwxr-xr-x 1 root root 262144 Dec 16 01:43 /usr/lib/libpcap.so.1.2.0 + ls -l /usr/include/pcap* -rw-r--r-- 1 root root 2393 Dec 16 01:43 /usr/include/pcap-bpf.h -rw-r--r-- 1 root root 2125 Dec 16 01:43 /usr/include/pcap-namedb.h -rw-r--r-- 1 root root 2320 Dec 16 01:43 /usr/include/pcap.h /usr/include/pcap: total 88 -rw-r--r-- 1 root root 2016 Dec 16 01:43 bluetooth.h -rw-r--r-- 1 root root 35591 Dec 16 01:43 bpf.h -rw-r--r-- 1 root root 2272 Dec 16 01:43 ipnet.h -rw-r--r-- 1 root root 3421 Dec 16 01:43 namedb.h -rw-r--r-- 1 root root 16920 Dec 16 01:43 pcap.h -rw-r--r-- 1 root root 5563 Dec 16 01:43 sll.h -rw-r--r-- 1 root root 4659 Dec 16 01:43 usb.h -rw-r--r-- 1 root root 2151 Dec 16 01:43 vlan.h =============== But immediately following that I get: =========== + /usr/bin/perl Makefile.PL PREFIX=/usr looking for -lpcap... - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - You appear to lack the pcap(3) library. If it is installed in a non-standard location, please try setting the LIBS and INC values on the command line. Or get the sources and install the pcap library from http://www.tcpdump.org/ If you install the pcap library using a system package, make sure to also install the corresponding -devel package, which contains the C headers needed to compile this module. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ============================ Looking at Makefile.PL, the problem seems to be in: ================================================ sub have_library { my ($lib, $func, $header) = (@_, 'blank', 'blank'); printf("checking for %s() in -l%s... ", $func, $lib) if $func ne 'blank'; printf("looking for -l%s... ", $lib) if $func eq 'blank'; $header = $lib if $header eq 'blank'; my $result; # try to find a specific function in the library if ($func ne 'blank') { my $libs = $is_Win32 ? " $lib.lib " : "-l$lib"; if ($is_Win32) { $result = try_link(<<"SRC",undef ); #ifdef _CYGWIN #include <windows.h> #endif #include <${header}.h> blank() { return 0; } int t() { ${func}(); return 0; } SRC unless ($result) { $result = try_link(<<"SRC", undef); #ifdef _CYGWIN #include <windows.h> #endif #include <${header}.h> blank() { return 0; } int t() { void ((*p)()); p = (void ((*)()))${func}; return 0; } SRC } } else { $result = try_link(<<"SRC", undef); #include <${header}.h> blank() { return 0; } int t() { ${func}(); return 0; } SRC } # no function was specified, so just try to load or link against the library } else { if($has_Win32) { my $driver_ok = Win32::LoadLibrary("${lib}.dll"); $result = 1 and Win32::FreeLibrary($driver_ok) if $driver_ok; } else { $result = try_link(<<"SRC", undef); #ifdef _CYGWIN #include <windows.h> #endif #include <${header}.h> blank() { return 0; } SRC } } unless ($result) { print "no\n"; return 0; } if ($func ne "main") { $options{DEFINE} .= uc(" -Dhave_$func"); } print "yes\n"; return 1; } ======================================== which is called via: ==== warn <<"REASON" and exit unless have_library('pcap'); ==== Thinking the bug may actually be in the libpcap package, I also branched it to the same project and I've updated that to version v1.2.0. But it has the same basic behavior when I build against v1.2.0 of libpcap. Thanks Greg -- To unsubscribe, e-mail: opensuse-programming+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-programming+owner(a)opensuse.org

3 6

[opensuse-programming] Everything you wanted to know about aliasing
by Philipp Thomas 15 Dec '11

15 Dec '11

In the gcc-help ml I stumbled over this text http://dbp-consulting.com/tutorials/StrictAliasing.html which is the best text I've so far seen on this subject. It clearly explains what aliasing is and how thing should be done in the face of aliasing. Highly recommended! Philipp -- To unsubscribe, e-mail: opensuse-programming+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-programming+help(a)opensuse.org

2 1

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Programming December 2011