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

[MacPorts] #38769: atlas: incorrect compiler checking code
by MacPorts 22 Apr '13

22 Apr '13

#38769: atlas: incorrect compiler checking code --------------------------+--------------------- Reporter: ryandesign@… | Owner: vince@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: atlas --------------------------+--------------------- The atlas port includes this code in the global part of the portfile: {{{ # Chose the right flags for GCC and Clang compilers if {${build_arch} == "i386" || ${build_arch} == "x86_64"} { # General flags # GCC set gcc_flags "-fomit-frame-pointer -mfpmath=sse -O3\ -fno-schedule-insns2 -fPIC" # Clang if {${use_clang} == "32" || ${use_clang} == "XCode" } { pre-fetch { ui_warn "Compiling Atlas with this version of clang is\ likely *NOT* to work. Please use clang-3.3 or\ higher." } set clang_flags "-O3 -fomit-frame-pointer -fPIC" } else { # Clang 3.3 – Use loop and straight vectorizer set clang_flags "-O3 -fomit-frame-pointer -fPIC\ -fvectorize -fslp-vectorize" } }}} There are two problems with this. First, if compiling atlas with clang 3.2 will not work, then the +mpclang32 variant should be removed and macports-clang-3.2 should be added to compiler.blacklist (along with any other compilers with which atlas will not work). If compiling atlas with some versions of Xcode clang will not work, then the specific versions of Xcode clang with which it will not work should be blacklisted using the compiler_blacklist_versions portgroup as mentioned in #38768. Second, the more important issue is that the message will never actually be printed, because MacPorts does not execute code in the order in which you think it does. First, MacPorts executes all code in the global part of the portfile (i.e. code that's not within a phase or a variant). Then afterward, it executes the code in any selected variants. And within variants is where you're defining the use_clang variable. So at the point where the above code runs, use_clang is always empty (except when no compiler variant was selected and have_avx is yes, in which case use_clang is set to 33), so the message never prints. This also means the clang_flags aren't set the way you want them to be, for some clang versions. The same goes for the gcc_version variable. It's initialized to 0 in the global part of the portfile, then changed in the gcc4x variants, but it's checked in the global part of the portfile, before it's been set, so it will always be 0 when the following code runs (except when no compiler variant was selected and have_avx is no, in which case gcc_version is set to 47): {{{ # Threading # If we run on a mono-processor machine (PPC), then disable threading if {![catch {sysctl hw.logicalcpu} result] && $result == 1} { configure.args-append -t 0 set no_threads 1 } else { set no_threads 0 # Threading relies on OpenMP if gcc compilers are selected if {${gcc_version} != 0} { configure.args-append -Si omp 1 } } }}} This means `-Si omp 1` won't be added to the configure.args in all of the situations where you want it to be. (Specifically, it won't be, if the user selects a gcc4x variant.) ------ One solution could be to set the variables in the global part of the portfile instead of within a variant. For example, instead of doing this: {{{ variant gcc48 conflicts gcc46 gcc47 \ clang mpclang32 mpclang33 \ description {build using macports-gcc-4.8} { depends_build-append port:gcc48 configure.compiler macports-gcc-4.8 set gcc_version 48 set use_clang "" } }}} Do this: {{{ variant gcc48 conflicts gcc46 gcc47 \ clang mpclang32 mpclang33 \ description {build using macports-gcc-4.8} { depends_build-append port:gcc48 configure.compiler macports-gcc-4.8 } if {[variant_isset gcc48]} { set gcc_version 48 set use_clang "" } }}} You'll need to increase the port's revision when you make these changes so that things get rebuilt in the way you want them to be built. -- Ticket URL: <https://trac.macports.org/ticket/38769> MacPorts <http://www.macports.org/> Ports system for OS X

1 10

[MacPorts] #38816: atlas: post-build proc fails
by MacPorts 22 Apr '13

22 Apr '13

