mirror of
https://sourceware.org/git/binutils-gdb.git
synced 2025-01-30 12:44:10 +08:00
9b8ffbf410
On aarch64-linux, I noticed the compile command didn't work at all. It always gave the following error: aarch64-linux-gnu-g++: error: : No such file or directory Turns out we're passing an empty argv entry to GCC (because aarch64 doesn't have a -m64 option), and GCC's behavior is to think that is a file it needs to open. One can reproduce it like so: gcc "" "" "" "" gcc: error: : No such file or directory gcc: error: : No such file or directory gcc: error: : No such file or directory gcc: error: : No such file or directory gcc: fatal error: no input files compilation terminated. The solution is to check for an empty string and skip adding that to argv. Regression tested on aarch64-linux/Ubuntu 18.04/20.04. gdb/ChangeLog: 2021-03-29 Luis Machado <luis.machado@linaro.org> * compile/compile.c (get_args): Don't add empty argv entries. |
||
---|---|---|
.. | ||
compile-c-support.c | ||
compile-c-symbols.c | ||
compile-c-types.c | ||
compile-c.h | ||
compile-cplus-symbols.c | ||
compile-cplus-types.c | ||
compile-cplus.h | ||
compile-internal.h | ||
compile-loc2c.c | ||
compile-object-load.c | ||
compile-object-load.h | ||
compile-object-run.c | ||
compile-object-run.h | ||
compile.c | ||
compile.h | ||
gcc-c-plugin.h | ||
gcc-cp-plugin.h |