#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 xeron.oskom@…): Replying to [comment:1 cal@…]:
Replying to [ticket:42756 xeron.oskom@…]:
tcl bundled macports coudn't be compiled if tcl already installed and $LDFLAGS and/or $CPPFLAGS include macports dirs
What's your use case for doing this anyway? I'd say it's a bad idea and unsupported; we even strip MacPorts dirs from $PATH deliberately at the beginning of `./configure`. I could extend the check to remove `-I$prefix/include` from `CPPFLAGS` and `-L$prefix/lib` from `LDFLAGS`, but that would be unexpected to a user actually specifying them.
I think this is a user error – feel free to convince me that it isn't, and if you can suggest how this can be solved.
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 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. -- Ticket URL: <https://trac.macports.org/ticket/42756#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X