[MacPorts] #26797: curl: curl-config differs

[MacPorts]

#26797: curl: curl-config differs
-------------------------------------+--------------------------------------
 Reporter:  keith.crist@…            |       Owner:  ryandesign@…           
     Type:  defect                   |      Status:  new                    
 Priority:  Normal                   |   Milestone:                         
Component:  ports                    |     Version:  1.9.1                  
 Keywords:                           |        Port:  curl                   
-------------------------------------+--------------------------------------

Comment(by ryandesign@…):

 Replying to [comment:2 keith.crist@…]:
 > I do not need to build universal.  The two files are attached. The
 command was Install htop, macports did the rest.  I am new to macports,
 please let me know the command to build Intel only.

 The files are identical except that the PowerPC version contains "'--host
 =powerpc-apple-darwin9.8.0' 'host_alias=powerpc-apple-darwin9.8.0'" which
 makes this report a duplicate of #24001.

 The command to build curl for Intel only is:
 {{{
 sudo port clean curl
 sudo port install curl
 }}}
 To build universal, you would have had to ask for the universal variant
 with "sudo port install curl +universal", or have put "+universal" in your
 variants.conf. MacPorts base also sometimes rebuilds dependencies
 universal if it believes that will help, but that should really only apply
 if your build_arch is 64-bit (e.g. x86_64) and you are building a port
 that requires 32-bit (e.g. i386), and this is only the case by default, so
 you should not have run into it on Leopard, unless you have changed your
 build_arch.

 Replying to [comment:3 keith.crist@…]:
 > I did edit macports.conf  universal_archs   i386  x86_64

 If you change universal_archs, you pretty much need to manually rebuild
 any existing ports you've installed universal. Really it's best not to
 change universal_archs once you've installed any ports.

 > Is it OK to just remove
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_curl/work
 and start over?

 Yes, and to do so, you would run "sudo port clean curl".

-- 
Ticket URL: <https://trac.macports.org/ticket/26797#comment:4>
MacPorts <http://www.macports.org/>
Ports system for Mac OS