bug#43950: closed (lz4 CC=gcc - Why?)

[GNU bug Tracking System]

Your message dated Mon, 12 Oct 2020 15:18:26 +0200
with message-id <87eem3invh.fsf@nckx>
and subject line Re: bug#43950: lz4 CC=gcc - Why?
has caused the debbugs.gnu.org bug report #43950,
regarding lz4 CC=gcc - Why?
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
43950: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=43950
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: lz4 CC=gcc - Why? Date: Mon, 12 Oct 2020 14:21:53 +0200

* lz4 has "CC=gcc".  Shouldn't that be (string-append "CC=" (cc-for-target)) ?

pgp9aSmIotPca.pgp
Description: OpenPGP digital signature

--- End Message ---

--- Begin Message --- Subject: Re: bug#43950: lz4 CC=gcc - Why? Date: Mon, 12 Oct 2020 15:18:26 +0200

Danny,

Danny Milosavljevic 写道：

lz4 CC=gcc - Why?

For the same reason as the *hundreds* of other ‘CC=gcc’ occurrences in the tree: CC-FOR-TARGET is new. Out of all of them, why are you so interested in LZ4 (I think this is your second mail on it :-)?

I'm currently slogging through the "CC=gcc"s & removing as many as possible; not fun work but can be done completely off-line.

LZ4 tweaked in 2b6ecdf41a09ab9ecae06d7c537583a2f0f28efc,

T G-R

signature.asc
Description: PGP signature

--- End Message ---