Toby Peterson wrote:
On Sun, Mar 22, 2009 at 16:19, Ryan Schmidt
wrote:
So I ask again: can you think of any reason why we should not set
these
variables in the build, test and destroot phases? Can you think of
any
problems it would cause?
CC is probably safe, others not so much (e.g. C
Toby Peterson wrote:
> On Sun, Mar 22, 2009 at 16:19, Ryan Schmidt wrote:
>> So I ask again: can you think of any reason why we should not set these
>> variables in the build, test and destroot phases? Can you think of any
>> problems it would cause?
>
> CC is probably safe, others not so much (e
On Sun, Mar 22, 2009 at 16:19, Ryan Schmidt wrote:
> So I ask again: can you think of any reason why we should not set these
> variables in the build, test and destroot phases? Can you think of any
> problems it would cause?
CC is probably safe, others not so much (e.g. CFLAGS might cause
unexpec
On Mar 22, 2009, at 18:00, Toby Peterson wrote:
On Sun, Mar 22, 2009 at 15:48, Ryan Schmidt wrote:
MacPorts sets the environment variables CC, CXX and so forth in the
configure phase only.
Can anyone think of a reason why it should not also set these
variables in
the build, test and destro
On Sun, Mar 22, 2009 at 15:48, Ryan Schmidt wrote:
> MacPorts sets the environment variables CC, CXX and so forth in the
> configure phase only.
>
> Can anyone think of a reason why it should not also set these variables in
> the build, test and destroot phases? It would save a lot of this kind of
MacPorts sets the environment variables CC, CXX and so forth in the
configure phase only.
Can anyone think of a reason why it should not also set these
variables in the build, test and destroot phases? It would save a lot
of this kind of thing for ports that have an unusual configure
scri
