← index #6800Issue #3521
Related · medium · value 2.754
QUERY · ISSUE

Build process: mpy file in frozen dir produces spam

openby peterhinchopened 2021-01-26updated 2024-09-13
enhancementtools

I inadvertently included a .mpy file in a directory containing .py files for freezing. On building, so much output spewed that the Bash history buffer filled; I couldn't scroll back far enough to see where the error first occurred.

It would be good if the build process either stopped with a clear message or ignored files without .py extensions with a warning.

CANDIDATE · ISSUE

Error about FROZEN_MPY_DIR

closedby Meekdaiopened 2017-12-26updated 2017-12-27

make V=1 or set BUILD_VERBOSE in your environment to increase build verbosity.
FIND: The format of the parameter is incorrect
mkdir -p build-PYBV10/genhdr
Create build-PYBV10/genhdr/pins.h
...
CC ../py/../extmod/uos_dupterm.c
CC ../py/../lib/embed/abort_.c
CC ../py/../lib/utils/printf.c
Creating build-PYBV10/frozen_mpy.c
usage: mpy-tool.py [-h] [-d] [-f] [-q QSTR_HEADER]
[-mlongint-impl {none,longlong,mpz}] [-mmpz-dig-size N]
files [files ...]
mpy-tool.py: error: too few arguments
make: *** [build-PYBV10/frozen_mpy.c] ERROR 2
make: *** Deleting file“build-PYBV10/frozen_mpy.c”

Python 2.7.11 |Anaconda 4.0.0 (64-bit)|
GNU Make 3.81

Keyboard

j / / n
next pair
k / / p
previous pair
1 / / h
show query pane
2 / / l
show candidate pane
c
copy suggested comment
r
toggle reasoning
g i
go to index
?
show this help
esc
close overlays

press ? or esc to close

copied