STDCXX issue

2020-01-20 Thread Vincent Blondel
Hi all, I am totally new with auto tools :-) When trying to make a very first project, I do encounter always the same issue with _CXX_COMPILE_STDCXX macro. Below the current content of both configure.ac and Makefile.am $ configure.ac AC_CONFIG_MACRO_DIRS([m4]) m4_pattern_allow([AC_PROG_CC_C99])

Re: STDCXX issue

2020-01-20 Thread Vincent Blondel
both ..._stdcxxx.m4 files are in the m4 subfolder ... is that not enough ? On Mon, Jan 20, 2020 at 3:02 PM Bob Friesenhahn < bfrie...@simple.dallas.tx.us> wrote: > On Mon, 20 Jan 2020, Vincent Blondel wrote: > > > BUT when doing the configure script I

Re: STDCXX issue

2020-01-20 Thread Vincent Blondel
this is the run with warnings ... $ autoreconf --verbose --force --install --warnings=all autoreconf-2.69: Entering directory `.' autoreconf-2.69: configure.ac: not using Gettext autoreconf-2.69: running: aclocal --force --warnings=all ${ACLOCAL_FLAGS} -I m4 autoreconf-2.69: configure.ac: tracing

Re: STDCXX issue

2020-01-23 Thread Vincent Blondel
Thank You for your help It works now Vincent On Tue, Jan 21, 2020 at 4:37 PM Zack Weinberg wrote: > On Tue, Jan 21, 2020 at 10:18 AM Zack Weinberg wrote: > > > > The `aclocal` program (which is run by autoreconf) is supposed to > > generate aclocal.m4, though. I strongly suspect the missing A

Makefile.am target name prefix *.o

2020-02-01 Thread Vincent Blondel
Hello, Encounter a strange behaviour with autoconf. I do not understand why all the compiled *.o files are prefixed with target-xxx.o. Below an example ... have no progname yet for my executable hence let's call it main for now ... bin_PROGRAMS = main main_SOURCES = obj1.cc obj2.cc Executable

Re: Makefile.am target name prefix *.o

2020-02-02 Thread Vincent Blondel
Thank You for the detailed answer :-) -V. On Sat, Feb 1, 2020 at 9:58 PM Russ Allbery wrote: > Vincent Blondel writes: > > > Encounter a strange behaviour with autoconf. > > I do not understand why all the compiled *.o files are prefixed with > > target-xxx.o. > &g

checking for C compiler default output...

2002-09-12 Thread vincent blondel
Hi all, I am trying to compile all packages for a Linux from Scratch installation but I encounter problem with the compilation. I am using Mandrake 8.2 on a AMD Athlon Xp1600+ and I got following messages. checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux

Re: checking for C compiler default output...

2002-09-12 Thread vincent blondel
Thursday, September 12, 2002 7:35 PM Subject: Re: checking for C compiler default output... > vincent blondel writes: > > Hi all, > > > > I am trying to compile all packages for a Linux from Scratch installation > > but I encounter problem with the compilation. > > I