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

[MacPorts] #17871: Added universal variant
by MacPorts 11 Aug '09

11 Aug '09

#17871: Added universal variant -------------------------------------+-------------------------------------- Reporter: gianluca.toso@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.7.0 Keywords: libpcap universal | Port: libpcap -------------------------------------+-------------------------------------- Added universal variant, patching Makefile :-( Tested on OSX 10.4.11 PPC -- Ticket URL: <http://trac.macports.org/ticket/17871> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #19451: BUG:Port cant execute mysqld_safe
by MacPorts 11 Aug '09

11 Aug '09

#19451: BUG:Port cant execute mysqld_safe ---------------------------------+------------------------------------------ Reporter: naruto97d@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: mysql5 | Port: ---------------------------------+------------------------------------------ I cant execute mysqld_safe after i run mysql_install_db without sudo permission. -- Ticket URL: <http://trac.macports.org/ticket/19451> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #17800: Failed to build hmake
by MacPorts 10 Aug '09

10 Aug '09

#17800: Failed to build hmake ----------------------------------+----------------------------------------- Reporter: gggg.iiiii@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: | Port: ----------------------------------+----------------------------------------- I have been trying to build hmake with no success. My ports are up-to-date. ---> Fetching hmake ---> Verifying checksum(s) for hmake ---> Extracting hmake ---> Applying patches to hmake ---> Configuring hmake ---> Building hmake Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_hmake/work/hmake-3.14" && make all " returned error 2 Command output: or --package-conf can be used to act on another database entirely. When multiple of these options are given, the rightmost one is used as the database to act upon. Commands that query the package database (list, latest, describe, field) operate on the list of databases specified by the flags --user, --global, and --package-conf. If none of these flags are given, the default is --global --user. The following optional flags are also accepted: --user use the current user's package database --global use the global package database -f FILE --package-conf=FILE use the specified package config file --global-conf=FILE location of the global package config --no-user-package-conf never read the user package database --force ignore missing dependencies, directories, and libraries --force-files ignore missing directories and libraries only -g --auto-ghci-libs automatically build libs for GHCi (with register) -? --help display this help and exit -V --version output version information and exit --simple-output print output in easy-to-parse format for some commands --names-only only print package names, not versions; can only be used with list --simple-output --ignore-case ignore case for substring matching MkConfig: user error (Command (/opt/local/bin/ghc-pkg-6.10.1 -l) failed) hmake-config: compiler not known: 'ghc' make[1]: *** [config] Error 2 make: *** [targets/ix86-Darwin-9.6.0/hmake-ghc] Error 2 Error: Status 1 encountered during processing. ghais-issas-macbook:~ ghais$ sudo port clean hmake ---> Cleaning hmake ghais-issas-macbook:~ ghais$ sudo port install hmake ---> Fetching hmake ---> Verifying checksum(s) for hmake ---> Extracting hmake ---> Applying patches to hmake ---> Configuring hmake ---> Building hmake Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_hmake/work/hmake-3.14" && make all " returned error 2 Command output: or --package-conf can be used to act on another database entirely. When multiple of these options are given, the rightmost one is used as the database to act upon. Commands that query the package database (list, latest, describe, field) operate on the list of databases specified by the flags --user, --global, and --package-conf. If none of these flags are given, the default is --global --user. The following optional flags are also accepted: --user use the current user's package database --global use the global package database -f FILE --package-conf=FILE use the specified package config file --global-conf=FILE location of the global package config --no-user-package-conf never read the user package database --force ignore missing dependencies, directories, and libraries --force-files ignore missing directories and libraries only -g --auto-ghci-libs automatically build libs for GHCi (with register) -? --help display this help and exit -V --version output version information and exit --simple-output print output in easy-to-parse format for some commands --names-only only print package names, not versions; can only be used with list --simple-output --ignore-case ignore case for substring matching MkConfig: user error (Command (/opt/local/bin/ghc-pkg-6.10.1 -l) failed) hmake-config: compiler not known: 'ghc' make[1]: *** [config] Error 2 make: *** [targets/ix86-Darwin-9.6.0/hmake-ghc] Error 2 Error: Status 1 encountered during processing. I am kind of new to macport, previously a debian user, if there is anything else needed form me please let me know. -- Ticket URL: <http://trac.macports.org/ticket/17800> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #18374: MacPort 1.700 selfupdate failing
by MacPorts 10 Aug '09

10 Aug '09

#18374: MacPort 1.700 selfupdate failing ----------------------------------+----------------------------------------- Reporter: amrobinson@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: | Port: ----------------------------------+----------------------------------------- When running selfupdate as: sudo port -v -d selfupdate I get the following message: DEBUG: Synchronizing ports tree(s) Synchronizing local ports tree from rsync://rsync.macports.org/release/ports/ DEBUG: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/ports/ /opt/local/var/macports/sources/rsync.macports.org/release/ports My mac then sits there doing nothing for hours until I force quit the selfupdate routine. -- Ticket URL: <http://trac.macports.org/ticket/18374> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #19442: librsvg incompatible with Python 3
by MacPorts 10 Aug '09

