Hi folks. I'm fighting with a very confusing problem with scons at the moment. For reasons I haven't determined, when I have things set up to build when scons is run from outside the gem5 directory (using -C), it fails the final linker step with error 127 and no other output 100% of the time. If I run from within the gem5 directory everything works fine.
I did some reading, and bash reports error 127 when it can't find the command you asked it to run. To determine if that might be the problem, I modified scons to run "which" on each command it was about to spawn before it did, to make sure it resolved to something. That worked just fine. If I run the command manually, it returns exit code 0. If I take the environment scons tries to run g++ under and partially duplicate that with a script and env -i, it still succeeds. If I run with clang instead of g++, I get the same behavior which makes me think it's not g++ doing something weird, it's scons. I can't for the life of me figure out what though, and I can't seem to get any information to work with other than this mysterious error 127. If any of you have any idea why it's doing what it's doing, or if there's any information I can gather that might help, I would be very happy to hear it. Gabe _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
