May 2012 - macports-tickets - lists.macosforge.org

[MacPorts] #34618: swig: add swig-php53 and swig-php54 subports
by MacPorts 10 Jun '14

10 Jun '14

#34618: swig: add swig-php53 and swig-php54 subports -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: kevin@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Keywords: | Port: swig -------------------------------------+-------------------------------------- Currently there is a swig-php5 subport, which depends on path:bin/php:php5. The php5 and php5-devel ports are going away, and ${prefix}/bin/php will no longer be installed by a port. php5 and php5-devel are to be replaced by the new php53 and php54 subports, which install ${prefix}/bin/php53 and ${prefix}/bin/php54 respectively. I'm not sure how swig works, but I assume we should have new swig-php53 and swig- php54 ports, which let you build something for use with php53 and php54 respectively. -- Ticket URL: <https://trac.macports.org/ticket/34618> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #34448: webkit-gtk +quartz missing symbol: Webcore::PluginView::invalidateRect
by MacPorts 09 Jun '14

09 Jun '14

#34448: webkit-gtk +quartz missing symbol: Webcore::PluginView::invalidateRect ------------------------------------------+--------------------------------- Reporter: michael.culbertson@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Keywords: | Port: webkit-gtk ------------------------------------------+--------------------------------- I installed webkit-gtk (version 1.6.3_2) with the +quartz variant (in addition to the default +svg and +video variants) as a dependency for gnucash. It built and installed correctly, but when I tried to run gnucash, it died immediately reporting: {{{ dyld: Symbol not found: __ZN7WebCore10PluginView14invalidateRectERKNS_7IntRectE Referenced from: /opt/local/lib/libwebkitgtk-1.0.0.dylib Expected in: dynamic lookup }}} -- Ticket URL: <https://trac.macports.org/ticket/34448> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #16110: libxml2: attempts to use libxslt.1.dylib
by MacPorts 06 Jun '14

06 Jun '14

#16110: libxml2: attempts to use libxslt.1.dylib -------------------------------------+-------------------------------------- Reporter: ryandesign(a)macports.org | Owner: cedric.luthi(a)gmail.com Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: | -------------------------------------+-------------------------------------- I previously had libxml2 2.6.32_1 and libxslt 1.1.23_0 installed. I forcibly uninstalled libxml2 and reinstalled it, to test an issue. During the reinstall, this message appeared in the debug output, and also a Mac OS X Crash Reporter dialog appeared with similar information: {{{ dyld: lazy symbol binding failed: Symbol not found: _xmlXPathContextSetCache Referenced from: /mp/lib/libxslt.1.dylib Expected in: flat namespace dyld: Symbol not found: _xmlXPathContextSetCache Referenced from: /mp/lib/libxslt.1.dylib Expected in: flat namespace }}} `/mp` is my MacPorts prefix. So it seems that libxml2 is trying to load libxslt.1.dylib during the build. You must modify the port so that this does not happen, because libxml2 does not declare a dependency on libxslt (and it cannot, since libxslt declares a dependency on libxml2, and we cannot have circular dependencies). I am running Mac OS X 10.4.11 on an Intel Mac with Xcode 2.5 and MacPorts from trunk @38557. -- Ticket URL: <http://trac.macports.org/ticket/16110> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #32842: swig-python build fails for non-default build_arch
by MacPorts 05 Jun '14

05 Jun '14

#32842: swig-python build fails for non-default build_arch -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: kevin@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: swig-python -------------------------------------+-------------------------------------- {{{ ld: warning: in /i386-10.6-mp/lib/libpcre.dylib, file was built for i386 which is not the architecture being linked (x86_64) Undefined symbols: "_pcre_version", referenced from: _Swig_pcre_version in misc.o (maybe you meant: _Swig_pcre_version) "_pcre_compile", referenced from: _Swig_string_regex in misc.o _Swig_name_regexmatch_value in naming.o "_pcre_free", referenced from: _Swig_string_regex in misc.o _Swig_string_regex in misc.o _Swig_name_regexmatch_value in naming.o "_pcre_exec", referenced from: _Swig_string_regex in misc.o _Swig_name_regexmatch_value in naming.o ld: symbol(s) not found }}} -- Ticket URL: <https://trac.macports.org/ticket/32842> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #21294: Enable cffi support in swig?
by MacPorts 05 Jun '14

