April 2008 - macports-tickets - lists.macosforge.org

Re: [MacPorts] #15140: gcj34 mtree violation
by MacPorts 30 Apr '08

30 Apr '08

#15140: gcj34 mtree violation -----------------------------+---------------------------------------------- Reporter: alex352(a)web.de | Owner: ryandesign(a)macports.org Type: defect | Status: assigned Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: -----------------------------+---------------------------------------------- Changes (by ryandesign(a)macports.org) * owner: macports-tickets(a)lists.macosforge.org => ryandesign(a)macports.org * status: new => assigned * summary: gcj34 violation of /opt/local => gcj34 mtree violation * milestone: => Port Bugs Comment: Yes, it's just a warning, really intended for the maintainer of the port, except that gcj34 doesn't have one. It's intentional that gcj34 violates the mtree. (It installs into `${prefix}/gcj34-3.4.6`.) -- Ticket URL: <http://trac.macports.org/ticket/15140#comment:1> MacPorts </> Ports system for Mac OS

1 0

Re: [MacPorts] #14108: inkscape fails to compile on intel leopard install
by MacPorts 30 Apr '08

30 Apr '08

#14108: inkscape fails to compile on intel leopard install ------------------------------------+--------------------------------------- Reporter: atenderholt(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: inkscape leopard intel ------------------------------------+--------------------------------------- Comment (by atenderholt(a)gmail.com) Yes it still fails with the same error. This is now on 10.5.2 with MacPorts selfupdate'd today (Inkscape 0.46). Adam -- Ticket URL: <http://trac.macports.org/ticket/14108#comment:3> MacPorts </> Ports system for Mac OS

1 0

[MacPorts] #14084: cdparanoia missing an option causing abcde to fail
by MacPorts 29 Apr '08

29 Apr '08

#14084: cdparanoia missing an option causing abcde to fail -------------------------------+-------------------------------------------- Reporter: duke(a)spacebox.net | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: cdparanoia abcde | -------------------------------+-------------------------------------------- I'm trying to use abcde to rip and encode some CDs but it's failing due to a command line option missing from cdparanoia. The "-d" option in cdparanoia is used to specify a device to rip from. It seems the macports code has removed this option from the original cdparanoia code but references to it have not been removed from other macports (or at least not from abcde.) Using the macports version, the -d option prints out usage information causing abcde to fail. At least I assume that macports specifically removed the option - I downloaded the original cdparanoia code and the -d option is present. If this is the case, I really think the -d option should be left in but made a "placebo" option so its absence doesn't break other programs like abcde. Or maybe the -d option should just be left in its original form - is there something in OS X that prevents cdparanoia from being able to select a different device from which to rip a disc? -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14084> MacPorts </projects/macports> Ports system for Mac OS

1 5

[MacPorts] #14576: darcs 1.0.9 fails to configure due to incompatibility with ghc 6.8.2
by MacPorts 29 Apr '08

29 Apr '08

#14576: darcs 1.0.9 fails to configure due to incompatibility with ghc 6.8.2 --------------------------------+------------------------------------------- Reporter: ndimiduk(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: | --------------------------------+------------------------------------------- ghc-6.8.2 installs without issue but contains an API incompatible with darcs-1.0.9. Here's the output: ---- {{{ ndimiduk@luna /opt/MacPorts $ port install darcs ---> Configuring darcs Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/MacPorts/var/macports/build/_opt_MacPorts_var_macports_sources_rsync.macports.org_release_ports_devel_darcs/work/darcs-1.0.9" && ./configure --prefix=/opt/MacPorts --mandir=/opt/MacPorts/share/man --without-docs " returned error 1 Command output: checking for darcs... no checking the release state... release checking for gcc... /usr/bin/gcc-4.0 checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /usr/bin/gcc-4.0 accepts -g... yes checking for /usr/bin/gcc-4.0 option to accept ISO C89... none needed checking how to run the C preprocessor... /usr/bin/cpp-4.0 checking for a BSD-compatible install... /usr/bin/install checking for ghc... ghc checking where GHC keeps its libraries... /opt/MacPorts/lib/ghc-6.8.2 checking GHC.Handle.openFd... NOT old API checking GHC.Handle.openFd new API... failed configure: error: Couldnt figure out how to call GHC.Handle.openFd! Error: Status 1 encountered during processing. }}} ---- The system in a 12" g4 powerbook running 10.4.11 Here's a link to a mailing list entry which looks directly relevant: [http://www.mail-archive.com/darcs-devel@darcs.net/msg04019.html] -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14576> MacPorts </projects/macports> Ports system for Mac OS

