Re: configure: error: no acceptable C compiler found in $PATH (+possible solution)

Ralf Wildenhues <[EMAIL PROTECTED]> writes: >> [EMAIL PROTECTED] PATH >> -Absolute names of files, including programs. > > What was this change for? AC_PATH_PROG and the like still exist, no? They exist but they don't follow that naming convention. AC_PATH_PROG has that name because it looks in

Re: configure: error: no acceptable C compiler found in $PATH (+possible solution)

Hello Paul, One very small nit: * Paul Eggert wrote on Wed, Jun 13, 2007 at 06:53:15PM CEST: > * doc/autoconf.texi (Special Shell Variables): Warn about FPATH. > (Macro Names, Defining Directories): Don't mention PATH as a name > for a fully qualified file name, as this usage v

Re: configure: error: no acceptable C compiler found in $PATH (+possible solution)

Thanks for the bug report. I audited Autoconf looking for PATH glitches and installed this patch: 2007-06-13 Paul Eggert <[EMAIL PROTECTED]> * lib/m4sugar/m4sh.m4 (_AS_PATH_SEPARATOR_PREPARE): Set FPATH too. Problem reported by Fred Kreek in

Re: Configure error

On Fri, Jun 17, 2005 at 10:29:51AM +0200, Wernher Friedrich wrote: > I am trying to do a cross compilation, but the configure script is telling > me, that it does not find my Berkeley db.h file and that it is not the > right version and that it is not compilable. > > I am 100% sure that I have t

Re: ./configure error

Hello, thank you for your bug report. On Tue, Mar 22, 2005 at 04:29:44PM +0100, Kjell Arne Rekaa wrote: > I've got this error message while running: > -- > bash-2.05$ ./configure# (for bash-3.0) > . > .. > checking sys/ptem.h usability... n