#38816: atlas: post-build proc fails --------------------------+--------------------- Reporter: ryandesign@… | Owner: vince@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: atlas --------------------------+--------------------- After a successful (+mpclang32 +universal) build, it fails in the post- build proc: {{{ DEBUG: Executing proc-post-org.macports.build-build-0 DEBUG: Executing reinplace: /usr/bin/sed {s|^LIBTOOL=.*$|LIBTOOL=$(GCC) $(GCCFLAGS)|} < /opt/local/var/macports/build/_Users_rschmidt_macports_dports_math_atlas/atlas/work/atlas-3.10.1-x86_64/build/lib/Makefile >@ file10 DEBUG: euid/egid changed to: 0/0 DEBUG: chowned /opt/local/var/macports/build/_Users_rschmidt_macports_dports_math_atlas/atlas/work/atlas-3.10.1-x86_64/build/lib/Makefile to macports DEBUG: euid/egid changed to: 501/528 DEBUG: euid/egid changed to: 0/0 DEBUG: setting attributes on /opt/local/var/macports/build/_Users_rschmidt_macports_dports_math_atlas/atlas/work/atlas-3.10.1-x86_64/build/lib/Makefile DEBUG: euid/egid changed to: 501/528 DEBUG: Executing reinplace: /usr/bin/sed s|dynamic|dynamiclib|g < /opt/local/var/macports/build/_Users_rschmidt_macports_dports_math_atlas/atlas/work/atlas-3.10.1-x86_64/build/lib/Makefile >@ file10 DEBUG: euid/egid changed to: 0/0 DEBUG: chowned /opt/local/var/macports/build/_Users_rschmidt_macports_dports_math_atlas/atlas/work/atlas-3.10.1-x86_64/build/lib/Makefile to macports DEBUG: euid/egid changed to: 501/528 DEBUG: euid/egid changed to: 0/0 DEBUG: setting attributes on /opt/local/var/macports/build/_Users_rschmidt_macports_dports_math_atlas/atlas/work/atlas-3.10.1-x86_64/build/lib/Makefile DEBUG: euid/egid changed to: 501/528 /usr/bin/make dylib rm -rf RCW_tMp ; mkdir RCW_tMp cd RCW_tMp ; ar x ../liblapack.a cd RCW_tMp ; ar x ../libf77blas.a ar: ../libf77blas.a: No such file or directory make[1]: *** [dylib] Error 1 make: *** [shared_all] Error 2 Command failed: /usr/bin/make shared_all Exit code: 2 }}} I verified liblapack.a exists in both i386 and x86_64 directories, but libf77blas.a exists only in the i386 directory. -- Ticket URL: <https://trac.macports.org/ticket/38816> MacPorts <http://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #38743: Installing SExtractor
by MacPorts 22 Apr '13

22 Apr '13

#38743: Installing SExtractor --------------------------------+-------------------------------- Reporter: matthew.bothwell@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: --------------------------------+-------------------------------- Hi -- I hope this is the right place for this. Apologies if not. I'm trying to install SExtractor via MacPorts. I'm on OS X 10.7.5, and I'm using the latest version of Xcode. The install is failing when trying to build ATLAS, with the following error: ---> Computing dependencies for sextractor ---> Dependencies to be installed: atlas fftw-3 ---> Building atlas Error: org.macports.build for port atlas returned: command execution failed Error: Failed to install atlas -- Ticket URL: <https://trac.macports.org/ticket/38743> MacPorts <http://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #38836: atlas: build fails very quickly
by MacPorts 22 Apr '13

22 Apr '13

#38836: atlas: build fails very quickly --------------------------+--------------------- Reporter: ryandesign@… | Owner: vince@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: atlas --------------------------+--------------------- Previously atlas would build for hours before failing; now it fails within 20 seconds. I tried the +mpclang32 and +mpclang33 variants with the same result; here's the log of the +mpclang33 variant. {{{ Error report error_<ARCH>.tgz has been created in your top-level ATLAS directory. Be sure to include this file in any help request. cat: ../../CONFIG/error.txt: No such file or directory cat: ../../CONFIG/error.txt: No such file or directory BEGIN STAGE 1-0-0: SYSTEM PROBE/AUX COMPILE at 13:05 make[1]: *** [build] Error 255 }}} -- Ticket URL: <https://trac.macports.org/ticket/38836> MacPorts <http://www.macports.org/> Ports system for OS X

1 7

[MacPorts] #38878: gettext: Use macports libtool and thus support compilation against libc++
by MacPorts 22 Apr '13

22 Apr '13

