Displaying 4 results from an estimated 4 matches for "ac_canonical_target".
2012 Sep 26
1
[LLVMdev] Add --program-prefix support with AC_CANONICAL_TARGET override.
...d. It worked on the usual llvm bots, but failed on
other bots with different configure options.
The patch was reverted as it broke on bots specifying --build, --host,
and --target in configure.
An option is proposed here to change the behavior of program-prefix to
it's normal behavior when AC_CANONICAL_TARGET is not specified. Meaning
--program-prefix can only be set from the configure command line.
--- background
LLVM autoconf/configure.ac uses the AC_CANONICAL_TARGET.
This rule adds a test that can set program_prefix=target if
--program-prefix is not specified on the configure line.
test -n "...
2004 Sep 10
5
detecting host machine in configure.in?
I am trying to set up a flexible infrastructure for the assembly
code. Basically what I want is configure.in determination of
basic machine type (intel/compatible, alpha, ppc), then within
that (say intel) the code will detect variants like MMX, SSE,
and use the right routines.
I know how to do the second, but what is a good way to do the first?
Linux/Cygwin/Solaris seem to support the MACHTYPE
2005 Dec 14
2
Patch: ioloop using kqueue/kevent for FreeBSD
...dovecot-cvs/configure.in
--- old-dovecot-cvs/configure.in 2005-12-14 11:35:03.545823016 +0100
+++ new-dovecot-cvs/configure.in 2005-12-14 11:35:06.150746230 +0100
@@ -1,6 +1,10 @@
AC_INIT(dovecot, 1.0.alpha5, [dovecot@dovecot.org])
AC_CONFIG_SRCDIR([src])
+AC_CANONICAL_BUILD
+AC_CANONICAL_HOST
+AC_CANONICAL_TARGET
+
AC_CONFIG_HEADERS([config.h])
AM_INIT_AUTOMAKE
@@ -327,6 +331,15 @@
])
fi
+if test "$ioloop" = "kqueue"; then
+ AC_CHECK_FUNC(kqueue, [
+ AC_DEFINE(IOLOOP_KQUEUE,, [Implement I/O loop with FreeBSD kqueue()])
+ have_ioloop=yes
+ ], [
+ ioloop=""
+...
2004 Sep 10
0
detecting host machine in configure.in?
...o support the MACHTYPE environment variable.
> Is uname -m or uname -p more reliable? Is there a simple way than
> knowing all the uname -m variants that mean intel 386 compatible?
> (i386, i586, i686, athlon? etc).
The best way to do this is to let autoconf work its magic for you. Use
AC_CANONICAL_TARGET in configure.in, and it will place canonical system type
for the target in the shell variable 'target' in the form
CPU_TYPE-MANUFACTURER-KERNEL-OPERATING_SYSTEM. Be sure to use the target, not
the host, to allow cross-compiling. It will also be broken out into
target_cpu, target_vendor an...