GNU bug report logs - #43950
lz4 CC=gcc - Why?

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Subject: bug#43950: closed (Re: bug#43950: lz4 CC=gcc - Why?)
Date: Mon, 12 Oct 2020 13:19:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#43950: lz4 CC=gcc - Why?

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 43950 <at> debbugs.gnu.org.

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

[Message part 2 (message/rfc822, inline)]

From: Tobias Geerinckx-Rice <me <at> tobias.gr>
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: 43950-done <at> debbugs.gnu.org
Subject: Re: bug#43950: lz4 CC=gcc - Why?
Date: Mon, 12 Oct 2020 15:18:26 +0200

[Message part 3 (text/plain, inline)]

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 (application/pgp-signature, inline)]

[Message part 5 (message/rfc822, inline)]

From: Danny Milosavljevic <dannym <at> scratchpost.org>
To: <bug-guix <at> gnu.org>
Subject: lz4 CC=gcc - Why?
Date: Mon, 12 Oct 2020 14:21:53 +0200

[Message part 6 (text/plain, inline)]

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

[Message part 7 (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.