question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Makefile screwed up with python 3.8

See original GitHub issue

I switched to python 3.8 (2.7 is no longer supported), and tried to make.

First it complains that linenoise folder already exists (the script should indeed check for that), and after removing the folder and tried again, complains about prep folder. removed and tried again, got the following.

iMac:duktape wc$ make -B
# git clone https://github.com/antirez/linenoise.git
# Use forked repo to get compile warnings fixed.
git clone -b fix-compile-warnings-duktape https://github.com/svaarala/linenoise.git
fatal: destination path 'linenoise' already exists and is not an empty directory.
make: *** [linenoise] Error 128
iMac:duktape wc$ 
iMac:duktape wc$ rm -fr linenoise/
iMac:duktape wc$ make -B
# git clone https://github.com/antirez/linenoise.git
# Use forked repo to get compile warnings fixed.
git clone -b fix-compile-warnings-duktape https://github.com/svaarala/linenoise.git
Cloning into 'linenoise'...
remote: Enumerating objects: 414, done.
remote: Total 414 (delta 0), reused 0 (delta 0), pack-reused 414
Receiving objects: 100% (414/414), 123.21 KiB | 35.00 KiB/s, done.
Resolving deltas: 100% (243/243), done.
mkdir: prep: File exists
make: *** [prep] Error 1
/usr/local/opt/python@3.8/bin/python3 tools/configure.py --output-directory ./prep/nondebug --source-directory src-input --config-metadata config --option-file util/makeduk_base.yaml --line-directives
Traceback (most recent call last):
  File "tools/configure.py", line 1005, in <module>
    main()
  File "tools/configure.py", line 315, in main
    get_duk_version(os.path.join(srcdir, 'duktape.h.in'))
  File "tools/configure.py", line 139, in get_duk_version
    m = r.match(line)
TypeError: cannot use a string pattern on a bytes-like object

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

3reactions
svaaralacommented, May 5, 2020

All Duktape tooling is Python2 only

2reactions
svaaralacommented, May 24, 2020

I didn’t miss that - all the tooling will be converted to Node.js and that is already in progress, see src-tools.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Getting error when trying to install python - Stack Overflow
I have created a file with the error and shared it Google drive. Click Here for the full stack trace. The relevant portion...
Read more >
Unable to build Python library from source on Linux #380
Hello, I'm following the instructions here to build the Python library but I'm getting a compiler error. Repro steps: sudo apt-get install git ......
Read more >
View topic - Python-3.8.7 issue: sharedmods Error 1
Am upgrading system (after quite some time) and systrem is bit broken now. Am stuck on re-compialtion of python-3.8.7. Does anyone already know ......
Read more >
Error compiling with Python 3 - ISSM Forum
The above error happens when I set the configure script's --with-python-dir= setting to a Python 3 path, and it seems to be hardcoded...
Read more >
Creating a Python Makefile - Earthly Blog
The reason make is very common with compiled languages is because the compilation commands for those languages can be long and complicated and ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found