Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #197656
| From | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: Annoyance building python from source |
| Date | 2025-12-31 14:47 -0800 |
| Organization | None to speak of |
| Message-ID | <87bjjew9nw.fsf@example.invalid> (permalink) |
| References | <87o6ngvc32.fsf@example.invalid> |
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 */
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar
Annoyance building python from source Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-12-29 20:16 -0800 Re: Annoyance building python from source Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2025-12-31 14:47 -0800
csiph-web