[MacPorts] #18209: ufraw 0.15 fails to build

[MacPorts]

#18209: ufraw 0.15 fails to build
---------------------------------+------------------------------------------
 Reporter:  macports@…           |       Owner:  frank.mcpherson@…                
     Type:  defect               |      Status:  new                              
 Priority:  Normal               |   Milestone:  Port Bugs                        
Component:  ports                |     Version:  1.7.0                            
 Keywords:                       |        Port:  ufraw                            
---------------------------------+------------------------------------------

Comment(by devans@…):

 Replying to [comment:4 ryanjohns@…]:
 > edit variants.conf to include +no_static +no_x11 -x11 +quartz

 Really only +no_x11 and +quartz are necessary for gimp.  -x11 is sort of a
 noop as all the ports with +no_x11 turn off
 +x11 if it exists now.  I assume the +no_static has to do with your other
 quartz port but it isn't necessary for gimp.
 >
 > Yet I still received the error message. I'm going to follow your
 recommendations and start over with a fresh install of macports from
 trunk.

 You might try doing it in pieces to isolate where the problem is.  If
 you're starting from scratch I would do
 {{{
 sudo port install gimp2   // which installs the gimp application and
 default plugins
 sudo port install ufraw   // add the ufraw plugin
 }}}

 if this works then you can install gimp to fill in the rest

 > 1) Am I correct in assuming that running 'sudo port selfupdate' will
 actually downgrade to the latest release version? Therefore, I need to use
 'sudo port sync' to get updates.

 No it will sync the ports and then tell you that you have the most recent
 as trunk says it is version 1.8.0.  If you wanted
 to downgrade you would have to use the -f option to force selfupdate. But
 as you say sync is sufficient to update the ports
 tree.

 >
 > 2) Do I want to use the trunk ports tree or the regular release version?

 They are the same.

 > 3) If I want to install a port like 'tightvnc' which uses x11 but
 doesn't have a quartz variant, will this cause problems with other quartz-
 built ports like gimp and gnucash?  If the answer to this question is yes
 then I will install 2 copies of macports.
 >

 yes, it will cause problems if any of the common dependencies of tightvnc
 and gimp have both x11 and no_x11 variants.  So, it
 is easiest to have separate environments.  I use three, one for x11, one
 for no_x11 and one for system_x11.  Be sure and pay
 attention to the instructions for doing this in the guide.  the directory
 that you want to build from is trunk/base instead of
 the tar ball.  Then you can switch from one to the other by changing your
 PATH (with a script say).  I have x11 installed at
 /opt/local for instance and the no_x11 installed at /opt/gtk.


 By the way, in case it matters, my successful build of ufraw is on 10.4.11
 ppc with XCode 2.5.

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