All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>,
	Mark Brown <broonie@kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: linux-next: Tree for Sep 19 (make htmldocs problem)
Date: Sun, 21 Sep 2025 13:27:48 -0600	[thread overview]
Message-ID: <87cy7jbo7f.fsf@trenco.lwn.net> (raw)
In-Reply-To: <e2112be7-ba68-43d1-92ba-98adfb869a95@infradead.org>

Randy Dunlap <rdunlap@infradead.org> writes:

> lrwxrwxrwx 1 root root 4 Sep 11 01:42 /usr/bin/sphinx-build -> alts*
>
> $ file  /usr/bin/alts
> /usr/bin/alts: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 4.3.0, BuildID[sha1]=17681640c9985eb36ae6d9eca0f08159509386c4, stripped

That is clearly the problem, when combined with this code in
sphinx-build-wrapper:

>             if self.venv:
>                 cmd = ["python"]
>             else:
>                 cmd = [sys.executable,]
> 
>             cmd += [sphinx_build]

Mauro, what is the reason for explicitly interposing the interpreter
there rather than just invoking the sphinx-build binary directly?  It
seems like we could take that out and make this problem go away?

Thanks,

jon

  reply	other threads:[~2025-09-21 19:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-19 15:05 linux-next: Tree for Sep 19 Mark Brown
2025-09-21  0:17 ` linux-next: Tree for Sep 19 (make htmldocs problem) Randy Dunlap
2025-09-21  8:43   ` Akira Yokosawa
2025-09-21 14:03   ` Jonathan Corbet
2025-09-21 15:59     ` Randy Dunlap
2025-09-21 19:27       ` Jonathan Corbet [this message]
2025-09-21 20:32         ` Mauro Carvalho Chehab
2025-09-21 20:44           ` Jonathan Corbet
2025-09-21 21:43             ` Mauro Carvalho Chehab
2025-09-21 21:56               ` Jonathan Corbet
2025-09-21 22:06                 ` Mauro Carvalho Chehab
2025-09-21 21:10           ` Mauro Carvalho Chehab

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=87cy7jbo7f.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=broonie@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.