10 Aug '09

#19442: librsvg incompatible with Python 3 ----------------------------+----------------------------------------------- Reporter: gale@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.1 Keywords: | Port: librsvg ----------------------------+----------------------------------------------- The python script rsvg uses the shell bang {{{ #!/usr/bin/env python }}} to access the python interpreter. So it gets whatever version of python is currently selected as current in MacPorts. But this script is not compatible with version >= 3.0 of Python: the script contains a print statement, but print has changed to a function in version >= 3.0 of Python. There may be additional incompatibilities, I have not checked. Note that this also implies that this port has a runtime dependency on Python which is missing from the portfile. See also #19441. -- Ticket URL: <http://trac.macports.org/ticket/19442> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7

[MacPorts] #18614: freetype: wording in bytecode variant unclear
by MacPorts 10 Aug '09

10 Aug '09

#18614: freetype: wording in bytecode variant unclear -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: | Port: freetype -------------------------------------+-------------------------------------- The wording of the warning displayed by the bytecode variant could be improved. This came to me by email: On Feb 22, 2009, at 14:19, David Magda wrote: >If the 'bytecode' variant of the FreeType MacPort is chose, the following text is displayed: > >>You may want not to compile a bytecode interpreter into the >>TrueType driver. Without this you will only compile the code >>necessary to load TrueType glyphs without hinting. > >I do not understand what this paragraph is trying to tell me. Could it be reworded so that the text is "By enabling the bytecode interpreter, it will cause the library to ..." ? Or perhaps "By enabling the bytecode interpreter, you will be unable to ...". > >The second sentence uses the word "without" twice, which makes it difficult to understand what is enabled and what is disabled. -- Ticket URL: <http://trac.macports.org/ticket/18614> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #16499: speex, speex-devel: enable parallel build
by MacPorts 10 Aug '09

10 Aug '09

#16499: speex, speex-devel: enable parallel build -------------------------------------+-------------------------------------- Reporter: ryandesign(a)macports.org | Owner: billitch(a)gmail.com Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Keywords: | Port: -------------------------------------+-------------------------------------- Do you have any objection to enabling the parallel build feature in the speex and speex-devel ports? This lets them build faster on multiprocessor systems. -- Ticket URL: <http://trac.macports.org/ticket/16499> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #19849: libgeotiff doesn't build correctly with universal variant
by MacPorts 10 Aug '09

10 Aug '09

#19849: libgeotiff doesn't build correctly with universal variant ---------------------------------------+------------------------------------ Reporter: rhys.hill@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.7.1 Keywords: universal | Port: libgeotiff ---------------------------------------+------------------------------------ the libgeotiff port uses a custom post-build step to create a dynamic library, but if the universal variant is being built, you only get your native architecture at the end, even though the source static library is universal. If this: -arch ppc -arch i386 -arch x86_64 -arch ppc64 is added to the post-build step, it works correctly. -- Ticket URL: <http://trac.macports.org/ticket/19849> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #16104: libgeotiff: please update to 1.2.4
by MacPorts 10 Aug '09

10 Aug '09

#16104: libgeotiff: please update to 1.2.4 -------------------------------------+-------------------------------------- Reporter: ryandesign(a)macports.org | Owner: shadow(a)dementia.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Updates Component: ports | Version: 1.7.0 Keywords: | -------------------------------------+-------------------------------------- The libgeotiff port is at version 1.2.1 but version 1.2.4 is available. The port should be updated. -- Ticket URL: <http://trac.macports.org/ticket/16104> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #19559: variant variables not carried through to post-destroot
by MacPorts 09 Aug '09

09 Aug '09

#19559: variant variables not carried through to post-destroot ---------------------------------+------------------------------------------ Reporter: dweber@… | Owner: macports-tickets@… Type: request | Status: new Priority: Low | Milestone: MacPorts 1.8.0 Component: base | Version: 1.7.1 Keywords: variant variables | Port: ---------------------------------+------------------------------------------ Can we make variant variables carry through into the post-destroot stage definition within the variant (such that variables defined within the variant over-ride any global variables)? For example: {{{ variant python26 { set pyver 2.6 set python python${pyver} set pyport [join [lrange [split ${python} .] 0 1] ""] set pyframe ${prefix}/Library/Frameworks/Python.framework/Versions/${pyver} depends_lib-append port:${pyport} post-destroot { set pyPackage ${destroot}${pyframe}/lib/${python}/site- packages/THISPACKAGE } } }}} In this mock-up example, the depends-lib will get the ${pyport} but anything within the post-destroot will not see any of the python variables defined in the variant. All of those variables have to be either global or set within the post-destroot clause (within the variant). -- Ticket URL: <http://trac.macports.org/ticket/19559> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5