October 2009 - macports-tickets - lists.macosforge.org

[MacPorts] #20053: Document the port naming convention of replacing ++ with xx
by MacPorts 04 Jul '14

04 Jul '14

#20053: Document the port naming convention of replacing ++ with xx ------------------------------+--------------------------------------------- Reporter: blb@… | Owner: markd@… Type: defect | Status: new Priority: Normal | Milestone: Component: guide | Version: 1.8.0 Keywords: | Port: ------------------------------+--------------------------------------------- Several ports whose "true" name have ++ in their names (libsigc++, libxml++, mysql++, and others) have the plus signs replaced with the letter x (libsigcxx2, libxmlxx, mysqlxx). This is the convention we've picked (and is also used in other project names directly like libpqxx), but we have no current documentation for it in the guide. This should be added someplace. -- Ticket URL: <http://trac.macports.org/ticket/20053> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #20377: iTerm: build fail
by MacPorts 04 Jul '14

04 Jul '14

#20377: iTerm: build fail -------------------------------+-------------------------------------------- Reporter: nefar@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.7.1 Keywords: | Port: iTerm -------------------------------+-------------------------------------------- See attached log -- Ticket URL: <http://trac.macports.org/ticket/20377> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 14

[MacPorts] #20775: gnustep-base: gnustep-config: command not found
by MacPorts 02 Jul '14

02 Jul '14

#20775: gnustep-base: gnustep-config: command not found -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.7.1 Keywords: | Port: gnustep-base -------------------------------------+-------------------------------------- I can't seem to install gnustep-base on (Mac OS X 10.4.11 Intel) because it cannot find gnustep-config: {{{ $ port install Etoile ---> Fetching gnustep-make ---> Attempting to fetch gnustep-make-2.2.0.tar.gz from http://distfiles.macports.org/gnustep-make ---> Verifying checksum(s) for gnustep-make ---> Extracting gnustep-make ---> Configuring gnustep-make ---> Building gnustep-make ---> Staging gnustep-make into destroot Warning: gnustep-make requests to install files outside the common directory structure! ---> Installing gnustep-make @2.2.0_0+gnustep_layout ########################################################## To have a fully working GNUstep make system, please add '. /mp/GNUstep/System/Library/Makefiles/GNUstep.sh' to your shell login (in ~/.profile) You may also want to set up your MANPATH : export MANPATH=$GNUSTEP_LOCAL_ROOT/Library/Documentation/man:$GNUSTEP_SYSTEM_ROOT/Library/Documentation/man:/mp/share/man:/usr/share/man ########################################################## ---> Activating gnustep-make @2.2.0_0+gnustep_layout ---> Cleaning gnustep-make ---> Fetching gnustep-base ---> Attempting to fetch gnustep-base-1.19.1.tar.gz from http://distfiles.macports.org/gnustep-base ---> Verifying checksum(s) for gnustep-base ---> Extracting gnustep-base ---> Applying patches to gnustep-base Warning: reinplace s|GNUSTEP_INSTALLATION_DIR = $(GNUSTEP_SYSTEM_ROOT)|GNUSTEP_INSTALLATION_DOMAIN=SYSTEM|g didn't change anything in /mp/var/macports/build /_Users_rschmidt_macports_dports_gnustep_gnustep-base/work/gnustep- base-1.19.1/GNUmakefile ---> Configuring gnustep-base Error: Target org.macports.configure returned: configure failure: shell command " cd "/mp/var/macports/build /_Users_rschmidt_macports_dports_gnustep_gnustep-base/work/gnustep- base-1.19.1" && ./configure --prefix=/mp CC=gcc-mp-4.2 GNUSTEP_MAKEFILES=/mp/share/GNUstep/Makefiles --disable-tls --enable- libffi --with-ffi-include=/mp/include/gcc42 --with-ffi- library=/mp/lib/gcc42 " returned error 1 Command output: ./configure: line 1: gnustep-config: command not found configure: error: cannot find install-sh or install.sh in /mp/share/GNUstep/Makefiles .//mp/share/GNUstep/Makefiles Error: The following dependencies failed to build: SQLClient Performance gnustep-base oniguruma5 poppler openjpeg poppler-data Error: Status 1 encountered during processing. $ }}} -- Ticket URL: <http://trac.macports.org/ticket/20775> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 28

[MacPorts] #16336: Allow multiple ports to satisfy a single dependency
by MacPorts 25 Jun '14

25 Jun '14

