Re: [cfe-dev] [RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment

On Tue, Oct 18, 2016 at 8:59 AM, Ludovic Courtès via cfe-dev wrote: > Shea Levy skribis: > >> Your patches look good! My biggest concern is how the ld wrapper behaves >> in the presence of response files. Have you tested that? > > It surely doesn’t

Re: [RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment

Hi! Shea Levy skribis: > Your patches look good! My biggest concern is how the ld wrapper behaves > in the presence of response files. Have you tested that? It surely doesn’t (yet?). However, GCC does not pass “@file” arguments when it invokes ‘ld’, and the bug report you

Re: [RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment

Hi Ludo’, Your patches look good! My biggest concern is how the ld wrapper behaves in the presence of response files. Have you tested that? Thanks, Shea Ludovic Courtès writes: > Hi Shea, > > Shea Levy skribis: > >> Unlike the traditional approach of installing system libraries

Re: [RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment

Hey Ludo’, Amazing, more than a decade of close working with these tools and I never knew about C_INCLUDE_PATH et al! It looks like those will solve a huge portion of the problem. Will look at your gcc and clang patches as well, thank you! ~Shea Ludovic Courtès writes: > Hi

Re: [RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment

Hi Shea, Shea Levy skribis: > Unlike the traditional approach of installing system libraries into one > central location like /usr/{lib,include}, the nix package manager [1] > installs each package into it's own prefix > (e.g. /nix/store/mn9kqag3d24v6q41x747zd7n5qnalch7-zlib-1.2.8-dev).

Re: [RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment

On Sun, 16 Oct 2016, Shea Levy wrote: > options) and clearly have the semantics we want. Ideally we would be > able to specify something on the level of abstraction of "this directory > should be treated like you would normally treat /usr" and get > e.g. /include, /lib, frameworks on OS X, etc.

[RFC] Reliable compiler specification setting (at least include/lib dirs) through the process environment

Hello GCC and Clang devs! Unlike the traditional approach of installing system libraries into one central location like /usr/{lib,include}, the nix package manager [1] installs each package into it's own prefix (e.g. /nix/store/mn9kqag3d24v6q41x747zd7n5qnalch7-zlib-1.2.8-dev). Moreover, each