>>> "Bruce" == Bruce Korb <[EMAIL PROTECTED]> writes:
Bruce> Hi,
Hi,
Bruce> It would be really, really convenient to be able to
Bruce> shell-evaluate the value inserted into the config.h file.
AC_DEFINE_UNQUOTED is indeed really, really convenient :)
[...]
--
Alexandre Duret-Lutz
Title: Configure/make files for cross compilers
Folks,
I need to port some UNIX based code to an embedded OS (VxWorks).
Autoconf/configure is the modus operandus for building the various UNIX flavours. To keep things nice I'd like to try to follow this module.
Is it possible to generate c
Yep. Here's what I do to build my 'linux distribution'.
I have an outer autoconf configure that figures out the location
of compilers and flags needed to cross-compile; it configures
one little wrapper Makefile for each third-party package.
Here's the wrapper Makefile.in I use to build betaftpd (
Dan Kegel wrote:
> ACENV=CC=@IXIA_CROSS_TOOL@gcc CFLAGS="@IXIA_TARGET_CFLAGS@"
> ac_cv_func_mmap_fixed_mapped=yes
That should all have been one line; the ac_cv_func_mmap_fixed_mapped=yes
is supposed to be part of $(ACENV), so it overrides the
environment properly in the line
cd @IXIA_K_ARCH@; $(
> Es schrieb Andrew Kiggins:
>
> Folks,
> I need to port some UNIX based code to an embedded OS (VxWorks).
>
> Autoconf/configure is the modus operandus for building the various
> UNIX flavours. To keep things nice I'd like to try to
> follow this module.
>
> Is it possible to generate configu
source of 27 Mar 2002 17:20GMT
NetBSD-1.5ZC/i386
Failed tests:
GNU Autoconf 2.53a test suite test groups:
NUM: FILENAME:LINE TEST-GROUP-NAME
KEYWORDS
15: m4sh.at:29 LINENO
Skipped tests:
GNU Autoconf 2.53a test suite test groups:
NUM: FILENAME:LINE TEST-GROUP-NAME
I think this is an autoconf bug:
While trying to build libsigc++ on Solaris, with the Sun Forte CC
compiler,we found that our autoconf-generated configure file contains
an unsuitable -z linker switch.
This prevents the project from linking, but we can fix it by
commenting-out the "no_undefined_f
AutoConf;
This may be a Question from the FAQ -- I'd read it if I knew where it
was.
How do I make a AC_CHECK_LIB for a C++ library?
My example looks for cgi_base::configureForServer on different systems
like this:
> AC_CHECK_LIB(cgi, configureForServer__8cgi_basePci)
> AC_CHECK_LIB(cgi, config
Murray Cumming writes:
> I think this is an autoconf bug:
>
> While trying to build libsigc++ on Solaris, with the Sun Forte CC
> compiler,we found that our autoconf-generated configure file contains
> an unsuitable -z linker switch.
-> [EMAIL PROTECTED]
--
Peter Eisentraut [EMAIL PROTECTED]
On Fri, 2002-03-29 at 01:12, Peter Eisentraut wrote:
> Murray Cumming writes:
>
> > I think this is an autoconf bug:
> >
> > While trying to build libsigc++ on Solaris, with the Sun Forte CC
> > compiler,we found that our autoconf-generated configure file contains
> > an unsuitable -z linker swit
Murray Cumming writes:
> > -> [EMAIL PROTECTED]
>
> What are you saying? Are you saying "This might be a libtool bug", or are you
> saying "Use libtool". I have other linker errors if I don't do a
> export LD=CC.
Autoconf does not contain the code you have shown. It's probably a
libtool-related
On Wed, Mar 27, 2002 at 09:00:10PM -0500, Peter Eisentraut wrote:
> # AIX -qlanglvl=ansi
> # Ultrix and OSF/1 -std1
> # HP-UX 10.20 and later -Ae
> # HP-UX older versions -Aa -D_HPUX_SOURCE
> # SVR4 -Xc -D__EXTENSIONS__
>
> where -qlanglvl=ansi and -std1 s
On Fri, Mar 29, 2002 at 01:22:34AM +0100, Murray Cumming wrote:
> On Fri, 2002-03-29 at 01:12, Peter Eisentraut wrote:
> > Murray Cumming writes:
> >
> > > I think this is an autoconf bug:
> > >
> > > While trying to build libsigc++ on Solaris, with the Sun Forte CC
> > > compiler,we found that o
13 matches
Mail list logo