#16336: Allow multiple ports to satisfy a single dependency ---------------------------------+------------------------------------------ Reporter: rhwood(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: | ---------------------------------+------------------------------------------ Currently there is no mechanism to specify that multiple ports may satisfy a single dependency requirement. It would be nice to be able to do so. I can think of two ways this can be done: OR dependencies:: Allow dependencies to be specified in the following fashion:[[BR]]{{{port:able|baker|charlie}}}[[BR]]where the pipe is used to separate one or more ports that may satisfy a single dependency. The first port would be used if none of the ports are installed. There should be no limit to the number of pipes, nor should there be any requirement that any pipes be used (ie, no pipes = no alternate dependencies). This should also wotk with ''bin:'' and ''path:'' type dependencies. "provides" capability in ports:: Use a "provides" key to specify that a port satisfies a particular requirement. Use the name of the port if a provides keyword is not specified. For example, if port '''able-devel''' specifies that it {{{ provides able }}} then port '''able-devel''' would be able satisfy the dependency {{{ port:able }}} in another port, without that other port having to be aware of port '''able-devel''' -- Ticket URL: <http://trac.macports.org/ticket/16336> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 12

[MacPorts] #17366: mkvtoolnix - 2.4.0 - +wxwidgets variant produces unusable binary
by MacPorts 24 Jun '14

24 Jun '14

#17366: mkvtoolnix - 2.4.0 - +wxwidgets variant produces unusable binary ------------------------------+--------------------------------------------- Reporter: krunk7@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: | Port: mkvtoolnix ------------------------------+--------------------------------------------- The +wxwidgets variant produces a binary which does not properly bind to the osx Gui framework. The end result is a correctly rendered gui that does not respond to user mouse or keyboard input nor is capable of changing focus. The fix is to place the binary in an app bundle as described in the WxWidgets Mac OSX Issues wiki: http://wiki.wxwidgets.org/WxMac_Issues -- Ticket URL: <http://trac.macports.org/ticket/17366> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #22223: Support BigTIFF format in GDAL
by MacPorts 17 Jun '14

17 Jun '14

#22223: Support BigTIFF format in GDAL ------------------------------+--------------------------------------------- Reporter: adam@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.1 Keywords: | Port: gdal @1.6.2_0 ------------------------------+--------------------------------------------- When built with internal libtiff or with libtiff >= 4.0, GDAL supports reading and writing BigTIFF files as described here: http://www.gdal.org/frmt_gtiff.html GDAL in macports is currently 1.6.2 and the internal libtiff has been at version 4 since GDAL 1.5.0. The current libtiff in macports is 3.9.1 so the easiest way to support BigTIFF is to compile GDAL with the --with- libtiff=internal and --with-geotiff=internal options. -- Ticket URL: <http://trac.macports.org/ticket/22223> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7

[MacPorts] #21535: Parallel build breaks gdal +python...
by MacPorts 17 Jun '14

17 Jun '14

#21535: Parallel build breaks gdal +python... --------------------------------+------------------------------------------- Reporter: vince@… | Owner: seanasy@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.0 Keywords: gdal python | Port: gdal --------------------------------+------------------------------------------- It seems that use_parallel_build is now enabled by default. In that case, it breaks gdal +python because the makefile scheduling is wrong: it attempts to build python extension before the library is fully built, leading to an error (-lgdal not found). Specifying {{{ use_parallel_build no }}} in the various python variants fixes this behavior. -- Ticket URL: <http://trac.macports.org/ticket/21535> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #18211: xprobe2-0.3: runtime error - ping modules cause errors
by MacPorts 13 Jun '14

13 Jun '14

#18211: xprobe2-0.3: runtime error - ping modules cause errors -------------------------------------------+-------------------------------- Reporter: simon@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: xprobe2 ping invalid argument | Port: xprobe2 -------------------------------------------+-------------------------------- The first three modules are broken in xprobe2-0.3 as they generate the following error when being executed: {{{ TX_IP::sendpack::sendto: Invalid argument }}} Unfortunately the program is useless with all "ping:" modules disabled as every machine seems to be down for it. Since there is a darwin 8 platform section I guess that this might be platform dependent and it might be worth checking this on different releases. This one is failing on 10.5.6 on an Intel iMac. -- Ticket URL: <http://trac.macports.org/ticket/18211> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #16598: ettercap do not work on Mac OS X 10.5.5
by MacPorts 12 Jun '14

12 Jun '14

#16598: ettercap do not work on Mac OS X 10.5.5 -------------------------------+-------------------------------------------- Reporter: monserg(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: ettercap mac ox x | Port: ettercap-ng -------------------------------+-------------------------------------------- ettercap do not work on Mac OS X 10.5.5. card: AirportExtreme ( (0x14E4, 0x88) (Broadcom 4328 (4.170.46.11) ) ) installation fine with: sudo port install ettercap-ng but, when executing a test: ettercap -Tzq -i en1 got this error: ettercap NG-0.7.3 copyright 2001-2004 ALoR & NaGA Listening on en1... (Ethernet) ERROR : 6, Device not configured [ec_send.c:send_init:114] libnet_init(LIBNET_RAW4_ADV) failed: libnet_init(): UID or EUID of 0 required -- Ticket URL: <http://trac.macports.org/ticket/16598> 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