[MacPorts] #15010: kdelibs3 3.5.8 fails to build

[MacPorts]

#15010: kdelibs3 3.5.8 fails to build
--------------------------------+-------------------------------------------
  Reporter:  gargasm at gmail.com  |       Owner:  macports-tickets at lists.macosforge.org
      Type:  defect             |      Status:  new                                  
  Priority:  Normal             |   Milestone:  Port Bugs                            
 Component:  ports              |     Version:  1.6.0                                
Resolution:                     |    Keywords:  kde kdelibs3                         
--------------------------------+-------------------------------------------
Changes (by ryandesign at macports.org):

 * cc: ryandesign at macports.org (added)

Comment:

 Replying to [comment:4 gargasm at gmail.com]:
 > also, this just re-occurred to me and may make me look like a total newb
 and idiot:
 >
 > i think many of my ports may have been installed with {{{gcc 3.4.3}}},
 but i did just perform the upgrade (which didn't seem to hit every port)
 with {{{gcc 4.0.1}}}. if this is an issue should i reinstall all my
 current ports? what's the best way to do this if so?

 If you're on Tiger, how were you using gcc 3, where gcc 4 is the default?
 Did you `gcc_select` version 3? You should not do so. This was definitely
 [http://lists.macosforge.org/pipermail/macports-
 users/2007-April/002431.html the cause] of the "dyld: Symbol not found:
 _sprintf$LDBLStub" message for another MacPorts user. MacPorts 1.7.0 will
 no longer care about what you set your default compiler to with
 `gcc_select`; e.g. it will always use gcc 4 on Tiger. But MacPorts 1.6.0
 still cares and will use whatever you have selected, sometimes with
 unfortunate results if you don't have gcc 4 selected.

 Replying to [comment:6 gargasm at gmail.com]:
 > i even made sure that {{{/opt/local/[s]*bin}}} is at the head of
 $PATH...
 When building ports, MacPorts doesn't use your PATH variable, or any other
 environment variables you may have set.
 > is there such a thing as an include path variable?
 During the configure phase, MacPorts sets the CPPFLAGS to include
 -I${prefix}/include and the LDFLAGS to include -L${prefix}/lib. This
 should be all most ports need to be able to find other ports' headers and
 libraries.

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