Bug 111309 - Mesa doesn't build with current Scons version (3.1.0)
Summary: Mesa doesn't build with current Scons version (3.1.0)
Alias: None
Product: Mesa
Classification: Unclassified
Component: Other (show other bugs)
Version: git
Hardware: All All
: medium critical
Assignee: mesa-dev
QA Contact: mesa-dev
Depends on:
Reported: 2019-08-06 21:52 UTC by Eric Engestrom
Modified: 2019-09-18 20:19 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Description Eric Engestrom 2019-08-06 21:52:34 UTC
$ scons
scons: Reading SConscript files ...

scons: warning: EnsureSConsVersion is ignored for development version
File "SConstruct", line 33, in <module>
TypeError: a bytes-like object is required, not 'str':
  File "SConstruct", line 47:
    ENV = os.environ,
  File "/usr/lib/python3.7/site-packages/SCons/Environment.py", line 991:
    apply_tools(self, tools, toolpath)
  File "/usr/lib/python3.7/site-packages/SCons/Environment.py", line 107:
  File "/usr/lib/python3.7/site-packages/SCons/Environment.py", line 1798:
  File "/usr/lib/python3.7/site-packages/SCons/Tool/__init__.py", line 303:
    self.generate(env, *args, **kw)
  File "scons/gallium.py", line 219:
    env['gcc_compat'] = check_cc(env, 'GCC', 'defined(__GNUC__)')
  File "scons/gallium.py", line 135:
    source.write('#if !(%s)\n#error\n#endif\n' % expr)
  File "/usr/lib/python3.7/tempfile.py", line 481:
    return func(*args, **kwargs)

From the error, it sounds like it could be a python2 vs python3 issue?

It works fine if I downgrade back to scons 3.0.4 (which I'll be doing for the time being)
Comment 1 GitLab Migration User 2019-09-18 20:19:33 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/944.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.