1 10

[MacPorts] #14035: libconfig doesn't seem to include C++ version of the library
by MacPorts 29 Apr '08

29 Apr '08

#14035: libconfig doesn't seem to include C++ version of the library --------------------------------+------------------------------------------- Reporter: jan(a)kilvo.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: libconfig, broken, | --------------------------------+------------------------------------------- Hello, The libconfig package does not seem to include the C++ library that comes with the standard package, at least it's not installed when you install the port. Can this be rectified? Cheers Jan -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14035> MacPorts </projects/macports> Ports system for Mac OS

1 2

[MacPorts] #14960: BUG: ffmpeg svn fetch is using HEAD for parts of the software
by MacPorts 29 Apr '08

29 Apr '08

#14960: BUG: ffmpeg svn fetch is using HEAD for parts of the software ---------------------------------+------------------------------------------ Reporter: raimue(a)macports.org | Owner: acho(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: ffmpeg | ---------------------------------+------------------------------------------ ffmpeg is fetched using svn from `1svn://svn.mplayerhq.hu/ffmpeg/trunk/` using a specific revision specified by svn.tag. But in this directory in the repository is a svn:externals declaration: {{{ svn:externals : libswscale svn://svn.mplayerhq.hu/mplayer/trunk/libswscale }}} Therefore, libswscale is always fetched from HEAD of *another* repository. Building ffmpeg now always uses HEAD of libswscale which is not reliable. Also, building ffmpeg will result in different results although the version and revision of the port is the same. As reported on IRC by dang`r`us, ffmpeg fails at the moment on destrooting due to some HEAD commit in libswscale: {{{ : make -C libpostproc install-headers make -C libswscale install-headers Makefile:20: ../subdir.mak: No such file or directory make[1]: *** No rule to make target `../subdir.mak'. Stop. make: *** [install-headers] Error 2 }}} We can't rely on this and therefore we should export our own source tarballs for ffmpeg. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14960> MacPorts </projects/macports> Ports system for Mac OS

1 11

[MacPorts] #15155: pgintcl 3.0.2 portfile
by MacPorts 29 Apr '08

29 Apr '08

#15155: pgintcl 3.0.2 portfile -------------------------------+-------------------------------------------- Reporter: giorgio_v(a)mac.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Updates Component: ports | Version: 1.6.0 Keywords: | -------------------------------+-------------------------------------------- Please see attachment -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/15155> MacPorts </projects/macports> Ports system for Mac OS

1 0

[MacPorts] #13991: Mercurial doesn't build on Leopard
by MacPorts 29 Apr '08

29 Apr '08

#13991: Mercurial doesn't build on Leopard ---------------------------------------+------------------------------------ Reporter: ndw(a)nwalsh.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: leopard mac osx mercurial | ---------------------------------------+------------------------------------ $ sudo port install mercurial ... ---> Attempting to fetch mercurial-0.9.5.tar.gz from http://www.selenic.com/mercurial/release/ ---> Verifying checksum(s) for mercurial ---> Extracting mercurial ---> Configuring mercurial ---> Building mercurial with target build 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_mercurial/work/mercurial-0.9.5" && /opt/local/bin/python2.4 setup.py build " returned error 1 Command output: copying hgext/graphlog.py -> build/lib.macosx-10.3-i386-2.4/hgext copying hgext/hbisect.py -> build/lib.macosx-10.3-i386-2.4/hgext copying hgext/hgk.py -> build/lib.macosx-10.3-i386-2.4/hgext copying hgext/imerge.py -> build/lib.macosx-10.3-i386-2.4/hgext copying hgext/interhg.py -> build/lib.macosx-10.3-i386-2.4/hgext copying hgext/mq.py -> build/lib.macosx-10.3-i386-2.4/hgext copying hgext/notify.py -> build/lib.macosx-10.3-i386-2.4/hgext copying hgext/parentrevspec.py -> build/lib.macosx-10.3-i386-2.4/hgext copying hgext/patchbomb.py -> build/lib.macosx-10.3-i386-2.4/hgext copying hgext/purge.py -> build/lib.macosx-10.3-i386-2.4/hgext copying hgext/record.py -> build/lib.macosx-10.3-i386-2.4/hgext copying hgext/transplant.py -> build/lib.macosx-10.3-i386-2.4/hgext copying hgext/win32text.py -> build/lib.macosx-10.3-i386-2.4/hgext creating build/lib.macosx-10.3-i386-2.4/hgext/convert copying hgext/convert/__init__.py -> build/lib.macosx-10.3-i386-2.4/hgext/convert copying hgext/convert/common.py -> build/lib.macosx-10.3-i386-2.4/hgext/convert copying hgext/convert/cvs.py -> build/lib.macosx-10.3-i386-2.4/hgext/convert copying hgext/convert/darcs.py -> build/lib.macosx-10.3-i386-2.4/hgext/convert copying hgext/convert/filemap.py -> build/lib.macosx-10.3-i386-2.4/hgext/convert copying hgext/convert/git.py -> build/lib.macosx-10.3-i386-2.4/hgext/convert copying hgext/convert/hg.py -> build/lib.macosx-10.3-i386-2.4/hgext/convert copying hgext/convert/subversion.py -> build/lib.macosx-10.3-i386-2.4/hgext/convert copying hgext/convert/transport.py -> build/lib.macosx-10.3-i386-2.4/hgext/convert running build_ext building 'mercurial.mpatch' extension creating build/temp.macosx-10.3-i386-2.4 creating build/temp.macosx-10.3-i386-2.4/mercurial -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -fno-common -fno- common -dynamic -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I/opt/local/Library/Frameworks/Python.framework/Versions/2.4/include/python2.4 -c mercurial/mpatch.c -o build/temp.macosx-10.3-i386-2.4/mercurial/mpatch.o unable to execute -fno-strict-aliasing: No such file or directory error: command '-fno-strict-aliasing' failed with exit status 1 Error: Status 1 encountered during processing. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13991> MacPorts </projects/macports> Ports system for Mac OS

