[MacPorts] #20190: xorg-libXt and xorg-libX11 should use configure.cc and configure.cpp (was: base is not properly exporting CC and CPP)

[MacPorts]

#20190: xorg-libXt and xorg-libX11 should use configure.cc and configure.cpp
-------------------------------------+--------------------------------------
 Reporter:  ryandesign@…             |       Owner:  ryandesign@…           
     Type:  defect                   |      Status:  new                    
 Priority:  Normal                   |   Milestone:                         
Component:  ports                    |     Version:  1.7.1                  
 Keywords:                           |        Port:  xorg-libXt, xorg-libX11
-------------------------------------+--------------------------------------
Changes (by ryandesign@…):

  * component:  base => ports
  * milestone:  MacPorts 1.8.0 =>


Comment:

 Replying to [comment:7 jeremyhu@…]:
 > Was libX11-1.2.1 ok?

 No, it was also affected. I have only recently written and begun using the
 script mentioned at the bottom of UsingTheRightCompiler.

 Base is not the problem. As I [comment:3 wrote above], the gcc problem is
 a problem is the configure script (e.g. line 12527 of xorg-libX11 1.2.2's
 configure script) which says

 {{{
     case `gcc -dumpversion` in
 }}}

 It is running "gcc"; it is not using any variable to discover what CC we
 would like to use. I would call this an upstream bug.

 And the cpp problem is that the configure script apparently does not
 respond to the common variable CPP and instead is looking for a variable
 RAWCPP. This is weird to me and I don't know why they do this but it can
 be fixed as I [comment:4 wrote above].

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