#38878: gettext: Use macports libtool and thus support compilation against libc++ --------------------+-------------------------- Reporter: dh@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: gettext --------------------+-------------------------- I am currently attempting to build various ports (in a separate tree) against `libc++` rather than the default `libstdc++`. Currently `gettext` builds using its own libtool shipped in the distribution. That libtool does not support linking against `libc++` (as it discards any`-stdlib` option passed). This results in one of the built libraries `libasprintf` linking against `libstdc++`. This patch makes `gettext` depend on our own libtool port and uses it during the build phase. {{{ Index: Portfile =================================================================== --- Portfile (revision 105464) +++ Portfile (working copy) @@ -7,6 +7,7 @@ name gettext version 0.18.2.1 +revision 1 categories devel maintainers ryandesign # libs are LGPL and executables are GPL @@ -53,6 +54,10 @@ port:libiconv \ port:ncurses +# macports libtool allows linking against libc++, the libtool in the distribution does not +depends_build port:libtool +build.args LIBTOOL=${prefix}/bin/glibtool + test.run yes test.target check }}} -- Ticket URL: <https://trac.macports.org/ticket/38878> MacPorts <http://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #38868: ROOT Update to 5.34.06 + new clang 3.2 and 3.3 variants
by MacPorts 21 Apr '13

21 Apr '13

#38868: ROOT Update to 5.34.06 + new clang 3.2 and 3.3 variants ---------------------------------+-------------------------------- Reporter: jonesc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: haspatch maintainer | Port: root ---------------------------------+-------------------------------- Hi, This ticket updates ROOT to the new release, 5.34.06. I also add two new variants to build with MacPorts clang 3.2 and 3.3 compilers. The cocoa variant doesn't yet support clang 3.3, so that variant is updated to veto this compiler, as well as all non-clang compilers. cheers Chris -- Ticket URL: <https://trac.macports.org/ticket/38868> MacPorts <http://www.macports.org/> Ports system for OS X

1 8

[MacPorts] #38872: Processing of port hydra failed
by MacPorts 21 Apr '13

21 Apr '13

#38872: Processing of port hydra failed -----------------------------------------+-------------------------------- Reporter: salex500@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.1.3 Keywords: Error, Install, Hydra, Help | Port: -----------------------------------------+-------------------------------- I have encountered a problem when installing hydra. I have followed everything on http://www.hackmac.org/forum/topic/1011-thc- hydra/page__p__5639#entry5639 and i got past the initial build doesnt work and xcode doesnt exist by installing the command line tools but now im stuck on this. I would greatly appreciate any help :) Heres the error code. {{{new-host:~ alexsaunders$ sudo port install hydra ---> Computing dependencies for hydra ---> Building hydra Error: org.macports.build for port hydra returned: command execution failed Please see the log file for port hydra for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_security_hydra/hydra/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port hydra failed}}} -- Ticket URL: <https://trac.macports.org/ticket/38872> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #38252: ola @0.8.27 new upstream release
by MacPorts 21 Apr '13

21 Apr '13

#38252: ola @0.8.27 new upstream release ---------------------------------+-------------------------------- Reporter: nomis52@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: haspatch maintainer | Port: ola ---------------------------------+-------------------------------- Update to reflect the new upstream release. This also adds the OSC variant and enables it by default. (OSC was included from 0.8.26). -- Ticket URL: <https://trac.macports.org/ticket/38252> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7

[MacPorts] #38867: quassel: version bump to 0.9.0 (patch included)
by MacPorts 20 Apr '13

20 Apr '13

#38867: quassel: version bump to 0.9.0 (patch included) ------------------------+-------------------------------- Reporter: macports@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: haspatch | Port: quassel ------------------------+-------------------------------- The attached patch updates the Portfile for quassel to the latest version 0.9.0 and fixes the livecheck. -- Ticket URL: <https://trac.macports.org/ticket/38867> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #38831: qca installs /opt/local/share/cmake/modules/FindQCA2.cmake
by MacPorts 20 Apr '13

20 Apr '13

#38831: qca installs /opt/local/share/cmake/modules/FindQCA2.cmake --------------------------+------------------------- Reporter: ryandesign@… | Owner: michaelld@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: qca --------------------------+------------------------- qca installs /opt/local/share/cmake/modules/FindQCA2.cmake but the directory name [http://www.cmake.org/Wiki/CMake:How_To_Find_Libraries should be] "Modules" not "modules". -- Ticket URL: <https://trac.macports.org/ticket/38831> MacPorts <http://www.macports.org/> Ports system for OS X

1 3