Jack Howarth wrote:

    If MacPorts is willing to junk the idea of building i386 packages
as a default on 10.6, the config.guess fix is really the way to go.
When patched this way, all programs that use config.guess to determine
the triplets for configure will pick the correct value of
x86_64-apple-darwin10 and there will be no need to force -m64 onto any
compiler flags or to bother to pass --build/--host/--target to
configure. From my own experiences on fink, I would strongly urge
MacPorts to abandon any attempt to build an i386 MacPorts on 10.6
(except where non-EMT64 Core Duo and Core Solo's will do that without
any intervention) and to focus on the x86_64 Macport builds for 10.6
fully utilizing the proposed config.guess patch to avoid the bother
of passing the --build/--target/--host triplets to configure in
Portfiles. My two cents anyway as a newcomer to MacPorts.

You probably want to fix the "${os.arch}" as well,
since that will affect e.g. how packages are named:

set archive.file "${name}-${version}_${revision}${portvariants}. [option os.arch].${archive.type}" set unarchive.file "${name}-${version}_${revision}${portvariants}. [option os.arch].${unarchive.type}"
                                
"x86_64", as per http://trac.macports.org/changeset/54798
is a workaround for http://trac.macports.org/ticket/20506

set os_arch $tcl_platform(machine)
if {$os_arch == "Power Macintosh"} { set os_arch "powerpc" }
if {$os_arch == "i586" || $os_arch == "i686" || $os_arch == "x86_64"} { set os_arch "i386" }
default os.arch {$os_arch}

--anders

_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Reply via email to