[MacPorts] #42756: macports doesn't compile with bundled tcl

[MacPorts]

#42756: macports doesn't compile with bundled tcl
----------------------------+--------------------------------
  Reporter:  xeron.oskom@…  |      Owner:  macports-tickets@…
      Type:  defect         |     Status:  new
  Priority:  Normal         |  Milestone:
 Component:  base           |    Version:  2.2.99
Resolution:                 |   Keywords:
      Port:                 |
----------------------------+--------------------------------

Comment (by cal@…):

 Replying to [comment:3 xeron.oskom@…]:
 > Because I would like any software which requires compilation (ruby gems
 natives, compilation by hands, etc) to use macports libs and headers.
 > And also https://rvm.io/integration/macports-before-autolibs

 That's certainly a good reason for having those variables set, but do you
 need them when compiling MacPorts?


 > If you want to use bundled tcl I think it's good idea to ensure there're
 no other tcls in any compiler paths and don't blame user.

 I'm not sure that's easy to test, though. I can certainly test whether Tcl
 headers are somewhere in the paths specified by `CPPFLAGS`, but since
 there are Tcl headers in `/usr/include` the test would always succeed (and
 having them in `/usr/include` is not a problem, just adding them to
 `CPPFLAGS` is because those are apparently put ahead of Tcl's own CPPFLAGS
 in their build system (which '''is''' the sane place to but them, btw)).
 Of course I could remove `-I$prefix/include` from CPPFLAGS and
 `-L$prefix/lib` from LDFLAGS if they are found, but there might be users
 out there who did set those variables on purpose when building macports
 and might wonder why they're getting stripped.

 Does this problem occur when running selfupdate or when compiling MacPorts
 from source?

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