Should root have a gcc/clang port as a lib dependency?

[Jeremy Huddleston Sequoia]

It sounds like root should have a depends_run dependency on whatever compiler it is executing.

--Jeremy

On Sep 23, 2013, at 10:01, Jean-François Caron <jfcaron at phas.ubc.ca> wrote:

> Hi, I use the root port for my work, and I was surprised this morning that everything stopped working after I did a cleanup of all my "leaves" ports.  root is used as a C++ interpreter, but it also trivially can be used to compile programs that use its libraries (usually by adding a + to a command string).  Apparently when it is used to compile stuff, the compiler that was used to compile root is called.
> 
> My root was compiled with clang-3.2, but this is listed only as a build dependency, not a lib dependency.  I got reasonably informative error messages ("/opt/local/bin/clang++-mp-3.2: No such file or directory"), but I am wondering if maybe the compiler should be listed as something other than a build directory, given that compiling root macros and programs is a pretty standard functionality of root.  I.e. root without a proper compiler is basically broken.  
> 
> My solution was to add clang-3.2 as a requested port, but really I only use it via root, so this feels un-MacPorts-like to me.  Adding the compiler as a lib dependency doesn't feel really appropriate either, since it's not being used as a library, but rather is called externally.  Perhaps experts can chime in about how they feel?
> 
> Jean-François
> 
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4145 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20130923/75406a7d/attachment.p7s>