From: Michael Tokarev <mjt@tls.msk.ru>
To: Akihiko Odaki <akihiko.odaki@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: get_relocated_path: the configured paths are not looked for?
Date: Sun, 23 Apr 2023 21:33:43 +0300 [thread overview]
Message-ID: <8bbe3316-2020-e995-9b57-d6a93da4ab1f@msgid.tls.msk.ru> (raw)
In-Reply-To: <dfa9e438-d1be-caec-6320-c5f196ced2f5@gmail.com>
23.04.2023 21:24, Akihiko Odaki wrote:
> The output ends with:
> gcc: fatal error: cannot execute 'cc1': execvp: No such file or directory
> compilation terminated.
$ cd /tmp; printf '#include <stdio.h>\nint main(){puts("Hello!");return 0;}' > hello.c; cp /usr/bin/gcc .; ./gcc hello.c; ./a.out ; ./gcc --version;
ls -l gcc; cd /tmp
Hello!
gcc (Debian 12.2.0-14) 12.2.0
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
-rwxr-xr-x 1 mjt mjt 1301496 апр 23 21:30 gcc*
This is debian bookworm. Ditto for debian bullseye (gcc-10 is in there).
It is interesting that it doesn't work, say, in a subdir of /tmp/, the
same way as in your case above.
Still, GCC is an exception. It is very rare.
/mjt
next prev parent reply other threads:[~2023-04-23 18:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 7:32 get_relocated_path: the configured paths are not looked for? Michael Tokarev
2023-04-20 5:29 ` Akihiko Odaki
2023-04-23 10:28 ` Michael Tokarev
2023-04-23 11:22 ` Akihiko Odaki
2023-04-23 11:31 ` Michael Tokarev
2023-04-23 11:47 ` Akihiko Odaki
2023-04-23 13:22 ` Michael Tokarev
2023-04-23 17:39 ` Akihiko Odaki
2023-04-23 18:10 ` Michael Tokarev
2023-04-23 18:24 ` Akihiko Odaki
2023-04-23 18:33 ` Michael Tokarev [this message]
2023-04-23 18:37 ` Michael Tokarev
2023-04-23 18:39 ` Akihiko Odaki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8bbe3316-2020-e995-9b57-d6a93da4ab1f@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=akihiko.odaki@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).