[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cfe-commits
Subject:    Re: [cfe-commits] r140409 - in /cfe/trunk: docs/tools/clang.pod
From:       Chandler Carruth <chandlerc () google ! com>
Date:       2011-09-30 21:42:08
Message-ID: CAGCO0KjY5igecLx+KTf_8gMfJU6PozPGDRySi0f+hgOFrrXwVA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Fri, Sep 30, 2011 at 2:30 PM, Douglas Gregor <dgregor@apple.com> wrote:

> > (b) the driver will have to do something to honor that option when it
> > is calling out to other processes (like the linker), or be able to
> > adjust paths.
>
> I think it's entirely reasonable to temporarily chdir() when calling those
> other processes.


Yea, the typical pattern I've seen is:

compute paths -> fork -> chdir -> exec

[Attachment #5 (text/html)]

<div class="gmail_quote">On Fri, Sep 30, 2011 at 2:30 PM, Douglas Gregor <span \
dir="ltr">&lt;<a href="mailto:dgregor@apple.com">dgregor@apple.com</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;"> <div class="im">&gt; (b) the driver will have to do \
something to honor that option when it<br> &gt; is calling out to other processes \
(like the linker), or be able to<br> &gt; adjust paths.<br>
<br>
</div>I think it&#39;s entirely reasonable to temporarily chdir() when calling those \
other processes.</blockquote></div><br><div>Yea, the typical pattern I&#39;ve seen \
is:</div><div><br></div><div>compute paths -&gt; fork -&gt; chdir -&gt; exec</div>



_______________________________________________
cfe-commits mailing list
cfe-commits@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits


[prev in list] [next in list] [prev in thread] [next in thread]