mirror of
https://github.com/espressif/binutils-gdb.git
synced 2025-06-28 15:18:37 +08:00
d389a1a769
The test gdb.python/py-startup-opt.exp checks the behaviour of GDB's: set python dont-write-bytecode on This flag (when on) stops Python creating .pyc files. The test first checks that .pyc files will be created, then turns this option on and checks .pyc files will not be created. However, if the user has PYTHONDONTWRITEBYTECODE set in their environment then this will prevent Python from creating .pyc files, as such the first test, that .pyc files are being created, currently fails. We could unset PYTHONDONTWRITEBYTECODE, however, until Python 3.8 there is no way to control where Python writes the .pyc files. As the GDB developer clearly doesn't want .pyc files created in their file-system it feels wrong to silently unset this environment variable. My proposal then, is that we just spot when this environment variable is set and adjust the expected results. My hope is that across all GDB developers some will be running with PYTHONDONTWRITEBYTECODE unset, so this feature will be fully tested at least some of the time. gdb/testsuite/ChangeLog: PR testsuite/27788 * gdb.python/py-startup-opt.exp (test_python_settings): Change the expected results when environment variable PYTHONDONTWRITEBYTECODE is set.
README for GNU development tools This directory contains various GNU compilers, assemblers, linkers, debuggers, etc., plus their support routines, definitions, and documentation. If you are receiving this as part of a GDB release, see the file gdb/README. If with a binutils release, see binutils/README; if with a libg++ release, see libg++/README, etc. That'll give you info about this package -- supported targets, how to use it, how to report bugs, etc. It is now possible to automatically configure and build a variety of tools with one command. To build all of the tools contained herein, run the ``configure'' script here, e.g.: ./configure make To install them (by default in /usr/local/bin, /usr/local/lib, etc), then do: make install (If the configure script can't determine your type of computer, give it the name as an argument, for instance ``./configure sun4''. You can use the script ``config.sub'' to test whether a name is recognized; if it is, config.sub translates it to a triplet specifying CPU, vendor, and OS.) If you have more than one compiler on your system, it is often best to explicitly set CC in the environment before running configure, and to also set CC when running make. For example (assuming sh/bash/ksh): CC=gcc ./configure make A similar example using csh: setenv CC gcc ./configure make Much of the code and documentation enclosed is copyright by the Free Software Foundation, Inc. See the file COPYING or COPYING.LIB in the various directories, for a description of the GNU General Public License terms under which you can copy the files. REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info on where and how to report problems.