I was trying to build "editors/nano" in pkgsrc, but my build failed on
the following messages:
[...]
checking that C++ compiler can compile simple programs... yes
checking that C++ static constructors and destructors are called... no
configure: error: a working C++ compiler is required
*** Error code 1
Stop.
bmake: stopped in /usr/pkgsrc/textproc/groff
[...]
So, it seems C++ support exists, but is partial with G++. Here's the
most related instance of this I found elsewhere, for NetBSD in this
case: http://mail-index.netbsd.org/port-alpha/2002/11/27/0001.html From that, it seems the trouble could be with "crtbegin.o,"
"crtend.o," and similar files.
From that NetBSD message, a possibility was that libtool needed to be
rebuilt with newer libraries. Unfortunately, rebuilding and installing
it doesn't seem to help.
loading cache ./config.cache
checking host system type... i386-pc-elf
checking target system type... i386-pc-elf
checking build system type... i386-pc-elf
checking for a BSD compatible install... /bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... missing
checking whether make sets ${MAKE}... (cached) yes
checking for gcc... gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for POSIXized ISC... no
checking whether the C compiler (gcc) compiles and links a simple C
program... yes
checking for c++... g++
checking whether the C++ compiler (g++ ) works... yes
checking whether the C++ compiler (g++ ) is a cross-compiler... no
checking whether we are using GNU C++... yes
checking whether g++ accepts -g... yes
checking whether the C++ compiler (g++) compiles a simple program...
no
configure: error: You must set the environment variable CXX to a
working
C++ compiler. Also check the CXXFLAGS settings.
See the file 'config.log' for further diagnostics.
On Aug 20, 5:30 pm, pikpik <pikpik.1...@gmail.com> wrote:
> I was trying to build "editors/nano" in pkgsrc, but my build failed on
> the following messages:
> [...]
> checking that C++ compiler can compile simple programs... yes
> checking that C++ static constructors and destructors are called... no
> configure: error: a working C++ compiler is required
> *** Error code 1
> Stop.
> bmake: stopped in /usr/pkgsrc/textproc/groff
> [...]
> So, it seems C++ support exists, but is partial with G++. Here's the
> most related instance of this I found elsewhere, for NetBSD in this
> case:http://mail-index.netbsd.org/port-alpha/2002/11/27/0001.html > From that, it seems the trouble could be with "crtbegin.o,"
> "crtend.o," and similar files.
> From that NetBSD message, a possibility was that libtool needed to be
> rebuilt with newer libraries. Unfortunately, rebuilding and installing
> it doesn't seem to help.
> loading cache ./config.cache
> checking host system type... i386-pc-elf
> checking target system type... i386-pc-elf
> checking build system type... i386-pc-elf
> checking for a BSD compatible install... /bin/install -c
> checking whether build environment is sane... yes
> checking whether make sets ${MAKE}... yes
> checking for working aclocal... missing
> checking for working autoconf... missing
> checking for working automake... missing
> checking for working autoheader... missing
> checking for working makeinfo... missing
> checking whether make sets ${MAKE}... (cached) yes
> checking for gcc... gcc
> checking whether the C compiler (gcc ) works... yes
> checking whether the C compiler (gcc ) is a cross-compiler... no
> checking whether we are using GNU C... yes
> checking whether gcc accepts -g... yes
> checking for POSIXized ISC... no
> checking whether the C compiler (gcc) compiles and links a simple C
> program... yes
> checking for c++... g++
> checking whether the C++ compiler (g++ ) works... yes
> checking whether the C++ compiler (g++ ) is a cross-compiler... no
> checking whether we are using GNU C++... yes
> checking whether g++ accepts -g... yes
> checking whether the C++ compiler (g++) compiles a simple program...
> no
> configure: error: You must set the environment variable CXX to a
> working
> C++ compiler. Also check the CXXFLAGS settings.
> See the file 'config.log' for further diagnostics.
> On Aug 20, 5:30 pm, pikpik <pikpik.1...@gmail.com> wrote:
> > Hi,
> > I was trying to build "editors/nano" in pkgsrc, but my build failed on
> > the following messages:
> > [...]
> > checking that C++ compiler can compile simple programs... yes
> > checking that C++ static constructors and destructors are called... no
> > configure: error: a working C++ compiler is required
> > *** Error code 1
> > Stop.
> > bmake: stopped in /usr/pkgsrc/textproc/groff
> > [...]
> > So, it seems C++ support exists, but is partial with G++. Here's the
> > most related instance of this I found elsewhere, for NetBSD in this
> > case:http://mail-index.netbsd.org/port-alpha/2002/11/27/0001.html > > From that, it seems the trouble could be with "crtbegin.o,"
> > "crtend.o," and similar files.
> > From that NetBSD message, a possibility was that libtool needed to be
> > rebuilt with newer libraries. Unfortunately, rebuilding and installing
> > it doesn't seem to help.
> > loading cache ./config.cache
> > checking host system type... i386-pc-elf
> > checking target system type... i386-pc-elf
> > checking build system type... i386-pc-elf
> > checking for a BSD compatible install... /bin/install -c
> > checking whether build environment is sane... yes
> > checking whether make sets ${MAKE}... yes
> > checking for working aclocal... missing
> > checking for working autoconf... missing
> > checking for working automake... missing
> > checking for working autoheader... missing
> > checking for working makeinfo... missing
> > checking whether make sets ${MAKE}... (cached) yes
> > checking for gcc... gcc
> > checking whether the C compiler (gcc ) works... yes
> > checking whether the C compiler (gcc ) is a cross-compiler... no
> > checking whether we are using GNU C... yes
> > checking whether gcc accepts -g... yes
> > checking for POSIXized ISC... no
> > checking whether the C compiler (gcc) compiles and links a simple C
> > program... yes
> > checking for c++... g++
> > checking whether the C++ compiler (g++ ) works... yes
> > checking whether the C++ compiler (g++ ) is a cross-compiler... no
> > checking whether we are using GNU C++... yes
> > checking whether g++ accepts -g... yes
> > checking whether the C++ compiler (g++) compiles a simple program...
> > no
> > configure: error: You must set the environment variable CXX to a
> > working
> > C++ compiler. Also check the CXXFLAGS settings.
> > See the file 'config.log' for further diagnostics.
> > On Aug 20, 5:30 pm, pikpik <pikpik.1...@gmail.com> wrote:
> > > Hi,
> > > I was trying to build "editors/nano" in pkgsrc, but my build failed on
> > > the following messages:
> > > [...]
> > > checking that C++ compiler can compile simple programs... yes
> > > checking that C++ static constructors and destructors are called... no
> > > configure: error: a working C++ compiler is required
> > > *** Error code 1
> > > So, it seems C++ support exists, but is partial with G++. Here's the
> > > most related instance of this I found elsewhere, for NetBSD in this
> > > case:http://mail-index.netbsd.org/port-alpha/2002/11/27/0001.html > > > From that, it seems the trouble could be with "crtbegin.o,"
> > > "crtend.o," and similar files.
> > > From that NetBSD message, a possibility was that libtool needed to be
> > > rebuilt with newer libraries. Unfortunately, rebuilding and installing
> > > it doesn't seem to help.
Did you run "make gnu-includes" and "make elf-libraries" in /usr/src?
And are you running the latest base system, 3.2.0? Can you send the
config.log file from ddd?
-Thomas
On Aug 23, 7:18 am, r0ller <r0l...@freemail.hu> wrote:
> > > loading cache ./config.cache
> > > checking host system type... i386-pc-elf
> > > checking target system type... i386-pc-elf
> > > checking build system type... i386-pc-elf
> > > checking for a BSD compatible install... /bin/install -c
> > > checking whether build environment is sane... yes
> > > checking whether make sets ${MAKE}... yes
> > > checking for working aclocal... missing
> > > checking for working autoconf... missing
> > > checking for working automake... missing
> > > checking for working autoheader... missing
> > > checking for working makeinfo... missing
> > > checking whether make sets ${MAKE}... (cached) yes
> > > checking for gcc... gcc
> > > checking whether the C compiler (gcc ) works... yes
> > > checking whether the C compiler (gcc ) is a cross-compiler... no
> > > checking whether we are using GNU C... yes
> > > checking whether gcc accepts -g... yes
> > > checking for POSIXized ISC... no
> > > checking whether the C compiler (gcc) compiles and links a simple C
> > > program... yes
> > > checking for c++... g++
> > > checking whether the C++ compiler (g++ ) works... yes
> > > checking whether the C++ compiler (g++ ) is a cross-compiler... no
> > > checking whether we are using GNU C++... yes
> > > checking whether g++ accepts -g... yes
> > > checking whether the C++ compiler (g++) compiles a simple program...
> > > no
> > > configure: error: You must set the environment variable CXX to a
> > > working
> > > C++ compiler. Also check the CXXFLAGS settings.
> > > See the file 'config.log' for further diagnostics.
> > > On Aug 20, 5:30 pm, pikpik <pikpik.1...@gmail.com> wrote:
> > > > Hi,
> > > > I was trying to build "editors/nano" in pkgsrc, but my build failed on
> > > > the following messages:
> > > > [...]
> > > > checking that C++ compiler can compile simple programs... yes
> > > > checking that C++ static constructors and destructors are called... no
> > > > configure: error: a working C++ compiler is required
> > > > *** Error code 1
> > > > So, it seems C++ support exists, but is partial with G++. Here's the
> > > > most related instance of this I found elsewhere, for NetBSD in this
> > > > case:http://mail-index.netbsd.org/port-alpha/2002/11/27/0001.html > > > > From that, it seems the trouble could be with "crtbegin.o,"
> > > > "crtend.o," and similar files.
> > > > From that NetBSD message, a possibility was that libtool needed to be
> > > > rebuilt with newer libraries. Unfortunately, rebuilding and installing
> > > > it doesn't seem to help.
Yes, I did run make gnu-includes elf-libraries in /usr/src and the
system I'm using is 3.2.0 (the one which can be downloaded from the
minix3 page). So I'm not tracking current. Please, find the config.log
below.
Regards,
r0ller
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
configure:620: checking host system type
configure:641: checking target system type
configure:659: checking build system type
configure:693: checking for a BSD compatible install
configure:746: checking whether build environment is sane
configure:803: checking whether make sets ${MAKE}
configure:843: checking for working aclocal
configure:856: checking for working autoconf
configure:869: checking for working automake
configure:882: checking for working autoheader
configure:895: checking for working makeinfo
configure:909: checking whether make sets ${MAKE}
configure:938: checking for gcc
configure:1051: checking whether the C compiler (gcc ) works
configure:1067: gcc -o conftest conftest.c 1>&5
configure:1093: checking whether the C compiler (gcc ) is a cross-
compiler
configure:1098: checking whether we are using GNU C
configure:1107: gcc -E conftest.c
configure:1126: checking whether gcc accepts -g
configure:1158: checking for POSIXized ISC
configure:1182: checking whether the C compiler (gcc) compiles and
links a simple C program
configure:1203: gcc -o conftest -g -O2 conftest.c 1>&5
configure:1235: checking for c++
configure:1267: checking whether the C++ compiler (g++ ) works
configure:1283: g++ -o conftest conftest.C 1>&5
configure:1309: checking whether the C++ compiler (g++ ) is a cross-
compiler
configure:1314: checking whether we are using GNU C++
configure:1323: g++ -E conftest.C
configure:1342: checking whether g++ accepts -g
configure:1530: checking whether the C++ compiler (g++) compiles a
simple program
configure:1551: g++ -o conftest -g -O2 conftest.C 1>&5
configure:1545:22: error: iostream.h: no such file or directory
configure: In function 'int main()':
configure:1547: error: 'cout' was not declared in this scope
configure: failed program was:
#line 1544 "configure"
#include "confdefs.h"
#include <iostream.h>
int main() {
cout << "hello, world!";
; return 0; }
On Aug 23, 10:54 pm, Thomas Cort <linuxg...@gmail.com> wrote:
> Did you run "make gnu-includes" and "make elf-libraries" in /usr/src?
> And are you running the latest base system, 3.2.0? Can you send the
> config.log file from ddd?
> -Thomas
> On Aug 23, 7:18 am, r0ller <r0l...@freemail.hu> wrote:
> > Hi Thomas,
> > I've just tried it with gcc-4.4.5 and I get the same:(
> > Regards,
> > r0ller
> > On Aug 23, 12:11 pm, Thomas Cort <linuxg...@gmail.com> wrote:
> > > > loading cache ./config.cache
> > > > checking host system type... i386-pc-elf
> > > > checking target system type... i386-pc-elf
> > > > checking build system type... i386-pc-elf
> > > > checking for a BSD compatible install... /bin/install -c
> > > > checking whether build environment is sane... yes
> > > > checking whether make sets ${MAKE}... yes
> > > > checking for working aclocal... missing
> > > > checking for working autoconf... missing
> > > > checking for working automake... missing
> > > > checking for working autoheader... missing
> > > > checking for working makeinfo... missing
> > > > checking whether make sets ${MAKE}... (cached) yes
> > > > checking for gcc... gcc
> > > > checking whether the C compiler (gcc ) works... yes
> > > > checking whether the C compiler (gcc ) is a cross-compiler... no
> > > > checking whether we are using GNU C... yes
> > > > checking whether gcc accepts -g... yes
> > > > checking for POSIXized ISC... no
> > > > checking whether the C compiler (gcc) compiles and links a simple C
> > > > program... yes
> > > > checking for c++... g++
> > > > checking whether the C++ compiler (g++ ) works... yes
> > > > checking whether the C++ compiler (g++ ) is a cross-compiler... no
> > > > checking whether we are using GNU C++... yes
> > > > checking whether g++ accepts -g... yes
> > > > checking whether the C++ compiler (g++) compiles a simple program...
> > > > no
> > > > configure: error: You must set the environment variable CXX to a
> > > > working
> > > > C++ compiler. Also check the CXXFLAGS settings.
> > > > See the file 'config.log' for further diagnostics.
> > > > On Aug 20, 5:30 pm, pikpik <pikpik.1...@gmail.com> wrote:
> > > > > Hi,
> > > > > I was trying to build "editors/nano" in pkgsrc, but my build failed on
> > > > > the following messages:
> > > > > [...]
> > > > > checking that C++ compiler can compile simple programs... yes
> > > > > checking that C++ static constructors and destructors are called... no
> > > > > configure: error: a working C++ compiler is required
> > > > > *** Error code 1
> > > > > So, it seems C++ support exists, but is partial with G++. Here's the
> > > > > most related instance of this I found elsewhere, for NetBSD in this
> > > > > case:http://mail-index.netbsd.org/port-alpha/2002/11/27/0001.html > > > > > From that, it seems the trouble could be with "crtbegin.o,"
> > > > > "crtend.o," and similar files.
> > > > > From that NetBSD message, a possibility was that libtool needed to be
> > > > > rebuilt with newer libraries. Unfortunately, rebuilding and installing
> > > > > it doesn't seem to help.
> [config.log]
> error: iostream.h: no such file or directory
It seems that the issue is with the configure script and not Minix's C+
+ compiler. iostream.h is a pre-ISO standard C++ header. As of
gcc-4.3, it was removed ( See http://gcc.gnu.org/gcc-4.3/porting_to.html ). My suggestion is to regenerate the configure script with autoconf
to get a more up to date C++ feature check.
I gave a try to a newer version (mainly because autoreconf also
failed) hoping that the configure script may be different. Actually,
configuring version 3.3.9 goes far beyond than version 3.2.1. However,
it also fails but now with a complaint to libX11.a -even though I
specified the X includes and X libraries explicitly:
I just copy the end of the configure output here -if it's necessary
later I can paste the whole stuff:)
[...]
checking for XOpenDisplay in -lX11... no
configure: error: The X11 library '-lX11' could not be found.
Please use the configure options '--x-includes=DIR'
and '--x-libraries=DIR' to specify the X location.
See the files 'config.log' and 'ddd/config.log'
for further diagnostics.
Any idea why it can't find that lib?
Regards,
r0ller
On Aug 24, 2:13 pm, Thomas Cort <linuxg...@gmail.com> wrote:
> > [config.log]
> > error: iostream.h: no such file or directory
> It seems that the issue is with the configure script and not Minix's C+
> + compiler. iostream.h is a pre-ISO standard C++ header. As of
> gcc-4.3, it was removed ( Seehttp://gcc.gnu.org/gcc-4.3/porting_to.html > ). My suggestion is to regenerate the configure script with autoconf
> to get a more up to date C++ feature check.
> I gave a try to a newer version (mainly because autoreconf also
> failed) hoping that the configure script may be different. Actually,
> configuring version 3.3.9 goes far beyond than version 3.2.1. However,
> it also fails but now with a complaint to libX11.a -even though I
> specified the X includes and X libraries explicitly:
> I just copy the end of the configure output here -if it's necessary
> later I can paste the whole stuff:)
> [...]
> checking for XOpenDisplay in -lX11... no
> configure: error: The X11 library '-lX11' could not be found.
> Please use the configure options '--x-includes=DIR'
> and '--x-libraries=DIR' to specify the X location.
> See the files 'config.log' and 'ddd/config.log'
> for further diagnostics.
> Any idea why it can't find that lib?
> Regards,
> r0ller
> On Aug 24, 2:13 pm, Thomas Cort <linuxg...@gmail.com> wrote:
> > Hi,
> > > [config.log]
> > > error: iostream.h: no such file or directory
> > It seems that the issue is with the configure script and not Minix's C+
> > + compiler. iostream.h is a pre-ISO standard C++ header. As of
> > gcc-4.3, it was removed ( Seehttp://gcc.gnu.org/gcc-4.3/porting_to.html > > ). My suggestion is to regenerate the configure script with autoconf
> > to get a more up to date C++ feature check.
