Re: sed portability

2005-01-03 Thread Paul Eggert
Ralf Wildenhues <[EMAIL PROTECTED]> writes: > | @example > | sed -e @var{instruction-1} \ > | -e @var{instruction-2} > | @end example > > is not equivalent to > > | @example > | sed @var{instruction-1};@var{instruction-2} > | @end example > > everywhere. Thanks for reporting that. I installe

Re: Last configure args

2005-01-03 Thread Ralf Wildenhues
* Bob Friesenhahn wrote on Sun, Jan 02, 2005 at 11:17:37PM CET: > > Use > > ./config.status --version > > to see the options used. At one time in the life of config.status it > was possible to simply paste the complete line output by config.status > --version but then someone decided to make

Re: question regarding AC_CHECK_LIB

2005-01-03 Thread Sander Niemeijer
2.Morever by default AC_CHECK_LIB looks for dynamic libraries.How do I specify that I should look for a static library. AC_CHECK_LIB looks for both static and dynamic libraries. If you wish to find only static libraries, you could determine the compiler flag(s) that do what `-static' does for g

Re: AC_PROG_SED selecting correct sed for config.status

2005-01-03 Thread Stepan Kasal
Hello, On Sat, Jan 01, 2005 at 12:16:08AM -0800, Paul Eggert wrote: > Stepan Kasal <[EMAIL PROTECTED]> writes: > > > If /usr/xpg4/bin is available, insert it to the path at the beginning > > of the configure script, in order to get working sed and awk. > > I'd rather avoid this if possible, as s

Re: configure-generated *.in's

2005-01-03 Thread Stepan Kasal
Hi, On Fri, Dec 31, 2004 at 03:09:21PM -0800, J.T. Conklin wrote: > While AC_CONFIG_PKGCONFIG_IN() is very appealing, writing a script > that takes similar arguments and generates a *.pc.in file that can if understand your situation correctly, you can still use AC_CONFIG_PKGCONFIG_IN to get the *