From: Akihiko Odaki <akihiko.odaki@gmail.com>
To: Michael Tokarev <mjt@tls.msk.ru>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: get_relocated_path: the configured paths are not looked for?
Date: Mon, 24 Apr 2023 03:39:35 +0900 [thread overview]
Message-ID: <62fdda3d-095a-679a-4579-0d20cef93e4e@gmail.com> (raw)
In-Reply-To: <635b7a76-9972-1c5a-5215-1d148a098e37@msgid.tls.msk.ru>
On 2023/04/24 3:37, Michael Tokarev wrote:
> 23.04.2023 21:33, Michael Tokarev пишет:
>
>> $ 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!
>
> execve("/tmp/../lib/gcc/x86_64-linux-gnu/12/cc1", [...])
>
> Since this is merged-usr system, it finds its component just fine,
> that's why it works here in /tmp, doesn't work in a subdir of /tmp,
> and doesn't work in your case (non-merged /usr).
>
>> Still, GCC is an exception. It is very rare.
Oh, I was just wondering why it worked and digging what's going on.
Thanks for the answer.
Well, I have nothing to say GCC is an exception or not, but it's
certainly an important program so I still think it's better to talk with
GCC packagers (and upstream developers perhaps?)
Regards,
Akihiko Odaki
>
> /mjt
>
prev parent reply other threads:[~2023-04-23 18:40 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
2023-04-23 18:37 ` Michael Tokarev
2023-04-23 18:39 ` Akihiko Odaki [this message]
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=62fdda3d-095a-679a-4579-0d20cef93e4e@gmail.com \
--to=akihiko.odaki@gmail.com \
--cc=mjt@tls.msk.ru \
--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).