[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev] Lastrites: net-im/linpopup, app-office/teapot, net-irc/bitchx, sys-power/cpufrequti
From:       Diamond <diamond () hi-net ! ru>
Date:       2014-12-11 19:50:21
Message-ID: 20141211225021.7b357c53 () diamond ! mlzone
[Download RAW message or body]

On Tue, 09 Dec 2014 11:05:31 +0100
Pacho Ramos <pacho@gentoo.org> wrote:

> 
> Regarding the gkrellm-plugins, looks like Fedora is supplying this
> one:
> http://pkgs.fedoraproject.org/cgit/gkrellm-freq.git/tree/gkrellm-freq.spec
> 
> 
 
I rewrote ebuild for gkrellm-gkfreq plugin a bit
 
 https://github.com/cerebrum/dr/blob/master/x11-plugins/gkrellm-gkfreq/gkrellm-gkfreq-2.3.ebuild

And sent this patch upstream

https://github.com/cerebrum/dr/blob/master/x11-plugins/gkrellm-gkfreq/files/gkrellm-gkfreq-2.3-make.patch
https://sourceforge.net/p/gkrellm-gkfreq/feature-requests/2/

Why do we have a function tc-getCC for CC environment variable and why
we don't use CC environment variable automatically? With this patch
CFLAGS and LDFLAGS are substituted automatically without garbage in
ebuild. Why don't we use the same strategy for CC variable?

"Sometimes a package will try to use a bizarre compiler, or will need
to be told which compiler to use. In these situations, the tc-getCC()
function from toolchain-funcs.eclass should be used...
Note: It is not correct to use the ${CC} variable for this purpose."
https://devmanual.gentoo.org/ebuild-writing/functions/src_compile/building/index.html

And why CC variable gives me "cc" but not "x86_64-pc-linux-gnu-gcc" as
it should be? Am I right that it's a bit strange?

[prev in list] [next in list] [prev in thread] [next in thread]