[Scons-users] VB: SCons fails to build

[Kristian Kinderlöv]

Hi,

I've attached an example. Extract the file with "tar -zxvf my_project.tar.gz" and  "cd" to my_project.

Now you build with:
./build/scons_wrapper.sh CONFIG=config/config-posix-debug.cfg TOOLCHAIN=posix-gcc hello

Answer from the question below:
Default in ubuntu the "sh" points to dash:
ll /bin/sh
lrwxrwxrwx 1 root root 9 Oct  3 09:49 /bin/sh -> /bin/dash*

(I tried also to changed "sh" to point to bash instead but that gave the same problem)

Br
Kristian

-----Ursprungligt meddelande-----
Från: Scons-users <scons-users-bounces at scons.org> För Mats Wichmann
Skickat: den 9 oktober 2018 21:35
Till: scons-users at scons.org
Ämne: Re: [Scons-users] VB: SCons fails to build

On 10/09/2018 10:07 AM, Bill Deegan wrote:
> Can you provide a sample SConstruct this happens with?
> It's possible the error is in some command string you're passing.
>
> And/or you're trying to run a binary which isn't in the default PATH
> set by SCons, so you either need to copy the PATH from your shell
> and/or add the path to env['ENV']['PATH'] or use the full path to the
> tool
>
>

>> When I build I get the error from Scons: “No such file or directory”.
>> From the debugger I found out that the function exec_subprocess in
>> SCons/platform/posix.py get an exception from the subprocess.Popen
>> call, see below. The same build system work fine on an Arch Linux or
>> MSYS. So something with the combination of Ubuntu and SCons causes this problem.
>>
>>
>>
>> Has anyone experience the same problem and/or have an solution for this?
>>
>>
>>
>> posix.py:
>>
>> ….
>>
>> 63 def exec_subprocess(l, env):
>> 64     proc = subprocess.Popen(l, env = env, close_fds = True)
>> 65     return proc.wait()

near as I can tell, this function is _only_ called from subprocess_spawn like this:

def subprocess_spawn(sh, escape, cmd, args, env):
    return exec_subprocess([sh, '-c', ' '.join(args)], env)


which is in turn set up by default this way:

SHELL: 'sh'
SPAWN: <function subprocess_spawn at 0x7f7fe858c158>


Is there any chance you've reset SHELL in your environment? To something that is not found on your Ubuntu system? An example would indeed be good.


_______________________________________________
Scons-users mailing list
Scons-users at scons.org
https://pairlist4.pair.net/mailman/listinfo/scons-users

The information in this email may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If you are not an intended recipient, you are strictly prohibited from reading, disclosing, distributing, copying or using this email or any of its contents, in any way whatsoever. If you have received this email in error, please contact the sender by reply email and destroy all copies of the original message. Please also be advised that emails are not a secure form for communication, and may contain errors.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: my_project.tar.gz
Type: application/x-gzip
Size: 19032 bytes
Desc: my_project.tar.gz
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20181010/d81f7dc6/attachment-0001.bin>