After much pondering on how to best solve the much-needed cleanup for Linux
detection in config.guess, I have made a start. Some of the grossness will
remain with us for some time until I can be sure that there will be very few
users on certain systems--such as a.out SPARC Linux.
In the meantime
On Jan 21, 2001, John Poltorak <[EMAIL PROTECTED]> wrote:
> I'm not really sure where config.h falls into the scheme of building apps
> using AUTO(MAKE|CONF), but I've found that for PATCH to get built on OS/2,
> it requires this single addition to config.h:-
> #define strncasecmp strnicmp
> Ho
On Jan 21, 2001, Matthew Schalit <[EMAIL PROTECTED]> wrote:
> Is this because I have no CXX or F77 at this point?
Quite likely. Would you give CVS autoconf a spin and see how it goes?
It should probably handle the lack of these programs more gracefully.
--
Alexandre Oliva Enjoy Guarana', se
I'm not really sure where config.h falls into the scheme of building apps
using AUTO(MAKE|CONF), but I've found that for PATCH to get built on OS/2,
it requires this single addition to config.h:-
#define strncasecmp strnicmp
How would I go about getting this line included in config.h if...
ch
Hi Folks,
I'm not sure where to post for help. Perhaps this
is the right place. I'm asking for some help checking
the FAIL lines from my gmake check output.
I am trying to compile and test the latest autoconf-2.13,
on UnixWare 7.1.1 using cc.
I am running
UnixWare 7.1.1
gmake 3.79.1
> "trevor" == trevor <[EMAIL PROTECTED]> writes:
trevor> one of the first steps that must take place in order to
trevor> compile is to apply a function called "pswrap" to the "*.psw"
trevor> file to generate both a *.h and a *.c file; much the same as
trevor> using LEX and YACC.
trevor> the
EBGILGEB.EXE
[EMAIL PROTECTED] writes:
> > # With Autoconf 2.50-to-be:
> >
> > $ LIBS='-L/tmp/obscure -ltest' ./configure
> > checking for gcc... gcc
> > checking whether the C compiler works... configure: error: cannot run C compiled
>programs.
> > To enable cross compilation, use `--host'.
> Could you try
Thanks. We must be hitting some internal size limitation I guess. I will
apply the patch you suggest.
Hi,
srcdir and top_srcdir get corrupted with cvs-autoconf, when using
them in AC_OUTPUT_COMMANDS and AC_CONFIG_COMMANDS in packages with
subdirectories.
Example: The configure script in the tarball below contains this:
AC_OUTPUT_COMMANDS(
[echo ""
echo srcdir=$srcdir
echo top_srcdir=$top_s
On Sat, Jan 20, 2001 at 12:22:58AM +0100, Peter Eisentraut wrote:
> I've created a simple shared library that I placed at a non-standard
> location for illustration purposes. Imagine I want to configure a package
> to link against that library:
>
> $ cat configure.in
> AC_INIT(.)
>
> AC_PROG_CC
11 matches
Mail list logo