Hi there, I'm getting the very same thing:
"
checking for C++ compiler default output... configure: error: C++ compiler
cannot create executables
See `config.log' for more details.
"
for all of the following packages:
avifile-0.7.32.20030219.ebuild
avifile-0.7.34.20030319.ebuild
avifile-0.7.37.20030522.ebuild
avifile-0.7.37.20030522-r1.ebuild
Output from config.log:
/var/tmp/portage/avifile-0.7.37.20030522-r1/work/avifile0.7-0.7.37/config.log:
configure:1932: checking for i686-pc-linux-gnu-g++
configure:1948: found /usr/bin/i686-pc-linux-gnu-g++
configure:1958: result: i686-pc-linux-gnu-g++
configure:2016: checking for C++ compiler version
configure:2019: i686-pc-linux-gnu-g++ --version </dev/null >&5
Could not run/locate "i686-pc-linux-gnu-g++"
configure:2022: $? = 1
configure:2024: i686-pc-linux-gnu-g++ -v </dev/null >&5
Could not run/locate "i686-pc-linux-gnu-g++"
configure:2027: $? = 1
configure:2029: i686-pc-linux-gnu-g++ -V </dev/null >&5
Could not run/locate "i686-pc-linux-gnu-g++"
configure:2032: $? = 1
configure:2056: checking for C++ compiler default output
configure:2059: i686-pc-linux-gnu-g++ conftest.cc >&5
Could not run/locate "i686-pc-linux-gnu-g++"
configure:2062: $? = 1
configure: failed program was:
| #line 2035 "configure"
| /* confdefs.h. */
|
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE "avifile0.7"
| #define VERSION "0.7.37"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:2101: error: C++ compiler cannot create executables
See `config.log' for more details.
It's a brand new 1.4_rc4 setup, since yesterday. Everything else so far has
been working all right. And I have also emerged a few other packages
afterwards without any problems. I don't think the compiler is kaputt, and
since the package apparently brings it's own CXXFLAGS (according to this
mail thread), then is the problem with it's own flags?
My CFLAGS/CXXFLAGS are:
CFLAGS="-march=athlon -O2 -pipe -fomit-frame-pointer"
I'm unable to descipher the problem of the config.log output. Is it looking
for some strange named g++ executable, or what's going on?
Thankful for any help to fix / work around this problem
Harebrafolk
Jimmy
On Thursday 17 July 2003 11.52, Jens Hoffrichter wrote:
> On Thu, Jul 17, 2003 at 12:19:25AM +0900, Jason Stubbs wrote:
> > > > Can anybody tell me the reason for this? Is this a bug or are some
> > > > packages missing (and even then this is a bug, because then the
> > > > dependencies are not right ;) )
> > >
> > > You have made an error in your CXXFLAGS.
> > >
> > > Write a tiny test program:
> > > int main(int argc,char** argv) { return 0; }
> > >
> > > and try:
> > > ( source /etc/make.globals ; source /etc/make.conf ; \
> > > g++ $CXXFLAGS test.o -o test )
> > >
> > > And it will tell you what is wrong.
> >
> > I agree that it is a problem with the CFLAGS or CXXFLAGS, but I think
> > the above might not show up the problem. Some ebuilds filter out
> > -mfpmath=sse and if you have -mfpmath=sse,387 in CFLAGS it leaves ,387
> > by itself causing the above error.
> >
> > I just checked the ebuild and found that it actually unsets CFLAGS,
> > CXXFLAGS, LDFLAGS, CC and CXX. I'm emerging it now to find out what's
> > going on.
>
> OK, I've done a bit more debugging on this point.
>
> The above program works fine, and my CFLAGS are quite conservative
> (-march=athlon-tbird -O3 -pipe), CXXFLAGS are just $CFLAGS.
>
> I just fetched and unpacked avifile with the ebuild program and
> had manually ran a configure - no error. Then I just tried to
> do a ebuild avifile-${PV} compile, and it exits with the same error
> as ever. When I copy then the configure options and run configure with
> the options the ebuild provides, even THEN it runs perfectly.
>
> I saw then the ebuild provides a couple of more configure options, I
> tried them, but it is still running.
>
> I'm definetely running out of ideas right now ;)
>
> CU all,
> Jens
--
[EMAIL PROTECTED] mailing list
