Update from SCons upstream; personally I'd expect aqsis needs fixing
here.

-- 
"You grabbed my hand and we fell into it, like a daydream - or a fever."
--- Begin Message ---
http://scons.tigris.org/issues/show_bug.cgi?id=1884






------- Additional comments from [EMAIL PROTECTED] Sun Jan 13 21:38:29 -0800 
2008 -------
Wanted to ack this report.  I pulled down a copy of aqsis and have isolated a
test case from it.  It's a kind of tricky combination of the following factors:

    --  Redefining the Install/InstallAs builders to wrap the original calls.



--- End Message ---
--- Begin Message ---
http://scons.tigris.org/issues/show_bug.cgi?id=1884



User stevenknight changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|NEW                       |STARTED
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Sun Jan 13 21:47:00 -0800 
2008 -------
Gah--hit the wrong thing and submitted that previous comment too soon.

As I was saying, it's a combination of several factors:

    --  Redefining the Install/InstallAs builders as wrappers that call the
original methods, which are now ToolInitializer objects
    --  Have the redefined wrappers *not* actually use the "attached"
environment, but instead use the "env" variable from the nested scope, which
means it's actually still attached to the "wrong" environment
    --  Clone the environment *after* the Install/InstallAs wrappers have been
called on the original environment, which changes them in the original 
environment
    --  Call Install/InstallAs on the cloned environment, which (because of the
 "env" variable in the nested scope) still ends up calling something that refers
to the original environment

I don't have a fix yet.  This may require a change to the aqsis SConscript file,
because this  really only worked kind of by accident, and because the relevant
construction variables in the two construction environments were the same.  If
the construction environments had different $DESTDIR values, for example, you
would have probably seen things from the cloned environment still getting
installed into the original environment's $DESTDIR.

So the aqsis configuration is kind of wrong to begin with, but we should still
at least handle the situation more gracefully, of course.  I'll try to figure
both the SCons fix for the infinite recursion and the aqsis SConscript file
change (if any) and let you know.

Warning:  I'm going to be basically off-line from Wednesday until at least
Saturday this week, so there's a chance that if I don't find the problem right
away that it might wait until next week.



--- End Message ---

Attachment: signature.asc
Description: Digital signature

Reply via email to