[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Building a software toolchain that works
From: |
Maxime Devos |
Subject: |
Re: Building a software toolchain that works |
Date: |
Thu, 17 Mar 2022 16:35:14 +0100 |
User-agent: |
Evolution 3.38.3-1 |
David Arroyo schreef op ma 14-03-2022 om 17:40 [-0400]:
> 1. Obtain the source and unpack it into a writable working directory,
> skipping downstream patches and snippets.
Why skip downstream patches and snippets? Often, these are necessry
to make the source actually compileable (e.g. if it uses '/bin/ls'
instead of 'ls', in case of type errrs -- e.g. abiword-explicitly-cast-
bools.patch, autotools changes (agg-am_c_prototype.patch)), remove bugs
(e.g a2ps-CVE-2001-1593)). These patches and snippets exist for a
reason.
Greetings,
Maxime.
signature.asc
Description: This is a digitally signed message part
Re: Building a software toolchain that works, Olivier Dion, 2022/03/14
Re: Building a software toolchain that works, zimoun, 2022/03/17
Re: Building a software toolchain that works, david larsson, 2022/03/18
Re: Building a software toolchain that works, Yasuaki Kudo, 2022/03/18
Windows Subsystem for Linux, zimoun, 2022/03/19
Re: Windows Subsystem for Linux, Ludovic Courtès, 2022/03/24