request for help (uberftp) ...

[Ryan Schmidt]

On Sep 10, 2013, at 11:54, Peter Danecek wrote:

> On Sep 4, 2013, at 1:05 , Ryan Schmidt wrote:
> 
>> If it depends on the bitness, then you will want to base it off the ${build_arch} variable. And you'll have to decide how to handle the universal variant, since a universal build on modern systems means i386 and x86_64 -- 32-bit and 64-bit.
> 
> Well, I understood that in general the values for globus_flavor may vary somewhat, not only with bitness. On the other hand, the globus ports seem to limit this to only 2 values `gcc64pthr` and  `gcc32pthr`. So to base it on  ${build_arch} might be okay.
> 
> In the Portfile of `globus-core` I find the following at the very top:
> --- snip ---
> # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4
> # $Id: Portfile 110696 2013-09-04 02:17:50Z ram at macports.org $
> 
> if {$build_arch == "x86_64" || $build_arch == "ppc64"} {
>    set flavor gcc64pthr
>    set enable64 yes
> } else {
>    set flavor gcc32pthr
>    set enable64 no
> }
> [...]
> --- snap --- 
> 
> So, would this be the appropriate way to handle this in uberftp as well?

That seems ok.


> I always assumed that Portfiles are supposed to start with the PortSystem line, but apparently I was wrong.

You're right, they are. The PortSystem line imports all the MacPorts-specific Tcl commands, so it should be the first line of a Portfile (after the modeline and $Id$ line). The code you quoted above is generic Tcl code which doesn't use any MacPorts-specific additions to the language so in that case it doesn't matter.


> universal?
> Not sure, how does `globus-*` ports solve this? Or do these bother at all?

I see nothing in the globus-core port that addresses universal builds. I'm unable to really test it; with or without the universal variant the build fails with "ERROR: gcc not supported". I'm using clang, of course, not gcc.


> Is disabling universal builds an option?

Yes, if you don't want to support universal builds you can disable the universal variant.

Using the muniversal portgroup may be an option if you do want to support universal builds.