Path: csiph.com!eternal-september.org!feeder.eternal-september.org!nntp.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups: comp.lang.python
Subject: Re: Annoyance building python from source
Date: Wed, 31 Dec 2025 14:47:47 -0800
Organization: None to speak of
Lines: 25
Message-ID: <87bjjew9nw.fsf@example.invalid>
References: <87o6ngvc32.fsf@example.invalid>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Wed, 31 Dec 2025 22:47:48 +0000 (UTC)
Injection-Info: dont-email.me; posting-host="eea1bd566f7c70dcb85fabb9ef2f06cf"; logging-data="3106480"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/VWgalxKvV73m6J8HDsGFU"
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:9ZtP14JXiZfkmZlIvg79IMd8LQQ= sha1:kbY0ZGhCrRCKICMe8tlCdS1RF4o=
Xref: csiph.com comp.lang.python:197656

Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:
> When I build Python from source, the "sudo make install" step
> creates root-owned files in the build directory.  I have not seen
> this while building other open-source packages from source.
>
> Is there a way to avoid this, so no root-owned files are creates
> other than under the target installation directory?
[...]

I received a reply on the python-list mailing list that didn't appear
here.  I can't post to python-list without joining it.

The reply suggested not using "sudo" for "make install".

That could be a workaround, but: 

- I install into a directory owned by root,
- It's easier to use sudo to clean up the generated files, and
- for all the other things I build from source (Python, Ruby, gcc,
  etc.), "sudo make install" doesn't create any root-owned files in
  the source directory; Python's build seems to be unique. 

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */