On Mar 21, 2012, at 11:35 AM, Ryan Schmidt wrote:
>
> On Mar 21, 2012, at 09:11, Leo Singer wrote:
>
>> Attached is a revised Portfile. I am having trouble with
>> get_canonical_archflags. After adding to build.post_args-append:
>>
>> CC="${configure.cc} [get_canonical_archflags cc]" \
>> CL="${configure.cc} [get_canonical_archflags ld]" \
>> CXX="${configure.cxx} [get_canonical_archflags cxx]" \
>> CXXL="${configure.cxx} [get_canonical_archflags ld]"
>>
>> I get the following error message:
>>
>> :info:build shell command "/usr/bin/make HEALPIX_TARGET=osx
>> BINDIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_healpix/healpix/work/Healpix_2.20a/bin
>>
>> LIBDIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_healpix/healpix/work/Healpix_2.20a/lib
>>
>> INCDIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_healpix/healpix/work/Healpix_2.20a/include
>> EXTERNAL_CFITSIO=yes CFITSIO_INCDIR=/opt/local/include
>> CFITSIO_LIBDIR=/opt/local/lib CFITSIO_EXT_LIB=/opt/local/lib/libcfitsio.a
>> CFITSIO_EXT_INC=/opt/local/include CC=\"/usr/bin/llvm-gcc-4.2 {-arch
>> x86_64"} CL=\"/usr/bin/llvm-gcc-4.2 {-arch x86_64"}
>> CXX=\"/usr/bin/llvm-g++-4.2 {-arch x86_64"} CXXL=\"/usr/bin/llvm-g++-4.2
>> {-arch x86_64"}" returned error 2
>
> The problem is how you're constructing the build command:
>
> build {
> system "${build.cmd} -C ${worksrcpath}/src/cxx ${build.post_args}"
> system "${build.cmd} -C ${worksrcpath}/src/C/subs static install AR=\"ar
> -rsv\" ${build.post_args}"
> }
>
> Instead of referencing ${build.post_args} directly, use [join
> ${build.post_args}].That worked. Updated Portfile attached. > The build process currently hides the actual compile commands from us, making > it not totally easy to see whether we've succeeded. If you can make the build > output more verbosely that would be great. By build process, do you mean the MacPorts build process, or healpix's Makefiles? healpix has a homebrew build system with two quirks: an interactive configure script (takes keystrokes instead of command line arguments) and handwritten Makefiles that produce output resembling Automake's silent build setting. Any other suggestions for revision 1? (As to the compiler on Tiger, I think that in the long run I ought to introduce an OpenMP variant so that it is possible to build healpix with compilers that don't support OpenMP.) Leo
Portfile
Description: Binary data
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
