On Mar 21, 2012, at 12:08 PM, Ryan Schmidt wrote:
>
> On Mar 21, 2012, at 11:00, Leo Singer wrote:
>
>>> 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.
>
> I meant healpix's Makefiles. If they have a setting for turning off these
> silent rules, and using "normal" verbose rules, let's use it. And if they
> don't have a setting for that, could you suggest they add one?
I'll ask about it the next chance I get.
>> Any other suggestions for revision 1?
>
> It's probably fine not to increase the revision just for this change. healpix
> has a dependency (cfitsio); if the user had chosen a non-standard build_arch,
> cfitsio would have been built for that other build_arch, but healpix would
> then fail to build. So increasing the revision (thereby forcing a rebuild)
> would not benefit anyone.
OK, done.
> I'd also still check whether adding a universal variant (i.e. by adding the
> line "variant universal {}" on a line before you invoke
> [get_canonical_archs]) works.
Both that and
universal_variant yes
worked, but according to the MacPorts guide, 'yes' is the default for
universal_variant. Why wasn't a universal variant added by default?
Leo
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
