From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge spamassassin: re2c failed...
Date: Thu, 21 May 2009 11:58:04 +0200 [thread overview]
Message-ID: <200905211158.04988.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <4A151D12.9030904@gmail.com>
On Thursday 21 May 2009 11:21:22 Jarry wrote:
> Alan McKinnon wrote:
> > On Thursday 21 May 2009 10:30:17 Jarry wrote:
> >> I tried to emerge spamassassin, but emerge failed while working
> >> on re2c. I keep getting this error for about 3 days, despite
> >> of syncing/cleaning/rebuilding portage tree. What could be reason
> >> for this problem?
> >>
> >> Log says something about c++ compiler problem. But just a few
> >> days ago I emerged sendmail, without any problem. Why suddenly
> >> c++ does not work?
> >> ---------------------------------------------
> >>
> >> >>> Emerging (14 of 62) dev-util/re2c-0.13.5
> >>
> >> ...
> >> checking for a BSD-compatible install... /usr/bin/install -c
> >> checking whether build environment is sane... yes
> >> checking for a thread-safe mkdir -p... /bin/mkdir -p
> >> checking for gawk... gawk
> >> checking whether make sets $(MAKE)... yes
> >> checking for bison... bison -y
> >> checking for x86_64-pc-linux-gnu-g++... x86_64-pc-linux-gnu-g++
> >> 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-util/re2c-0.13.5/work/re2c-0.13.5/config.log
> >
> > You need to do this first
>
> I'm not sure what you mean. Sending config.log? I did attach it.
> Probably mailing list has cut it off. So I put it directly
> (sorry for long post):
> ______________________________________________________________
>
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
>
> It was created by re2c configure 0.13.5, which was
> generated by GNU Autoconf 2.61. Invocation command line was
>
> $ ./configure --prefix=/usr --build=x86_64-pc-linux-gnu
> --host=x86_64-pc-linux-gnu --mandir=/usr/share/man
> --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
> --localstatedir=/var/lib --libdir=/usr/lib64
[snip]
> configure:2460: checking for C++ compiler default output file name
> configure:2487: x86_64-pc-linux-gnu-g++ -march=athlon64 - O2 -pipe
^
ka-ching!
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2009-05-21 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 8:30 [gentoo-user] emerge spamassassin: re2c failed Jarry
2009-05-21 9:05 ` Alan McKinnon
2009-05-21 9:21 ` Jarry
2009-05-21 9:56 ` Arttu V.
2009-05-21 9:58 ` Alan McKinnon [this message]
2009-05-21 12:31 ` Jarry
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=200905211158.04988.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