05 Jun '14

#21294: Enable cffi support in swig? ------------------------------------+--------------------------------------- Reporter: glen.henshaw@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.0 Keywords: swig, cffi | Port: swig 1.3.40 ------------------------------------+--------------------------------------- Swig 1.3.40 supports cffi, but the port does not have a variant for it, and the +universal variant does not seem to do anything. Would it be possible to enable cffi support? Is it possible to enable support for the other languages swig supports but for which there are no port variants? The built-in OSX swig does support cffi, but the implementation is quite old. -- Ticket URL: <http://trac.macports.org/ticket/21294> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #31384: Cannot install pike using macports
by MacPorts 05 Jun '14

05 Jun '14

#31384: Cannot install pike using macports -------------------------------------+-------------------------------------- Reporter: peymandelshad@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: -------------------------------------+-------------------------------------- Macports fail to install pike. Here's the log: ---> Computing dependencies for pike[[BR]] ---> Fetching archive for pike[[BR]] ---> Attempting to fetch pike-7.6.112_3.darwin_10.x86_64.tbz2 from http://packages.macports.org/pike [[BR]] ---> Fetching pike[[BR]] ---> Verifying checksum(s) for pike[[BR]] ---> Extracting pike[[BR]] ---> Applying patches to pike[[BR]] ---> Configuring pike[[BR]] ---> Building pike[[BR]] Error: Target org.macports.build returned: shell command failed (see log for details)[[BR]] Log for pike is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_pike/pike/main.log[[BR]] Error: Status 1 encountered during processing.[[BR]] To report a bug, see <http://guide.macports.org/#project.tickets>[[BR]] -- Ticket URL: <https://trac.macports.org/ticket/31384> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #30782: efte: update to 1.1
by MacPorts 30 May '14

30 May '14

#30782: efte: update to 1.1 -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: reiffert@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.1 Keywords: haspatch | Port: efte -------------------------------------+-------------------------------------- Here is a patch that makes the following changes to the efte port: * update efte to 1.1 * use bzip2 distfile because it is smaller * change no_x11 variant to x11 variant; retain compatibility code to ease upgrades * use the cmake portgroup * add ncurses dependency * change the X dependencies to library dependencies * use rmd160 and sha256 checksums for distfile * use `system`'s new `-W` argument The problem is it fails in the post-destroot block; the `cefte` program does not seem to exist anymore. I don't know what it did in efte 0.96 so I don't know whether this post-destroot block needs to be changed in some way or just deleted. -- Ticket URL: <https://trac.macports.org/ticket/30782> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #32590: lua port update
by MacPorts 30 May '14

30 May '14

#32590: lua port update -------------------------------+-------------------------------------------- Reporter: andremm@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: -------------------------------+-------------------------------------------- Lua 5.2.0 is out since Dec 16th. For this reason I'm providing an updated Portfile to lua port, as well as the necessary patches and files. To my mind, a new port called lua51 should be created with current lua Portfile for Lua 5.1.4. Regards, Andre -- Ticket URL: <https://trac.macports.org/ticket/32590> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 9

[MacPorts] #32827: xsane not working with Canon Lide Scanner
by MacPorts 27 May '14

27 May '14

#32827: xsane not working with Canon Lide Scanner -----------------------------------------+---------------------------------- Reporter: christian.kneissl@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: -----------------------------------------+---------------------------------- I tried hours to get (x)sane working via MacPorts for my Canon Lide 210, which should be handled by genesys. It seems that scanimage has problems to connect to the scanner via libusb, because the device is used/opened by another process. Find the Output of scanimage -L below. I tried with root and not-privileged user which seems to be the same. Here are the detailed Version infos: {{{ libusb @1.0.8 devel/libusb libusb-compat @0.1.3 devel/libusb-compat sane-backends @1.0.22 graphics/sane-backends sane-frontends @1.0.15git graphics/sane-frontends xsane @0.998 graphics/xsane }}} Permission of Lockfile: {{{ drwxrwxrwx 2 root admin /opt/local/var/lock/sane }}} Output of sane-find-scanner: {{{ /opt/local/var/lock>sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x05ac, product=0x8215) at libusb:250:007 found USB scanner (vendor=0x04a9, product=0x190a, chip=GL124?) at libusb:250:009 found USB scanner (vendor=0x0ccd, product=0x0043) at libusb:253:005 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. # You may want to run this program as root to find all devices. Once you # found the scanner devices, be sure to adjust access permissions as # necessary. }}} Genesys-Entry: {{{ # Canon LiDE 210 usb 0x04a9 0x190a }}} Output of scanimage -L: {{{ /opt/local/etc/sane.d>export SANE_DEBUG_GENESYS=255 /opt/local/etc/sane.d>export SANE_DEBUG_SANEI_USB=128 /opt/local/etc/sane.d>export SANE_DEBUG_DLL=255 chris@iMac:/opt/local/etc/sane.d>scanimage -L [sanei_debug] Setting debug level of dll to 255. [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends 1.0.22 [dll] sane_init/read_dlld: attempting to open directory `./dll.d' [dll] sane_init/read_dlld: attempting to open directory `/opt/local/etc/sane.d/dll.d' [dll] sane_init/read_dlld: opendir failed: No such file or directory [dll] sane_init/read_config: reading dll.conf [dll] add_backend: adding backend `genesys' [dll] sane_get_devices [dll] load: searching backend `genesys' in `/opt/local/lib/sane' [dll] load: trying to load `/opt/local/lib/sane/libsane-genesys.1.so' [dll] load: dlopen()ing `/opt/local/lib/sane/libsane-genesys.1.so' [dll] init: initializing backend `genesys' [sanei_debug] Setting debug level of genesys to 255. [genesys] SANE Genesys backend version 1.0 build 63 from sane-backends 1.0.22 [genesys] SANE Genesys backend built with libusb [genesys] sane_init: authorize != null [sanei_debug] Setting debug level of sanei_usb to 128. [sanei_usb] sanei_usb_init: marking existing devices [sanei_usb] sanei_usb_init: Looking for kernel scanner devices [sanei_usb] sanei_usb_init: Looking for libusb devices libusb:info [process_new_device] allocating new device for location 0xfa000000 libusb:info [process_new_device] found device with address 1 at 001-05ac-8006-09-00 libusb:info [process_new_device] allocating new device for location 0xfa100000 libusb:info [process_new_device] found device with address 2 at 002-0424-2514-09-00 libusb:info [process_new_device] allocating new device for location 0xfa200000 libusb:info [process_new_device] found device with address 3 at 003-05ac- 850b-ef-02 libusb:info [process_new_device] allocating new device for location 0xfa110000 libusb:info [process_new_device] found device with address 4 at 004-0a5c-4500-09-00 libusb:info [process_new_device] allocating new device for location 0xfa130000 libusb:info [process_new_device] found device with address 5 at 005-05ac-1006-09-00 libusb:info [process_new_device] allocating new device for location 0xfa111000 libusb:info [process_new_device] found device with address 7 at 007-05ac-8215-ff-01 libusb:info [process_new_device] allocating new device for location 0xfa132000 libusb:info [process_new_device] found device with address 6 at 006-05ac-0250-00-00 libusb:info [process_new_device] allocating new device for location 0xfa133000 libusb:info [process_new_device] found device with address 8 at 008-046d- c52b-00-00 libusb:info [process_new_device] allocating new device for location 0xfa131000 libusb:info [process_new_device] found device with address 9 at 009-04a9 -190a-ff-ff libusb:info [process_new_device] allocating new device for location 0xfd000000 libusb:info [process_new_device] found device with address 1 at 001-05ac-8006-09-00 libusb:info [process_new_device] allocating new device for location 0xfd100000 libusb:info [process_new_device] found device with address 2 at 002-0424-2514-09-00 libusb:info [process_new_device] allocating new device for location 0xfd120000 libusb:info [process_new_device] found device with address 3 at 003-05ac-8242-00-00 libusb:info [process_new_device] allocating new device for location 0xfd140000 libusb:info [process_new_device] found device with address 5 at 005-0ccd-0043-00-00 libusb:info [process_new_device] allocating new device for location 0xfd110000 libusb:info [process_new_device] found device with address 4 at 004-05ac-8403-00-00 libusb:info [process_new_device] allocating new device for location 0xfa000000 libusb:info [process_new_device] found device with address 1 at 001-05ac-8006-09-00 libusb:info [process_new_device] allocating new device for location 0xfa100000 libusb:info [process_new_device] found device with address 2 at 002-0424-2514-09-00 libusb:info [process_new_device] allocating new device for location 0xfa200000 libusb:info [process_new_device] found device with address 3 at 003-05ac- 850b-ef-02 libusb:info [process_new_device] allocating new device for location 0xfa110000 libusb:info [process_new_device] found device with address 4 at 004-0a5c-4500-09-00 libusb:info [process_new_device] allocating new device for location 0xfa130000 libusb:info [process_new_device] found device with address 5 at 005-05ac-1006-09-00 libusb:info [process_new_device] allocating new device for location 0xfa111000 libusb:info [process_new_device] found device with address 7 at 007-05ac-8215-ff-01 libusb:info [process_new_device] allocating new device for location 0xfa132000 libusb:info [process_new_device] found device with address 6 at 006-05ac-0250-00-00 libusb:info [process_new_device] allocating new device for location 0xfa133000 libusb:info [process_new_device] found device with address 8 at 008-046d- c52b-00-00 libusb:info [process_new_device] allocating new device for location 0xfa131000 libusb:info [process_new_device] found device with address 9 at 009-04a9 -190a-ff-ff libusb:info [process_new_device] allocating new device for location 0xfd000000 libusb:info [process_new_device] found device with address 1 at 001-05ac-8006-09-00 libusb:info [process_new_device] allocating new device for location 0xfd100000 libusb:info [process_new_device] found device with address 2 at 002-0424-2514-09-00 libusb:info [process_new_device] allocating new device for location 0xfd120000 libusb:info [process_new_device] found device with address 3 at 003-05ac-8242-00-00 libusb:info [process_new_device] allocating new device for location 0xfd140000 libusb:info [process_new_device] found device with address 5 at 005-0ccd-0043-00-00 libusb:info [process_new_device] allocating new device for location 0xfd110000 libusb:info [process_new_device] found device with address 4 at 004-05ac-8403-00-00 [sanei_usb] sanei_usb_init: device 0x05ac/0x8006, interface 0 doesn't look like a scanner (9/9) [sanei_usb] sanei_usb_init: device 0x05ac/0x8006: no suitable interfaces [sanei_usb] sanei_usb_init: device 0x0424/0x2514, interface 0 doesn't look like a scanner (9/9) [sanei_usb] sanei_usb_init: device 0x0424/0x2514: no suitable interfaces [sanei_usb] sanei_usb_init: device 0x05ac/0x850b, interface 0 doesn't look like a scanner (239/14) [sanei_usb] sanei_usb_init: device 0x05ac/0x850b, interface 1 doesn't look like a scanner (239/14) [sanei_usb] sanei_usb_init: device 0x05ac/0x850b, interface 2 doesn't look like a scanner (239/255) [sanei_usb] sanei_usb_init: device 0x05ac/0x850b: no suitable interfaces [sanei_usb] sanei_usb_init: device 0x0a5c/0x4500, interface 0 doesn't look like a scanner (9/9) [sanei_usb] sanei_usb_init: device 0x0a5c/0x4500: no suitable interfaces [sanei_usb] sanei_usb_init: device 0x05ac/0x1006, interface 0 doesn't look like a scanner (9/9) [sanei_usb] sanei_usb_init: device 0x05ac/0x1006: no suitable interfaces [sanei_usb] sanei_usb_init: found libusb device (0x05ac/0x8215) interface 0 at libusb:250:007 [sanei_usb] store_device: add dn 0 with libusb:250:007 [sanei_usb] sanei_usb_init: device 0x05ac/0x0250, interface 0 doesn't look like a scanner (0/3) [sanei_usb] sanei_usb_init: device 0x05ac/0x0250, interface 1 doesn't look like a scanner (0/3) [sanei_usb] sanei_usb_init: device 0x05ac/0x0250: no suitable interfaces [sanei_usb] sanei_usb_init: device 0x046d/0xc52b, interface 0 doesn't look like a scanner (0/3) [sanei_usb] sanei_usb_init: device 0x046d/0xc52b, interface 1 doesn't look like a scanner (0/3) [sanei_usb] sanei_usb_init: device 0x046d/0xc52b, interface 2 doesn't look like a scanner (0/3) [sanei_usb] sanei_usb_init: device 0x046d/0xc52b: no suitable interfaces [sanei_usb] sanei_usb_init: found libusb device (0x04a9/0x190a) interface 0 at libusb:250:009 [sanei_usb] store_device: add dn 1 with libusb:250:009 [sanei_usb] sanei_usb_init: device 0x05ac/0x8006, interface 0 doesn't look like a scanner (9/9) [sanei_usb] sanei_usb_init: device 0x05ac/0x8006: no suitable interfaces [sanei_usb] sanei_usb_init: device 0x0424/0x2514, interface 0 doesn't look like a scanner (9/9) [sanei_usb] sanei_usb_init: device 0x0424/0x2514: no suitable interfaces [sanei_usb] sanei_usb_init: device 0x05ac/0x8242, interface 0 doesn't look like a scanner (0/3) [sanei_usb] sanei_usb_init: device 0x05ac/0x8242: no suitable interfaces [sanei_usb] sanei_usb_init: found libusb device (0x0ccd/0x0043) interface 0 at libusb:253:005 [sanei_usb] store_device: add dn 2 with libusb:253:005 [sanei_usb] sanei_usb_init: device 0x05ac/0x8403, interface 0 doesn't look like a scanner (0/8) [sanei_usb] sanei_usb_init: device 0x05ac/0x8403: no suitable interfaces [sanei_usb] sanei_usb_init: found 3 devices [sanei_usb] sanei_usb_init: device 00 is libusb:250:007 [sanei_usb] sanei_usb_init: device 01 is libusb:250:009 [sanei_usb] sanei_usb_init: device 02 is libusb:253:005 [genesys] sane_init: little endian machine [genesys] probe_genesys_devices: start [sanei_usb] sanei_usb_find_devices: vendor=0x03f0, product=0x1405 [sanei_usb] sanei_usb_find_devices: vendor=0x0461, product=0x0377 [sanei_usb] sanei_usb_find_devices: vendor=0x03f0, product=0x0901 [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x2213 [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x221c [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1904 [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1909 [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1905 [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1906 [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1907 [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x190a [genesys] attach: start: devp != NULL, may_wait = 0 [genesys] attach: trying to open device `libusb:250:009' [sanei_usb] sanei_usb_open: trying to open device `libusb:250:009' libusb:error [darwin_open] USBDeviceOpen: another process has device opened for exclusive access libusb:info [darwin_open] device open for access [sanei_usb] sanei_usb_open: libusb complained: Device not configured [genesys] attach: couldn't open device `libusb:250:009': Invalid argument [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1906 [sanei_usb] sanei_usb_find_devices: vendor=0x04a7, product=0x0426 [sanei_usb] sanei_usb_find_devices: vendor=0x04a7, product=0x0474 [sanei_usb] sanei_usb_find_devices: vendor=0x0a82, product=0x4803 [sanei_usb] sanei_usb_find_devices: vendor=0x04a7, product=0x0494 [sanei_usb] sanei_usb_find_devices: vendor=0x04a7, product=0x049b [sanei_usb] sanei_usb_find_devices: vendor=0x0a17, product=0x3210 [sanei_usb] sanei_usb_find_devices: vendor=0x04f9, product=0x2038 [sanei_usb] sanei_usb_find_devices: vendor=0x1dcc, product=0x4812 [sanei_usb] sanei_usb_find_devices: vendor=0x0a82, product=0x4800 [sanei_usb] sanei_usb_find_devices: vendor=0x1dcc, product=0x4810 [sanei_usb] sanei_usb_find_devices: vendor=0x0a82, product=0x480c [sanei_usb] sanei_usb_find_devices: vendor=0x04a7, product=0x0229 [sanei_usb] sanei_usb_find_devices: vendor=0x04a7, product=0x04ac [sanei_usb] sanei_usb_find_devices: vendor=0x04da, product=0x100f [sanei_usb] sanei_usb_find_devices: vendor=0x03f0, product=0x4505 [sanei_usb] sanei_usb_find_devices: vendor=0x03f0, product=0x4605 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0900 [genesys] probe_genesys_devices: exit [genesys] sane_init: exit [dll] init: backend `genesys' is version 1.0.63 [genesys] sane_get_devices: start: local_only = false [genesys] probe_genesys_devices: start [sanei_usb] sanei_usb_find_devices: vendor=0x03f0, product=0x1405 [sanei_usb] sanei_usb_find_devices: vendor=0x0461, product=0x0377 [sanei_usb] sanei_usb_find_devices: vendor=0x03f0, product=0x0901 [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x2213 [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x221c [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1904 [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1909 [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1905 [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1906 [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1907 [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x190a [genesys] attach: start: devp != NULL, may_wait = 0 [genesys] attach: trying to open device `libusb:250:009' [sanei_usb] sanei_usb_open: trying to open device `libusb:250:009' libusb:error [darwin_open] USBDeviceOpen: another process has device opened for exclusive access libusb:info [darwin_open] device open for access [sanei_usb] sanei_usb_open: libusb complained: Device not configured [genesys] attach: couldn't open device `libusb:250:009': Invalid argument [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x1906 [sanei_usb] sanei_usb_find_devices: vendor=0x04a7, product=0x0426 [sanei_usb] sanei_usb_find_devices: vendor=0x04a7, product=0x0474 [sanei_usb] sanei_usb_find_devices: vendor=0x0a82, product=0x4803 [sanei_usb] sanei_usb_find_devices: vendor=0x04a7, product=0x0494 [sanei_usb] sanei_usb_find_devices: vendor=0x04a7, product=0x049b [sanei_usb] sanei_usb_find_devices: vendor=0x0a17, product=0x3210 [sanei_usb] sanei_usb_find_devices: vendor=0x04f9, product=0x2038 [sanei_usb] sanei_usb_find_devices: vendor=0x1dcc, product=0x4812 [sanei_usb] sanei_usb_find_devices: vendor=0x0a82, product=0x4800 [sanei_usb] sanei_usb_find_devices: vendor=0x1dcc, product=0x4810 [sanei_usb] sanei_usb_find_devices: vendor=0x0a82, product=0x480c [sanei_usb] sanei_usb_find_devices: vendor=0x04a7, product=0x0229 [sanei_usb] sanei_usb_find_devices: vendor=0x04a7, product=0x04ac [sanei_usb] sanei_usb_find_devices: vendor=0x04da, product=0x100f [sanei_usb] sanei_usb_find_devices: vendor=0x03f0, product=0x4505 [sanei_usb] sanei_usb_find_devices: vendor=0x03f0, product=0x4605 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0900 [genesys] probe_genesys_devices: exit [genesys] sane_get_devices: exit [dll] sane_get_devices: found 0 devices No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). [dll] sane_exit: exiting [dll] sane_exit: calling backend `genesys's exit function [genesys] sane_exit: start [genesys] sane_exit: exit [dll] sane_exit: finished }}} Greetings, Christian -- Ticket URL: <https://trac.macports.org/ticket/32827> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7

[MacPorts] #25904: [NEW] graphics/afterglow
by MacPorts 26 May '14

26 May '14

#25904: [NEW] graphics/afterglow ------------------------------+--------------------------------------------- Reporter: jul_bsd@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: ------------------------------+--------------------------------------------- AfterGlow 1.x is a collection of scripts which facilitate the process of generating link graphs. AfterGlow 1.x is written in Perl and is meant to be used on the command line. There is no graphical user interface available. AfterGlow expects a CSV file as input and generates either an attributed graph langugage file that can be processed by the graphiviz libraries, or it can generate output for consumption by the large grpah library (LGL). -- Ticket URL: <http://trac.macports.org/ticket/25904> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 13