Re: [gentoo-user] emerge spamassassin: re2c failed...

2009-05-21 Thread Jarry

Alan McKinnon wrote:


configure:2487: x86_64-pc-linux-gnu-g++ -march=athlon64 - O2 -pipe

   ^
ka-ching!


Arttu V. wrote:

>> CXXFLAGS='-march=athlon64 - O2 -pipe'
>
> Nah, let's make a better guess: most unfortunate typo in
> /etc/make.conf?

Thanks for your help, that fixed the problem. What amazes me, I've
been living with this typo for long time. And never got any complaint.

Jarry




Re: [gentoo-user] emerge spamassassin: re2c failed...

2009-05-21 Thread Alan McKinnon
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



Re: [gentoo-user] emerge spamassassin: re2c failed...

2009-05-21 Thread Arttu V.
On 5/21/09, Jarry  wrote:
> configure:2460: checking for C++ compiler default output file name
> configure:2487: x86_64-pc-linux-gnu-g++ -march=athlon64 - O2 -pipe
> -Wl,-O1 conftest.cpp  >&5
> x86_64-pc-linux-gnu-g++: O2: No such file or directory
> x86_64-pc-linux-gnu-g++: -E or -x required when input is from standard input
> configure:2490: $? = 1

> CFLAGS='-march=athlon64 -O2 -pipe'
> CXXFLAGS='-march=athlon64 - O2 -pipe'

Nah, let's make a better guess: most unfortunate typo in
/etc/make.conf? That single space in CXXFLAGS really makes the maximum
difference? :)

(Sorry about the earlier mails, their formats, etc., I was fighting
with gmail on a non-regular box again.)

-- 
Arttu V.



Re: [gentoo-user] emerge spamassassin: re2c failed...

2009-05-21 Thread Jarry

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


## - ##
## Platform. ##
## - ##

hostname = mail
uname -m = x86_64
uname -r = 2.6.22-vs2.2.0.7-gentoo
uname -s = Linux
uname -v = #2 SMP Fri Mar 20 18:27:58 GMT 2009

/usr/bin/uname -p = AMD Athlon(tm) 64 X2 Dual Core Processor 4800+
/bin/uname -X = unknown

/bin/arch  = unknown
/usr/bin/arch -k   = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo  = unknown
/bin/machine   = unknown
/usr/bin/oslevel   = unknown
/bin/universe  = unknown

PATH: /usr/lib64/portage/bin/ebuild-helpers
PATH: /usr/local/sbin
PATH: /sbin
PATH: /usr/sbin
PATH: /usr/local/bin
PATH: /bin
PATH: /usr/bin
PATH: /opt/bin
PATH: /usr/x86_64-pc-linux-gnu/gcc-bin/4.3.2


## --- ##
## Core tests. ##
## --- ##

configure:1796: checking for a BSD-compatible install
configure:1852: result: /usr/bin/install -c
configure:1863: checking whether build environment is sane
configure:1906: result: yes
configure:1934: checking for a thread-safe mkdir -p
configure:1973: result: /bin/mkdir -p
configure:1986: checking for gawk
configure:2002: found /bin/gawk
configure:2013: result: gawk
configure:2024: checking whether make sets $(MAKE)
configure:2045: result: yes
configure:2252: checking for bison
configure:2268: found /usr/bin/bison
configure:2279: result: bison -y
configure:2305: checking for x86_64-pc-linux-gnu-g++
configure:2321: found /usr/bin/x86_64-pc-linux-gnu-g++
configure:2332: result: x86_64-pc-linux-gnu-g++
configure:2407: checking for C++ compiler version
configure:2414: x86_64-pc-linux-gnu-g++ --version >&5
x86_64-pc-linux-gnu-g++ (Gentoo 4.3.2-r3 p1.6, pie-10.1.5) 4.3.2
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:2417: $? = 0
configure:2424: x86_64-pc-linux-gnu-g++ -v >&5
Using built-in specs.
Target: x86_64-pc-linux-gnu
Configured with: 
/var/tmp/portage/sys-devel/gcc-4.3.2-r3/work/gcc-4.3.2/configure 
--prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.3.2 
--includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.3.2/include 
--datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.3.2 
--mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.3.2/man 
--infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.3.2/info 
--with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.3.2/include/g++-v4 
--host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --disable-altivec 
--disable-fixed-point --enable-nls --without-included-gettext 
--with-system-zlib --disable-checking --disable-werror 
--enable-secureplt --enable-multilib --enable-libmudflap 
--disable-libssp --enable-libgomp --disable-libgcj 
--enable-languages=c,c++,treelang,fortran --enable-shared 
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu 
--with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.3.2-r3 
p1.6, pie-10.1.5'

Thread model: posix
gcc version 4.3.2 (Gentoo 4.3.2-r3 p1.6, pie-10.1.5)
configure:2427: $? = 0
configure:2434: x86_64-pc-linux-gnu-g++ -V >&5
x86_64-pc-linux-gnu-g++: '-V' option must have argument
configure:243

Re: [gentoo-user] emerge spamassassin: re2c failed...

2009-05-21 Thread Alan McKinnon
On Thursday 21 May 2009 10:30:17 Jarry wrote:
> Hi,
>
> 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

-- 
alan dot mckinnon at gmail dot com