1 7

[MacPorts] #13897: openjpeg 1.2 fails to build
by MacPorts 29 Apr '08

29 Apr '08

#13897: openjpeg 1.2 fails to build ------------------------------------+--------------------------------------- Reporter: swordangel(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: openjpeg build failure | ------------------------------------+--------------------------------------- Lots of TIFF-related undefined symbols. Verbose screen output (from executing "sudo port -v install jpeg") attached. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13897> MacPorts </projects/macports> Ports system for Mac OS

1 3

[MacPorts] #13838: Problem installing redland-bindings +python (probably python 2.3 dependency)
by MacPorts 29 Apr '08

29 Apr '08

#13838: Problem installing redland-bindings +python (probably python 2.3 dependency) ------------------------------+--------------------------------------------- Reporter: larlet(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: | ------------------------------+--------------------------------------------- I got some trouble with the python redland--binding on leopard, here is the difference with the ruby installation: {{{ $ sudo port install redland-bindings +ruby ---> Fetching redland-bindings ---> Verifying checksum(s) for redland-bindings ---> Extracting redland-bindings ---> Configuring redland-bindings ---> Building redland-bindings with target all ---> Staging redland-bindings into destroot ---> Installing redland-bindings 1.0.6.1_0+ruby ---> Activating redland-bindings 1.0.6.1_0+ruby ---> Cleaning redland-bindings $ sudo port install redland-bindings +python ---> Building python23 with target all Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_python23/work/Python-2.3.6" && make all " returned error 2 Command output: gcc -L/opt/local/lib -u __dummy -u _PyMac_Error -framework System -framework CoreServices -framework Foundation -o python.exe \ Modules/python.o \ -L. -lpython2.3 -ldl -framework CoreServices -framework Foundation Undefined symbols: "__dummy", referenced from: ld: symbol(s) not found collect2: ld returned 1 exit status make: *** [python.exe] Error 1 Error: The following dependencies failed to build: python23 Error: Status 1 encountered during processing. }}} The issue seemed to be a python23 dependency so I decide to install this one but I got another problem at this point: {{{ $ sudo port install python23 ---> Building python23 with target all Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_python23/work/Python-2.3.6" && make all " returned error 2 Command output: gcc -L/opt/local/lib -u __dummy -u _PyMac_Error -framework System -framework CoreServices -framework Foundation -o python.exe \ Modules/python.o \ -L. -lpython2.3 -ldl -framework CoreServices -framework Foundation Undefined symbols: "__dummy", referenced from: ld: symbol(s) not found collect2: ld returned 1 exit status make: *** [python.exe] Error 1 Error: Status 1 encountered during processing. }}} The issue had already been reported to the mailing-list without any suggestion so maybe this is the right place. Maybe the dependency could be set at python24 now? Let me know if I can help. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13838> MacPorts </projects/macports> Ports system for Mac OS

1 3