rtpengine

4607 Commits

293 Branches

1.2 GiB

Tree: c479b24d66

Commit Graph

Author SHA1 Message Date

Author	SHA1	Message	Date
Guillem Jover	bbf7b2e7b8	MT#61993 build: Force recursive variables into simple ones Starting with GNU make 4.4, build time have massively regressed where before they would take 5m on amd64 now can take 2h40m. While this seems clearly broken, the release notes are filled with notices for breaking changes, and in particular the one for passing all make variables down to the invoked programs executed via the «shell» GNU make function, so it is not clear what is expected breakage and what is not. This has been reported in Debian, but not yet upstream, and while it seems like a clear regression, it's not clear what will be the upstream take on it. For now apply workarounds that do not change semantics, and which do not regress with older GNU make versions. Use the GNU make «origin» function instead of «?=» which defaults to defining a variable as a recursive one. Coerce already defined variables into simple ones to avoid GNU make re-evaluating these variables for each «shell» function invocation. Ref: https://bugs.debian.org/1092051 Change-Id: I076fc05dd616918473a22e7e942fecfdc9851d47 (cherry picked from commit `887fb40f3f`) (cherry picked from commit `67a2b222c7`)	11 months ago
Sjoerd Boomstra	5d75460538	MT#55283 Fixed library path for libbcg729 Reported in #1676 Change-Id: I3fe4c9400e58f6ff2556dcdf4b996805175d303b	3 years ago
Richard Fuchs	d47f4ac427	TT#14008 make bcg729 inclusion conditional on dpkg profile closes #1174 Change-Id: I277986ea30b25633c281291aa956fb2159c386ed	5 years ago

Guillem Jover

bbf7b2e7b8

MT#61993 build: Force recursive variables into simple ones

Starting with GNU make 4.4, build time have massively regressed
where before they would take 5m on amd64 now can take 2h40m. While this
seems clearly broken, the release notes are filled with notices for
breaking changes, and in particular the one for passing all make
variables down to the invoked programs executed via the «shell» GNU make
function, so it is not clear what is expected breakage and what is not.

This has been reported in Debian, but not yet upstream, and while it
seems like a clear regression, it's not clear what will be the upstream
take on it. For now apply workarounds that do not change semantics, and
which do not regress with older GNU make versions.

Use the GNU make «origin» function instead of «?=» which defaults to
defining a variable as a recursive one. Coerce already defined variables
into simple ones to avoid GNU make re-evaluating these variables for
each «shell» function invocation.

Ref: https://bugs.debian.org/1092051
Change-Id: I076fc05dd616918473a22e7e942fecfdc9851d47
(cherry picked from commit 887fb40f3f)
(cherry picked from commit 67a2b222c7)

11 months ago

Sjoerd Boomstra

5d75460538

MT#55283 Fixed library path for libbcg729

Reported in #1676

Change-Id: I3fe4c9400e58f6ff2556dcdf4b996805175d303b

3 years ago

Richard Fuchs

d47f4ac427

TT#14008 make bcg729 inclusion conditional on dpkg profile

closes #1174

Change-Id: I277986ea30b25633c281291aa956fb2159c386ed

5 years ago

3 Commits (c479b24d6616fa636b878332cdc697a59eab9061)