From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] unixODBC econf failure
Date: Sat, 22 Mar 2008 22:06:27 +0200 [thread overview]
Message-ID: <200803222206.27736.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <1206212759.6449.63.camel@localhost>
On Saturday 22 March 2008, Max wrote:
> Hello,
>
> After updating gnutls revdep-rebuild would like to update an awfull
> lot of packages, including unixODBC. So far no problem but unixODBC
> does not compile. After a while it comes up with the following error
> message:
<shameless crib of request for more info from the forums>
Please post the output of "emerge --info".
Have you changed any of CFLAGS, CXXFLAGS, CHOST or LDFLAGS
in /etc/make.conf recently? Have you changed your profile recently?
Have you upgraded or unmerged ay version of GCC recently? If so, what
was the old value/version and what is the current value/version?
</shameless crib>
also please post 'gcc-config -l'
>
>
> ...
> checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
> checking for C compiler default output file name...
> configure: error: C compiler cannot create executables
> See `config.log' for more details.
>
> !!! Please attach the following file when seeking support:
> !!!
> /var/tmp/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.2.12/gODBCCon
>fig/config.log *
> * ERROR: dev-db/unixODBC-2.2.12 failed.
> * Call stack:
> * ebuild.sh, line 49: Called src_compile
> * environment, line 2622: Called econf 'src_compile'
> 'src_compile' '--host=x86_64-pc-linux-gnu'
> '--with-odbc=/var/tmp/portage/dev-db/unixODBC-2.2.12/work/unixODBC-2.
>2.12' '--enable-static' * ebuild.sh, line 513: Called
> die
> * The specific snippet of code:
> * die "econf failed"
> * The die message:
> * econf failed
> *
> * If you need support, post the topmost build error, and the call
> stack if relevant.
> * A complete build log is located at
> '/var/tmp/portage/dev-db/unixODBC-2.2.12/temp/build.log'.
> * The ebuild environment file is located at
> '/var/tmp/portage/dev-db/unixODBC-2.2.12/temp/environment'.
> *
> ...
>
> The following gcc is installed:
>
> sys-devel/gcc-4.1.2 USE="doc fortran gcj gtk ip28 ip32r10k mudflap
> multislot nls objc objc++ objc-gc (-altivec) -bootstrap -build -d
> (-hardened) -libffi (-multilib) (-n32) (-n64) -nocxx -test -vanilla"
>
> Some information about the system:
>
> CPU: Intel P4D Processor Family 15
> Gentoo: AMD64
>
> CFLAGS="-march=nocona -O2 -pipe -fomit-frame-pointer"
> CXXFLAGS="${CFLAGS}"
>
> Kernel: gentoo 2.6.24-r3
>
> If any further information is needed to solve the problem i'll be
> glad to provide it. Thank you a lot in advance.
>
> cu
> Max
--
Alan McKinnon
alan dot mckinnon at gmail dot com
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-03-22 20:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-22 19:05 [gentoo-user] unixODBC econf failure Max
2008-03-22 20:06 ` Alan McKinnon [this message]
2008-03-22 20:20 ` Max
2008-03-23 8:03 ` Alan McKinnon
2008-03-23 13:05 ` Max
2008-03-23 14:08 ` Alan McKinnon
2008-03-23 20:06 ` Max
2008-03-23 10:49 ` alain.didierjean
2008-03-23 11:42 ` Max
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200803222206.27736.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox