Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 158775

Summary: autoconf cached variables (CC_FOR_BUILD)
Product: Gentoo Linux Reporter: Josef Reidinger <queen.killer>
Component: New packagesAssignee: Gentoo's Team for Core System packages <base-system>
Status: RESOLVED INVALID    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: emerge --info
config.log
config.log of yasm
ls /var/log/portage/
my emerge --info -v

Description Josef Reidinger 2006-12-21 15:54:48 UTC
when compiling with this USE flags USE="X bzip2 readline usb zlib -bindist -curl -ecc -idea -ldap -nls (-selinux) -smartcard -static" LINGUAS="-ru"


make[3]: Entering directory `/var/tmp/portage/app-crypt/gnupg-1.4.6/work/gnupg-1.4.6/doc'
o yat2m ./yat2m.c
make[3]: o: Command not found
make[3]: [yat2m] Error 127 (ignored)
for file in gpg.texi gpgv.texi ; do \
              ./yat2m -I . -D gpgone --release "GnuPG 1.4.6" --source "GNU Privacy Guard" --store \
                  `test -f '$file' || echo './'`$file ; done
/bin/sh: line 1: ./yat2m: No such file or directory
/bin/sh: line 1: ./yat2m: No such file or directory
make[3]: *** [yat2m-stamp] Error 127
Comment 1 Josef Reidinger 2006-12-21 15:56:24 UTC
Created attachment 104546 [details]
emerge --info

maybe some missing dependency on some doc creating tool do this problem.
Comment 2 Alon Bar-Lev (RETIRED) gentoo-dev 2006-12-22 00:05:47 UTC
Can you please attach the config.log?
Should be located at:
/var/tmp/portage/gnupg-1.4.6/work/gnupg-1.4.6/config.log
Comment 3 Josef Reidinger 2006-12-22 03:03:49 UTC
Created attachment 104566 [details]
config.log
Comment 4 Alon Bar-Lev (RETIRED) gentoo-dev 2006-12-22 06:27:00 UTC
It seems you have the following variables cached:
ac_cv_env_CC_FOR_BUILD_set=set
ac_cv_env_CC_FOR_BUILD_value=

Is there any special reason why you use so many none stable components?
Comment 5 Josef Reidinger 2006-12-22 06:52:32 UTC
(In reply to comment #4)
> It seems you have the following variables cached:
> ac_cv_env_CC_FOR_BUILD_set=set
> ac_cv_env_CC_FOR_BUILD_value=
> 
> Is there any special reason why you use so many none stable components?
> 

Hmm, maybe stupid question: How can I delete this cached variable?

I have all system ~amd64. It's my home desktop and I develop software on it, so I prefer the latest lib and application.
Comment 6 Alon Bar-Lev (RETIRED) gentoo-dev 2006-12-23 03:22:34 UTC
I am afraid I don't know how exactly you got this...
Do you use ccache or similar tool?
Comment 7 Josef Reidinger 2006-12-23 03:41:11 UTC
(In reply to comment #6)
> I am afraid I don't know how exactly you got this...
> Do you use ccache or similar tool?
> 

no, I only use compiler.

Maybe is problem in my autotools. Yesterday I emerge yasm and that throw this error
I. -I. -I.  -c -o re2c-main.o `test -f tools/re2c/main.c || echo './'`tools/re2c
/main.c
I. -I. -I.  -c -o re2c-code.o `test -f tools/re2c/code.c || echo './'`tools/re2c
/code.c
I. -I. -I.  -c -o re2c-dfa.o `test -f tools/re2c/dfa.c || echo './'`tools/re2c/d
fa.c
 looks like it take I. instead compiler ....can someone please reassign this bug to autotools maintainer?
Comment 8 Josef Reidinger 2006-12-23 03:45:05 UTC
Created attachment 104627 [details]
config.log of yasm

I see possible problem, it looks like that it cut compiler name and - before first argument. So at first case it may be gcc -o and in second gcc -I. -I. -I....
Comment 9 Alon Bar-Lev (RETIRED) gentoo-dev 2006-12-23 08:53:58 UTC
Yes.
Exactly the same problem:
## ---------------- ##
## Cache variables. ##
## ---------------- ##
ac_cv_env_CC_FOR_BUILD_set=set
ac_cv_env_CC_FOR_BUILD_value=

So CC_FOR_BUILD is set to nothing...
Comment 10 Alon Bar-Lev (RETIRED) gentoo-dev 2006-12-23 08:58:10 UTC
base-system, can you please have a look?
It seems like it is not related to gnupg alone.
Thanks!
Comment 11 Josef Reidinger 2006-12-23 09:51:29 UTC
Created attachment 104644 [details]
ls /var/log/portage/

I attach ls my emerge log, maybe it help, because I successful emerge everythink except yasm and gnupg.
Comment 12 SpanKY gentoo-dev 2006-12-23 09:54:44 UTC
i dont really think it's a bug in the code but a bug in the user's environment

i noticed you havent posted `emerge --info -v`, do so now please
Comment 13 Josef Reidinger 2006-12-23 10:16:32 UTC
Created attachment 104646 [details]
my emerge --info -v

so than is interesting why almost everything work OK and some package have problem.
Comment 14 SpanKY gentoo-dev 2008-04-14 02:50:06 UTC
so it's not coming directly from your environment, but it may be elsewhere

if you're still having this problem, run `emerge --debug yasm` and post the output as an attachment