[Prev Page][Next Page]
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: autoconf tests and stdcall name mangling
- From: Dimitrios Apostolou <jimis@xxxxxxx>
- Re: autoconf tests and stdcall name mangling
- From: Dimitrios Apostolou <jimis@xxxxxxx>
- Re: autoconf tests and stdcall name mangling
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: autoconf tests and stdcall name mangling
- From: Zack Weinberg <zackw@xxxxxxxxx>
- Re: autoconf tests and stdcall name mangling
- From: Dimitrios Apostolou <jimis@xxxxxxx>
- Re: autoconf tests and stdcall name mangling
- From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
- autoconf tests and stdcall name mangling
- From: Dimitrios Apostolou <jimis@xxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Pavel Raiskup <praiskup@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Earnie Boyd <earnie@xxxxxxxxxxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Ben Elliston <bje@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Pavel Raiskup <praiskup@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Jan Engelhardt <jengelh@xxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Ben Elliston <bje@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Earnie Boyd <earnie@xxxxxxxxxxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Earnie Boyd <earnie@xxxxxxxxxxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Ben Elliston <bje@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Ben Elliston <bje@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Earnie Boyd <earnie@xxxxxxxxxxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Ben Elliston <bje@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Earnie Boyd <earnie@xxxxxxxxxxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Ben Elliston <bje@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Pavel Raiskup <praiskup@xxxxxxxxxx>
- Re: distcheck missing files
- From: Kip Warner <kip@xxxxxxxxxxxxxx>
- Re: distcheck missing files
- From: Kip Warner <kip@xxxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
- Re: distcheck missing files
- From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
- Re: distcheck missing files
- From: Kip Warner <kip@xxxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Wookey <wookey@xxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Paul Smith <psmith@xxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Paul Wise <pabs3@xxxxxxxxxxxxx>
- Re: distcheck missing files
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Eric Blake <eblake@xxxxxxxxxx>
- distcheck missing files
- From: Kip Warner <kip@xxxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Paul Wise <pabs3@xxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Pavel Raiskup <praiskup@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Paul Wise <pabs3@xxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Pavel Raiskup <praiskup@xxxxxxxxxx>
- Re: config.status: error: cannot find input file: `po/Makefile.in.in'
- From: Kip Warner <kip@xxxxxxxxxxxxxx>
- Re: config.status: error: cannot find input file: `po/Makefile.in.in'
- From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
- config.status: error: cannot find input file: `po/Makefile.in.in'
- From: Kip Warner <kip@xxxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Paul Wise <pabs3@xxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Warren Young <warren@xxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Warren Young <warren@xxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Paul Wise <pabs3@xxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Wookey <wookey@xxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Warren Young <warren@xxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Ralf Corsepius <ralf.corsepius@xxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Ralf Corsepius <ralf.corsepius@xxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: configure complexity
- From: Mona Pinjani <monap@xxxxxxxxxxxxx>
- Re: [Desperate] call for help with preparing an autotools-based package
- From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
- Re: configure complexity
- From: Bruce Korb <bkorb@xxxxxxx>
- Re: configure complexity
- From: Bruce Korb <bkorb@xxxxxxx>
- Re: Autoconf does not like "-D_FORTIFY_SOURCE=2 -O2"
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: Autoconf does not like "-D_FORTIFY_SOURCE=2 -O2"
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- [Desperate] call for help with preparing an autotools-based package
- From: Panicz Maciej Godek <godek.maciek@xxxxxxxxx>
- Re: Autoconf does not like "-D_FORTIFY_SOURCE=2 -O2"
- From: Zack Weinberg <zackw@xxxxxxxxx>
- Re: Autoconf does not like "-D_FORTIFY_SOURCE=2 -O2"
- From: Allan McRae <allan@xxxxxxxxxxxxx>
- Re: Autoconf does not like "-D_FORTIFY_SOURCE=2 -O2"
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: Autoconf does not like "-D_FORTIFY_SOURCE=2 -O2"
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: Autoconf does not like "-D_FORTIFY_SOURCE=2 -O2"
- From: Allan McRae <allan@xxxxxxxxxxxxx>
- Re: Autoconf does not like "-D_FORTIFY_SOURCE=2 -O2"
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: Autoconf does not like "-D_FORTIFY_SOURCE=2 -O2"
- From: Anatol Pomozov <anatol.pomozov@xxxxxxxxx>
- Re: Autoconf does not like "-D_FORTIFY_SOURCE=2 -O2"
- From: Ralf Corsepius <rc040203@xxxxxxxxxx>
- Re: Autoconf does not like "-D_FORTIFY_SOURCE=2 -O2"
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: Autoconf does not like "-D_FORTIFY_SOURCE=2 -O2"
- From: Zack Weinberg <zackw@xxxxxxxxx>
- Re: Autoconf does not like "-D_FORTIFY_SOURCE=2 -O2"
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: Autoconf does not like "-D_FORTIFY_SOURCE=2 -O2"
- From: Zack Weinberg <zackw@xxxxxxxxx>
- Re: Autoconf does not like "-D_FORTIFY_SOURCE=2 -O2"
- From: Allan McRae <allan@xxxxxxxxxxxxx>
- Re: Autoconf does not like "-D_FORTIFY_SOURCE=2 -O2"
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Autoconf does not like "-D_FORTIFY_SOURCE=2 -O2"
- From: Anatol Pomozov <anatol.pomozov@xxxxxxxxx>
- Re: [possibly OT] Updated giant inventory of headers available on various OSes
- From: Zack Weinberg <zackw@xxxxxxxxx>
- Re: [possibly OT] Updated giant inventory of headers available on various OSes
- From: Jason Curl <jcurlnews@xxxxxxxx>
- [possibly OT] Updated giant inventory of headers available on various OSes
- From: Zack Weinberg <zackw@xxxxxxxxx>
- Failure in make dist
- From: Jason Curl <jcurlnews@xxxxxxxx>
- Re: Preserving generated files
- From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
- Preserving generated files
- From: "A.P. Horst" <ariehorst@xxxxxxxxx>
- Re: Looking for an installed font
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Looking for an installed font
- From: Andreas Röver <andreas_roever@xxxxxx>
- Re: Feature suggestion: Option to generate a Makefile include file containing assignments for all of the output variables
- From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
- Re: Configure for non-gcc compiler
- From: "A.P. Horst" <ariehorst@xxxxxxxxx>
- Re: Configure for non-gcc compiler
- From: Bastien ROUCARIES <roucaries.bastien@xxxxxxxxx>
- Re: Configure for non-gcc compiler
- From: Miles Bader <miles@xxxxxxx>
- Re: Configure for non-gcc compiler
- From: "A.P. Horst" <ariehorst@xxxxxxxxx>
- Re: Configure for non-gcc compiler
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: Configure for non-gcc compiler
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: Configure for non-gcc compiler
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Configure for non-gcc compiler
- From: "A.P. Horst" <ariehorst@xxxxxxxxx>
- Re: Autoconf Digest, Vol 108, Issue 12
- From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
- Re: autoconf/tools produces to many top level files
- From: Miles Bader <miles@xxxxxxx>
- Re: autoconf/tools produces to many top level files
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: autoconf/tools produces to many top level files
- From: Bob Rossi <bob@xxxxxxxxxx>
- Re: Link tests when cross compiling
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: Link tests when cross compiling
- From: NightStrike <nightstrike@xxxxxxxxx>
- Re: How does one configure in directories with special characters in them?
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: Link tests when cross compiling
- From: Eric Blake <eblake@xxxxxxxxxx>
- How does one configure in directories with special characters in them?
- From: Jeff Johnston <jjohnstn@xxxxxxxxxx>
- Re: Link tests when cross compiling
- From: NightStrike <nightstrike@xxxxxxxxx>
- Re: Link tests when cross compiling
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: Link tests when cross compiling
- From: NightStrike <nightstrike@xxxxxxxxx>
- Re: Link tests when cross compiling
- From: Eric Blake <eblake@xxxxxxxxxx>
- Link tests when cross compiling
- From: NightStrike <nightstrike@xxxxxxxxx>
- Re: autoconf/tools produces to many top level files
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: autoconf/tools produces to many top level files
- From: Bert Wesarg <bert.wesarg@xxxxxxxxxxxxxx>
- autoconf/tools produces to many top level files
- From: Bob Rossi <bob@xxxxxxxxxx>
- Re: license question
- From: Peter Gavin <pgavin@xxxxxxxxx>
- Re: license question
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- license question
- From: Peter Gavin <pgavin@xxxxxxxxx>
- Re: Functions used by init before defined
- From: jeremy <jermccormick@xxxxxxxxx>
- Re: Functions used by init before defined
- From: Eric Blake <eblake@xxxxxxxxxx>
- Functions used by init before defined
- From: jeremy <jermccormick@xxxxxxxxx>
- Checks for "SQL Gateway C Precompiler"
- From: Jens Rehsack <rehsack@xxxxxxxxx>
- Re: Feature suggestion: Option to generate a Makefile include file containing assignments for all of the output variables
- From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
- Re: Autoreconf stops with "non-POSIX variable name"
- From: oborchert <borchert@xxxxxxxx>
- RE: Autoreconf stops with "non-POSIX variable name"
- From: "Borchert, Oliver" <oliver.borchert@xxxxxxxx>
- Re: Autoreconf stops with "non-POSIX variable name"
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: Autoreconf stops with "non-POSIX variable name"
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: Feature suggestion: Option to generate a Makefile include file containing assignments for all of the output variables
- From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
- Feature suggestion: Option to generate a Makefile include file containing assignments for all of the output variables
- From: Gavin Smith <gavinsmith0123@xxxxxxxxx>
- Re: Autoreconf stops with "non-POSIX variable name"
- From: Peter Johansson <trojkan@xxxxxxxxx>
- Re: Autoreconf stops with "non-POSIX variable name"
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: Autoreconf stops with "non-POSIX variable name"
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Autoreconf stops with "non-POSIX variable name"
- From: oborchert <borchert@xxxxxxxx>
- Re: AX_CREATE_PKGCONFIG_INFO and hardcoded paths
- From: LRN <lrn1986@xxxxxxxxx>
- Re: AX_CREATE_PKGCONFIG_INFO and hardcoded paths
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: AX_CREATE_PKGCONFIG_INFO and hardcoded paths
- From: Eric Blake <eblake@xxxxxxxxxx>
- AX_CREATE_PKGCONFIG_INFO and hardcoded paths
- From: LRN <lrn1986@xxxxxxxxx>
- Re: Cross-platform availability of header files
- From: Trent Nelson <trent@xxxxxxxxxxxxx>
- Re: Cross-platform availability of header files
- From: Zack Weinberg <zackw@xxxxxxxxx>
- Re: AC_CHECK_HEADER question
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: AC_CHECK_HEADER question
- From: Jan van Dijk <jan@xxxxxxxxxxxxxxxxxx>
- Re: AC_CHECK_HEADER question
- From: Jan van Dijk <jan@xxxxxxxxxxxxxxxxxx>
- Re: AC_CHECK_HEADER question
- From: Zack Weinberg <zackw@xxxxxxxxx>
- Re: AC_CHECK_HEADER question
- From: Peter Johansson <trojkan@xxxxxxxxx>
- Re: AC_CHECK_HEADER question
- From: Jan van Dijk <jan@xxxxxxxxxxxxxxxxxx>
- Re: AC_CHECK_HEADER question
- From: Rhys Ulerich <rhys.ulerich@xxxxxxxxx>
- AC_CHECK_HEADER question
- From: "Dijk, J. van" <J.v.Dijk@xxxxxx>
- Re: Cross-platform availability of header files
- From: Zack Weinberg <zackw@xxxxxxxxx>
- Re: Cross-platform availability of header files
- From: Ralf Corsepius <ralf.corsepius@xxxxxxxxx>
- Re: Cross-platform availability of header files
- From: Peter Rosin <peda@xxxxxxxxxxxxxx>
- Re: Cross-platform availability of header files
- From: Zack Weinberg <zackw@xxxxxxxxx>
- Re: Cross-platform availability of header files
- From: Zack Weinberg <zackw@xxxxxxxxx>
- Re: Cross-platform availability of header files
- From: Zack Weinberg <zackw@xxxxxxxxx>
- Re: Cross-platform availability of header files
- From: Zack Weinberg <zackw@xxxxxxxxx>
- Re: Cross-platform availability of header files
- From: Peter Rosin <peda@xxxxxxxxxxxxxx>
- Re: Cross-platform availability of header files
- From: Ralf Corsepius <ralf.corsepius@xxxxxxxxx>
- Re: Cross-platform availability of header files
- From: Thomas Jahns <jahns@xxxxxxx>
- Re: Cross-platform availability of header files
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: Cross-platform availability of header files
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: Cross-platform availability of header files
- From: Zack Weinberg <zackw@xxxxxxxxx>
- Re: Cross-platform availability of header files
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Cross-platform availability of header files
- From: Zack Weinberg <zackw@xxxxxxxxx>
- Re: meaning autotest exit code 13
- From: djien <djienaijkwee@xxxxxxxxx>
- Re: meaning autotest exit code 13
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: meaning autotest exit code 13
- From: djien <djienaijkwee@xxxxxxxxx>
- Re: meaning autotest exit code 13
- From: Eric Blake <eblake@xxxxxxxxxx>
- meaning autotest exit code 13
- From: djien <djienaijkwee@xxxxxxxxx>
- Using AC_SEARCH_LIBS with Fortran95/2003 library
- From: Paul van Delst <paul.vandelst@xxxxxxxx>
- Fwd: autoconf-mode: mark autoconf functions as builtin
- From: "Arne Babenhauserheide (IMK)" <arne.babenhauserheide@xxxxxxx>
- Re: configure.in still mentioned in autoupdate manpage
- From: Eric Blake <eblake@xxxxxxxxxx>
- configure.in still mentioned in autoupdate manpage
- From: Pavel Raiskup <praiskup@xxxxxxxxxx>
- Re: How to NOT include ($CFLAGS) in LINK?
- From: Ralf Corsepius <rc040203@xxxxxxxxxx>
- Re: How to NOT include ($CFLAGS) in LINK?
- From: Vania Joloboff <vania.joloboff@xxxxxxxx>
- configure rebuild rule not passing on -I to aclocal
- From: Warren Young <warren@xxxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Miles Bader <miles@xxxxxxx>
- Re: Enabling compiler warning flags
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: case change in m4_foreach()
- From: Eric Blake <eblake@xxxxxxxxxx>
- case change in m4_foreach()
- From: Robert Boehne <robertb@xxxxxxxxxx>
- [PATCH] AC_CONFIG_COMMANDS_PRE/POST: fix nested command registrations.
- From: Nick Bowler <nbowler@xxxxxxxxxx>
- Re: Recursive AC_CONFIG_COMMANDS_PRE?
- From: Nick Bowler <nbowler@xxxxxxxxxx>
- Re: Need for --build with --host when cross-compiling ?
- From: Keith Marshall <keith.d.marshall@xxxxxxxxxxxx>
- Re: Need for --build with --host when cross-compiling ?
- From: Jan Engelhardt <jengelh@xxxxxxx>
- Re: Need for --build with --host when cross-compiling ?
- From: Yann Droneaud <ydroneaud@xxxxxxxxxx>
- Re: using macro ...
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: using macro ...
- From: raespi <raespi@xxxxxxx>
- Re: using macro ...
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: using macro ...
- From: raespi <raespi@xxxxxxx>
- Re: using macro ...
- From: Eric Blake <eblake@xxxxxxxxxx>
- using macro ...
- From: raespi <raespi@xxxxxxx>
- Re: Need for --build with --host when cross-compiling ?
- From: Jan Engelhardt <jengelh@xxxxxxx>
- Re: Malloc issue when cross-compiling with autotools
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: Malloc issue when cross-compiling with autotools
- From: Francisco Cuesta <ndarkness@xxxxxxxxx>
- Re: Malloc issue when cross-compiling with autotools
- From: Francisco Cuesta <ndarkness@xxxxxxxxx>
- Re: Malloc issue when cross-compiling with autotools
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: Malloc issue when cross-compiling with autotools
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Malloc issue when cross-compiling with autotools
- From: Francisco Cuesta <ndarkness@xxxxxxxxx>
- Re: [PATCH] C++11 keyword fallback
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: [PATCH] C++11 keyword fallback
- From: Miles Bader <miles@xxxxxxx>
- Re: [PATCH] C++11 keyword fallback
- From: Roger Leigh <rleigh@xxxxxxxxxxxxx>
- Re: [PATCH] C++11 keyword fallback
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: [PATCH] C++11 keyword fallback
- From: Roger Leigh <rleigh@xxxxxxxxxxxxx>
- Need for --build with --host when cross-compiling ?
- From: Yann Droneaud <ydroneaud@xxxxxxxxxx>
- Uppercase in cross-compiler name
- From: Yann Droneaud <ydroneaud@xxxxxxxxxx>
- Re: [PATCH] C++11 keyword fallback
- From: Miles Bader <miles@xxxxxxx>
- [PATCH] C++11 keyword fallback
- From: Roger Leigh <rleigh@xxxxxxxxxxxxx>
- Re: Feature request: AC_PROG_CC_* macros for gnu89/gnu99-compliant compiler
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: Feature request: AC_PROG_CC_* macros for gnu89/gnu99-compliant compiler
- From: Michał Górny <mgorny@xxxxxxxxxx>
- Re: Feature request: AC_PROG_CC_* macros for gnu89/gnu99-compliant compiler
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Feature request: AC_PROG_CC_* macros for gnu89/gnu99-compliant compiler
- From: Michał Górny <mgorny@xxxxxxxxxx>
- Re: GNU autoconf configure script on cross-compiling to nearly identical target platform
- From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
- Re: GNU autoconf configure script on cross-compiling to nearly identical target platform
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- GNU autoconf configure script on cross-compiling to nearly identical target platform
- From: Wirawan Purwanto <wirawan0@xxxxxxxxx>
- Re: [patch] Extend AC_PROG_CXX to check for standards conformance
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: [patch] Extend AC_PROG_CXX to check for standards conformance
- From: Roger Leigh <rleigh@xxxxxxxxxxxxx>
- Re: Recursive AC_CONFIG_COMMANDS_PRE?
- From: Eric Blake <eblake@xxxxxxxxxx>
- Recursive AC_CONFIG_COMMANDS_PRE?
- From: Nick Bowler <nbowler@xxxxxxxxxx>
- Re: [patch] Extend AC_PROG_CXX to check for standards conformance
- From: Roger Leigh <rleigh@xxxxxxxxxxxxx>
- Re: [patch] Extend AC_PROG_CXX to check for standards conformance
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: [patch] Extend AC_PROG_CXX to check for standards conformance
- From: Miles Bader <miles@xxxxxxx>
- Re: [patch] Extend AC_PROG_CXX to check for standards conformance
- From: Roger Leigh <rleigh@xxxxxxxxxxxxx>
- Re: [patch] Extend AC_PROG_CXX to check for standards conformance
- From: Roger Leigh <rleigh@xxxxxxxxxxxxx>
- Re: [patch] Extend AC_PROG_CXX to check for standards conformance
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: [patch] Extend AC_PROG_CXX to check for standards conformance
- From: Roger Leigh <rleigh@xxxxxxxxxxxxx>
- Re: [patch] Extend AC_PROG_CXX to check for standards conformance
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- [patch] Extend AC_PROG_CXX to check for standards conformance
- From: Roger Leigh <rleigh@xxxxxxxxxxxxx>
- Re: configure mutilates -g option
- From: Dave Goodell <goodell@xxxxxxxxxxx>
- configure mutilates -g option
- From: Bruce Korb <bruce.korb@xxxxxxxxx>
- Re: [Help-smalltalk] [PATCH] build: drop useless AC_SUBST of 'INCLUDES'
- From: Paolo Bonzini <bonzini@xxxxxxx>
- Re: Selecting a C++ standard
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: Selecting a C++ standard
- From: Dave Goodell <goodell@xxxxxxxxxxx>
- Re: Selecting a C++ standard
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: Selecting a C++ standard
- From: Roger Leigh <rleigh@xxxxxxxxxxxxx>
- Re: Blogging about deprecated macros
- From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
- Re: Blogging about deprecated macros
- From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
- Re: Blogging about deprecated macros
- From: Marko Lindqvist <cazfi74@xxxxxxxxx>
- Re: Blogging about deprecated macros
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Blogging about deprecated macros
- From: Marko Lindqvist <cazfi74@xxxxxxxxx>
- /usr/bin/gcc -std=gnu99 -o conftest -g gdb3 conftest.c
- From: Bruce Korb <bruce.korb@xxxxxxxxx>
- Re: Conditional AC_DEFINE with m4_define variable?
- From: Jef Driesen <jefdriesen@xxxxxxxxxxx>
- Re: Conditional AC_DEFINE with m4_define variable?
- From: Jef Driesen <jefdriesen@xxxxxxxxxxx>
- Re: Conditional AC_DEFINE with m4_define variable?
- From: Jef Driesen <jefdriesen@xxxxxxxxxxx>
- Re: Conditional AC_DEFINE with m4_define variable?
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: Conditional AC_DEFINE with m4_define variable?
- From: Jef Driesen <jefdriesen@xxxxxxxxxxx>
- Re: Conditional AC_DEFINE with m4_define variable?
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: Autoconf Digest, Vol 104, Issue 14
- From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: Enabling compiler warning flags
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Enabling compiler warning flags
- From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
- Re: Future autoconf package compression
- From: Jim Meyering <jim@xxxxxxxxxxxx>
- Re: Future autoconf package compression
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: RE : RE : rm -f core cause some troubles
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: RE : RE : rm -f core cause some troubles
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: RE : RE : rm -f core cause some troubles
- From: NightStrike <nightstrike@xxxxxxxxx>
- Re: Future autoconf package compression
- From: Jim Meyering <jim@xxxxxxxxxxxx>
- Re: Future autoconf package compression
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: RE : RE : rm -f core cause some troubles
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: Future autoconf package compression
- From: Jim Meyering <jim@xxxxxxxxxxxx>
- Re: RE : RE : rm -f core cause some troubles
- From: Marko Lindqvist <cazfi74@xxxxxxxxx>
- Re: RE : RE : rm -f core cause some troubles
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: RE : RE : rm -f core cause some troubles
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: RE : RE : rm -f core cause some troubles
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: RE : RE : rm -f core cause some troubles
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: About dynamic configure options.
- From: Eduardo Costa <ecosta.tmp@xxxxxxxxx>
- Re: About dynamic configure options.
- From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
- Re: About dynamic configure options.
- From: Eduardo Costa <ecosta.tmp@xxxxxxxxx>
- Re: About dynamic configure options.
- From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
- Re: About dynamic configure options.
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: About dynamic configure options.
- From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
- Re: RE : RE : rm -f core cause some troubles
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: rm -f core cause some troubles
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: Future autoconf package compression
- From: Marko Lindqvist <cazfi74@xxxxxxxxx>
- Re: Future autoconf package compression
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: RE : RE : rm -f core cause some troubles
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: RE : RE : rm -f core cause some troubles
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: RE : RE : rm -f core cause some troubles
- From: Marko Lindqvist <cazfi74@xxxxxxxxx>
- Re: RE : RE : rm -f core cause some troubles
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: Future autoconf package compression
- From: Jim Meyering <jim@xxxxxxxxxxxx>
- Re: Future autoconf package compression
- From: Jim Meyering <jim@xxxxxxxxxxxx>
- Re: rm -f core cause some troubles
- From: John Hawkinson <jhawk@xxxxxxx>
- Re: rm -f core cause some troubles
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- RE : RE : rm -f core cause some troubles
- From: PICCA Frédéric-Emmanuel <frederic-emmanuel.picca@xxxxxxxxxxxxxxxxxxxxx>
- Re: RE : rm -f core cause some troubles
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- RE : rm -f core cause some troubles
- From: PICCA Frédéric-Emmanuel <frederic-emmanuel.picca@xxxxxxxxxxxxxxxxxxxxx>
- Re: rm -f core cause some troubles
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- rm -f core cause some troubles
- Re: Can packages rely on AC_PROVIDE_IFELSE?
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: RFC: autoconf opengl macro
- From: Bastien ROUCARIES <roucaries.bastien@xxxxxxxxx>
- Snakebite and Autoconf
- From: Trent Nelson <trent@xxxxxxxxxxxxx>
- Can packages rely on AC_PROVIDE_IFELSE?
- From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
- RFC: autoconf opengl macro
- From: Bastien ROUCARIES <roucaries.bastien@xxxxxxxxx>
- Re: Future autoconf package compression
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: Future autoconf package compression
- From: Marko Lindqvist <cazfi74@xxxxxxxxx>
- Re: Future autoconf package compression
- From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
- Future autoconf package compression
- From: Marko Lindqvist <cazfi74@xxxxxxxxx>
- Re: Global autoconf cache
- From: Richard Stallman <rms@xxxxxxx>
- Re: Assigning command output to a variable
- From: Adam Mercer <ramercer@xxxxxxxxx>
- Re: Assigning command output to a variable
- From: Adam Mercer <ramercer@xxxxxxxxx>
- Re: Global autoconf cache
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: Global autoconf cache
- From: Richard Stallman <rms@xxxxxxx>
- need help building and installing in non-standard place
- From: Gary Aitken <gnu@xxxxxxxxxxxxxxx>
- Re: Assigning command output to a variable
- From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
- Re: Global autoconf cache
- From: Wookey <wookey@xxxxxxxxxxxx>
- Re: Assigning command output to a variable
- From: Eric Blake <eblake@xxxxxxxxxx>
- Assigning command output to a variable
- From: Adam Mercer <ramercer@xxxxxxxxx>
- Re: Global autoconf cache
- From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx>
- [akim@xxxxxxxxxxxxx: Re: [gnu-prog-discuss] Autotools]
- From: Richard Stallman <rms@xxxxxxx>
- Re: Global autoconf cache
- From: NightStrike <nightstrike@xxxxxxxxx>
- Global autoconf cache
- From: Richard Stallman <rms@xxxxxxx>
- Re: bug#12877: Autoconf, GNU m4 and POSIXLY_CORRECT
- From: "Sebastian Freundt" <sebastian.freundt@xxxxxxxxxxx>
- Re: Autoconf, GNU m4 and POSIXLY_CORRECT
- From: Sebastian Freundt <sebastian.freundt@xxxxxxxxxxx>
- Re: bug#12877: Autoconf, GNU m4 and POSIXLY_CORRECT
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: bug#12877: Autoconf, GNU m4 and POSIXLY_CORRECT
- From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
- Re: bug#12877: Autoconf, GNU m4 and POSIXLY_CORRECT
- From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
- Autoconf, GNU m4 and POSIXLY_CORRECT (was: Re: bug#12877: automake error: unrequested trace '')
- From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
- Re: split the result of AC_ARG_WITH with a given token
- From: Eric Blake <eblake@xxxxxxxxxx>
- split the result of AC_ARG_WITH with a given token
- From: Vincent Torri <vincent.torri@xxxxxxxxx>
- Re: AC_CHECK_LIB for C++ libraries
- From: Peter Johansson <trojkan@xxxxxxxxx>
- Re: Selecting a C++ standard
- From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
- Re: Selecting a C++ standard
- From: Florian Weimer <fw@xxxxxxxxxxxxx>
- Re: Selecting a C++ standard
- From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
- Re: Selecting a C++ standard
- From: Florian Weimer <fw@xxxxxxxxxxxxx>
- Re: Passing options to libtool from within a GNU Autotools project.
- From: Robert Boehne <robertb@xxxxxxxxxx>
- Re: AC_CHECK_LIB for C++ libraries
- From: Jan Mikelson <jan.mikelson@xxxxxxxxx>
- Re: AC_CHECK_LIB for C++ libraries
- From: Peter Johansson <trojkan@xxxxxxxxx>
- Passing options to libtool from within a GNU Autotools project.
- From: Craig Sanders <craig.autotools.user@xxxxxxxxx>
- AC_CHECK_LIB for C++ libraries
- From: Jan Mikelson <jan.mikelson@xxxxxxxxx>
- Re: cross-compiling difficulties caused by running compiled programs during build
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- cross-compiling difficulties caused by running compiled programs during build
- From: George McCollister <george.mccollister@xxxxxxxxx>
- Re: Selecting a C++ standard
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: Selecting a C++ standard
- From: Trent Nelson <trent@xxxxxxxxxxxxx>
- Re: Selecting a C++ standard
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: Selecting a C++ standard
- From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
- Re: Selecting a C++ standard
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: Selecting a C++ standard
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: Selecting a C++ standard
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: Selecting a C++ standard
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: Selecting a C++ standard
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: Selecting a C++ standard
- From: Florian Weimer <fw@xxxxxxxxxxxxx>
- Re: Selecting a C++ standard
- From: "Andrew W. Nosenko" <andrew.w.nosenko@xxxxxxxxx>
- Re: Selecting a C++ standard
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: Selecting a C++ standard
- From: Florian Weimer <fw@xxxxxxxxxxxxx>
- Re: Selecting a C++ standard
- From: Roger Leigh <rleigh@xxxxxxxxxxxxx>
- Re: Selecting a C++ standard
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: Selecting a C++ standard
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: Selecting a C++ standard
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: Selecting a C++ standard
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: Selecting a C++ standard
- From: Harlan Stenn <stenn@xxxxxxx>
- Re: Selecting a C++ standard
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: Selecting a C++ standard
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: Selecting a C++ standard
- From: Harlan Stenn <stenn@xxxxxxx>
- Re: Selecting a C++ standard
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: Selecting a C++ standard
- From: Harlan Stenn <stenn@xxxxxxx>
- Re: Selecting a C++ standard
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: Selecting a C++ standard
- From: Harlan Stenn <stenn@xxxxxxx>
- Re: Selecting a C++ standard
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: Selecting a C++ standard
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: Selecting a C++ standard
- From: Roger Leigh <rleigh@xxxxxxxxxxxxx>
- Re: Selecting a C++ standard
- From: Harlan Stenn <stenn@xxxxxxx>
- Re: Selecting a C++ standard
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Selecting a C++ standard
- From: Roger Leigh <rleigh@xxxxxxxxxxxxx>
- Re: FYI: grep had to switch: AC_PROG_CC_STDC -> AC_PROG_CC
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: FYI: grep had to switch: AC_PROG_CC_STDC -> AC_PROG_CC
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: FYI: grep had to switch: AC_PROG_CC_STDC -> AC_PROG_CC
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- FYI: grep had to switch: AC_PROG_CC_STDC -> AC_PROG_CC
- From: Jim Meyering <jim@xxxxxxxxxxxx>
- Re: how to use autoconf projcet to make bin
- From: Manuel Cano <manutalcual@xxxxxxxxx>
- Re: how to use autoconf projcet to make bin
- From: Eric Blake <eblake@xxxxxxxxxx>
- how to use autoconf projcet to make bin
- From: 李裕 <liyu_www@xxxxxxx>
- Re: Question about ac_lib and ac_res
- From: Sergio Belkin <sebelk@xxxxxxxxx>
- Re: Question about ac_lib and ac_res
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: Question about ac_lib and ac_res
- From: Sergio Belkin <sebelk@xxxxxxxxx>
- Re: Question about ac_lib and ac_res
- From: Eric Blake <eblake@xxxxxxxxxx>
- Question about ac_lib and ac_res
- From: Sergio Belkin <sebelk@xxxxxxxxx>
- Re: Running a shell command
- From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
- Running a shell command
- From: Michael Talbot-Wilson <mtw@xxxxxxxxxxx>
- Re: [RFC] pass #2 at getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: [RFC] pass #2 at getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: [RFC] pass #2 at getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Roger Leigh <rleigh@xxxxxxxxxxxxx>
- Re: [Autoconf] Including and extracting jar files in Makefile.am
- From: Sujit Devkar <sujit.devkar@xxxxxxx>
- Re: Wholesale sharing of config.cache across many packages
- From: tsuna <tsunanet@xxxxxxxxx>
- Re: [Autoconf] Including and extracting jar files in Makefile.am
- From: Eric Blake <eblake@xxxxxxxxxx>
- [Autoconf] Including and extracting jar files in Makefile.am
- From: Sujit Devkar <sujit.devkar@xxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: [RFC] pass #2 at getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Eric Blake <eblake@xxxxxxxxxx>
- Wholesale sharing of config.cache across many packages
- From: tsuna <tsunanet@xxxxxxxxx>
- Re: [RFC] pass #2 at getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Paul Wise <pabs3@xxxxxxxxxxxxx>
- Re: [RFC] pass #2 at getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Ralf Corsepius <rc040203@xxxxxxxxxx>
- Re: [RFC] pass #2 at getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Paul Wise <pabs3@xxxxxxxxxxxxx>
- Re: [RFC] pass #2 at getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Eric Blake <eblake@xxxxxxxxxx>
- [RFC] pass #2 at getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Paul Wise <pabs3@xxxxxxxxxxxxx>
- [Autoconf] Including Files in configure.ac
- From: Sujit Devkar <sujit.devkar@xxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Wookey <wookey@xxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Paul Wise <pabs3@xxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Paul Wise <pabs3@xxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Paul Wise <pabs3@xxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Paul Wise <pabs3@xxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Paul Wise <pabs3@xxxxxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- [RFC] getting rid of the config.guess/sub problem when bootstrapping new ports/systems
- From: Paul Wise <pabs3@xxxxxxxxxxxxx>
- [Autoconf] Including Files in configure.ac and makefile.am
- From: Sujit Devkar <sujit.devkar@xxxxxxx>
- Fwd: [Automake] Including Dynamic libraries and java functionality in makefile.
- From: Sujit Devkar <sujit.devkar@xxxxxxx>
- Re: Add clang++ to AC_PROG_CXX
- From: Václav Zeman <vhaisman@xxxxxxxxx>
- Re: Add clang++ to AC_PROG_CXX
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Add clang++ to AC_PROG_CXX
- From: Václav Zeman <vhaisman@xxxxxxxxx>
- Re: help on configuration file creation
- From: Eric Blake <eblake@xxxxxxxxxx>
- help on configuration file creation
- From: Claudio Eterno <eterno.claudio@xxxxxxxxx>
- Dependencies to external packages
- From: "A.P. Horst" <ariehorst@xxxxxxxxx>
- Re: Python macros
- From: Brandon Invergo <brandon@xxxxxxxxxxx>
- Re: Python macros
- From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
- Re: Python macros
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Python macros
- From: Brandon Invergo <brandon@xxxxxxxxxxx>
- Re: generating pc file
- From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
- Re: generating pc file
- From: Bruce Korb <bkorb@xxxxxxx>
- Re: generating pc file
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: generating pc file
- From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
- Re: generating pc file
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: generating pc file
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: generating pc file
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: generating pc file
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: generating pc file
- From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
- Re: generating pc file
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: generating pc file
- From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
- Re: generating pc file
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: generating pc file
- From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
- Re: generating pc files
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: generating pc files
- From: Bruce Korb <bkorb@xxxxxxx>
- Re: generating pc file
- From: "David A. Wheeler" <dwheeler@xxxxxxxxxxxx>
- Re: RFE: macro for warning at configure-time if CFLAGS includes -Werror
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: RFE: macro for warning at configure-time if CFLAGS includes -Werror
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: RFE: macro for warning at configure-time if CFLAGS includes -Werror
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: RFE: macro for warning at configure-time if CFLAGS includes -Werror
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: RFE: macro for warning at configure-time if CFLAGS includes -Werror
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: RFE: macro for warning at configure-time if CFLAGS includes -Werror
- From: Marko Lindqvist <cazfi74@xxxxxxxxx>
- Re: RFE: macro for warning at configure-time if CFLAGS includes -Werror
- From: Harlan Stenn <stenn@xxxxxxx>
- Re: RFE: macro for warning at configure-time if CFLAGS includes -Werror
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: RFE: macro for warning at configure-time if CFLAGS includes -Werror
- From: Marko Lindqvist <cazfi74@xxxxxxxxx>
- Re: RFE: macro for warning at configure-time if CFLAGS includes -Werror
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: RFE: macro for warning at configure-time if CFLAGS includes -Werror
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: RFE: macro for warning at configure-time if CFLAGS includes -Werror
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: RFE: macro for warning at configure-time if CFLAGS includes -Werror
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: RFE: macro for warning at configure-time if CFLAGS includes -Werror
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Re: RFE: macro for warning at configure-time if CFLAGS includes -Werror
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: RFE: macro for warning at configure-time if CFLAGS includes -Werror
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: RFE: macro for warning at configure-time if CFLAGS includes -Werror
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: RFE: macro for warning at configure-time if CFLAGS includes -Werror
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- RFE: macro for warning at configure-time if CFLAGS includes -Werror
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: generating pc files
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: generating pc files
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: generating pc files
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: generating pc files
- From: Bastien ROUCARIES <roucaries.bastien@xxxxxxxxx>
- Re: generating pc files
- From: Peter Johansson <trojkan@xxxxxxxxx>
- Re: generating pc files
- From: Vincent Torri <vincent.torri@xxxxxxxxx>
- Re: generating pc files
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- generating pc files
- From: Vincent Torri <vtorri@xxxxxxxxxxxx>
- Re: Why conditionally include config.h?
- From: Kip Warner <kip@xxxxxxxxxxxxxx>
- Re: Why conditionally include config.h?
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: Why conditionally include config.h?
- From: Kip Warner <kip@xxxxxxxxxxxxxx>
- Re: Why conditionally include config.h?
- From: Kip Warner <kip@xxxxxxxxxxxxxx>
- Re: Why conditionally include config.h?
- From: Kip Warner <kip@xxxxxxxxxxxxxx>
- Re: Why conditionally include config.h?
- From: Kip Warner <kip@xxxxxxxxxxxxxx>
- Re: Why conditionally include config.h?
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: Why conditionally include config.h?
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: Why conditionally include config.h?
- From: Marko Lindqvist <cazfi74@xxxxxxxxx>
- Re: Why conditionally include config.h?
- From: Eric Blake <eblake@xxxxxxxxxx>
- Why conditionally include config.h?
- From: Kip Warner <kip@xxxxxxxxxxxxxx>
- Re: FCLIBS do not contain objects required for AC_FC_MAIN to succeed
- From: Thomas Jahns <jahns@xxxxxxx>
- FCLIBS do not contain objects required for AC_FC_MAIN to succeed
- From: Thomas Jahns <jahns@xxxxxxx>
- Re: how can I use the -C option of 'install' tool
- From: Peter Johansson <trojkan@xxxxxxxxx>
- Re: how can I use the -C option of 'install' tool
- From: Peter Johansson <trojkan@xxxxxxxxx>
- how can I use the -C option of 'install' tool
- From: Vincent Torri <vtorri@xxxxxxxxxxxx>
- Re: using $datadir in a file that is processed by configure
- From: Eric Blake <eblake@xxxxxxxxxx>
- using $datadir in a file that is processed by configure
- From: Vincent Torri <vtorri@xxxxxxxxxxxx>
- Re: make variable for GPL compliant builds
- From: Daniel Pocock <daniel@xxxxxxxxxxxxx>
- Re: make variable for GPL compliant builds
- From: Eric Blake <eblake@xxxxxxxxxx>
- make variable for GPL compliant builds
- From: Daniel Pocock <daniel@xxxxxxxxxxxxx>
- Re: Macros for QNX POSIX environment
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: [autoconf] Re: Macros for QNX POSIX environment
- From: suzuki toshiya <mpsuzuki@xxxxxxxxxxxxxxxxx>
- Re: Macros for QNX POSIX environment
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Macros for QNX POSIX environment
- From: suzuki toshiya <mpsuzuki@xxxxxxxxxxxxxxxxx>
- Re: AC_HEADER_STDBOOL: checking for _Bool separately for C and C++
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: AC_HEADER_STDBOOL: checking for _Bool separately for C and C++
- From: Mojca Miklavec <mojca.miklavec.lists@xxxxxxxxx>
- Re: AC_HEADER_STDBOOL: checking for _Bool separately for C and C++
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: AC_HEADER_STDBOOL: checking for _Bool separately for C and C++
- From: Mojca Miklavec <mojca.miklavec.lists@xxxxxxxxx>
- Re: AC_HEADER_STDBOOL: checking for _Bool separately for C and C++
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: AC_HEADER_STDBOOL: checking for _Bool separately for C and C++
- From: Mojca Miklavec <mojca.miklavec.lists@xxxxxxxxx>
- AC_HEADER_STDBOOL: checking for _Bool separately for C and C++
- From: Mojca Miklavec <mojca.miklavec.lists@xxxxxxxxx>
- Re: [PATCH] {master} AM_INIT_AUTOMAKE: allow obsolescent two-args invocation once again
- From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
- [PATCH] {master} AM_INIT_AUTOMAKE: allow obsolescent two-args invocation once again (was: Re: Dynamic package version numbers with Autoconf and Automake)
- From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
- Re: Problems Configuring (C Compiler cannot produce executables)
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: Add more check in autoreconf
- From: Javier Jardón <jjardon@xxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: Problems Configuring (C Compiler cannot produce executables)
- From: Ralf Corsepius <rc040203@xxxxxxxxxx>
- Re: [autoconf] Re: Problems Configuring (C Compiler cannot produce executables)
- From: suzuki toshiya <mpsuzuki@xxxxxxxxxxxxxxxxx>
- Re: Problems Configuring (C Compiler cannot produce executables)
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: Problems Configuring (C Compiler cannot produce executables)
- From: Miles Bader <miles@xxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: suzuki toshiya <mpsuzuki@xxxxxxxxxxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Russ Allbery <rra@xxxxxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Mike Frysinger <vapier@xxxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: suzuki toshiya <mpsuzuki@xxxxxxxxxxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: [autoconf] Problems Configuring (C Compiler cannot produce executables)
- From: suzuki toshiya <mpsuzuki@xxxxxxxxxxxxxxxxx>
- Problems Configuring (C Compiler cannot produce executables)
- From: Jeffrey Walton <noloader@xxxxxxxxx>
- Re: Automake, Autoconf and POSIX shells (was: Re: GraphicsMagick Automake TAP)
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Automake, Autoconf and POSIX shells (was: Re: GraphicsMagick Automake TAP)
- From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
- Re: Add more check in autoreconf
- From: Javier Jardón <jjardon@xxxxxxxxx>
- Re: Add more check in autoreconf
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: Add more check in autoreconf
- From: Peter Rosin <peda@xxxxxxxxxxxxxx>
- Re: Add more check in autoreconf
- From: Eric Blake <eblake@xxxxxxxxxx>
- Add more check in autoreconf
- From: Javier Jardón <jjardon@xxxxxxxxx>
- Re: Dynamic package version numbers with Autoconf and Automake
- From: Robert Boehne <robertb@xxxxxxxxxx>
- Re: Dynamic package version numbers with Autoconf and Automake
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: Dynamic package version numbers with Autoconf and Automake (was: Re: Automake 1.12.0b test release)
- From: Roger Leigh <rleigh@xxxxxxxxxxxxx>
- Re: Dynamic package version numbers with Autoconf and Automake
- From: Miles Bader <miles@xxxxxxx>
- Re: Dynamic package version numbers with Autoconf and Automake (was: Re: Automake 1.12.0b test release)
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Re: Dynamic package version numbers with Autoconf and Automake (was: Re: Automake 1.12.0b test release)
- From: Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx>
- Dynamic package version numbers with Autoconf and Automake (was: Re: Automake 1.12.0b test release)
- From: Stefano Lattarini <stefano.lattarini@xxxxxxxxx>
- Re: Build directory option for configure script
- From: Ben Pfaff <blp@xxxxxxxxxxxxxxx>
- Re: Build directory option for configure script
- From: karl@xxxxxxxxxxxxxxx (Karl Berry)
- Re: Build directory option for configure script
- From: Daniel J Sebald <daniel.sebald@xxxxxxxx>
- Re: Build directory option for configure script
- From: Daniel J Sebald <daniel.sebald@xxxxxxxx>
- Re: Build directory option for configure script
- From: Eric Blake <eblake@xxxxxxxxxx>
- Re: Build directory option for configure script
- From: Daniel J Sebald <daniel.sebald@xxxxxxxx>
- Re: Build directory option for configure script
- From: Eric Blake <eblake@xxxxxxxxxx>
- Build directory option for configure script
- From: Daniel J Sebald <daniel.sebald@xxxxxxxx>
- Re: What is the right way to specify -Wno-format-contains-nul?
- From: Bruce Korb <bruce.korb@xxxxxxxxx>
- Re: Intended behavior if "--build" and "--host" are set to the same value
- From: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
- Intended behavior if "--build" and "--host" are set to the same value
- From: Sven Joachim <svenjoac@xxxxxx>
- Re: test if compiler warns
- From: Peter Lee <peter.lee.cpp@xxxxxxxxx>
- Re: test if compiler warns
- From: Peter Johansson <trojkan@xxxxxxxxx>
- test if compiler warns
- From: Peter Johansson <trojkan@xxxxxxxxx>
- Re: configuring with non-standard location of gcc
- From: Paul Eggert <eggert@xxxxxxxxxxx>
- Re: configuring with non-standard location of gcc
- From: Eric Blake <eblake@xxxxxxxxxx>
- configuring with non-standard location of gcc
- From: Maynard Johnson <maynardj@xxxxxxxxxx>
- Cross Compilation for Intel MIC
- From: Jonathan Perkins <perkinjo@xxxxxxxxxxxxxxxxxx>
- Re: m4_foreach_w vs m4_foreach
- From: Vincent Torri <vtorri@xxxxxxxxxxxx>
- Re: m4_foreach_w vs m4_foreach
- From: Eric Blake <eblake@xxxxxxxxxx>
- m4_foreach_w vs m4_foreach
- From: Vincent Torri <vtorri@xxxxxxxxxxxx>
[GCC Help]
[Security]
[Netfilter]
[Video 4 Linux]
[Bugtraq]
[Linux Crypto]
