autoconf choking on paths containing comma

2002-04-27 Thread Sascha Silbe
Hi! I first tried it on the openssh ml, but they told me it'd rather look like a bug in autoconf, so here I am. This is my problem: If I leave the openssh 3.1p1 sources untouched, it works fine with paths containing a comma (,). But after just running autoconf (without touching anything else

Re: autoconf choking on paths containing comma

2002-04-27 Thread Sascha Silbe
On Sat, Apr 27, 2002 at 11:35:22AM +0200, Sascha Silbe [a] wrote: Forgot to mention that: I'm using autoconf 2.53 (the one that's in Debian woody). CU/Lnx Sascha Registered Linux User #77587 (http://counter.li.org/) msg07325/pgp0.pgp Description: PGP signature

Re: autoconf choking on paths containing comma

2002-04-27 Thread Earnie Boyd
Sascha Silbe wrote: > > Hi! > > I first tried it on the openssh ml, but they told me it'd rather look like a > bug in autoconf, so here I am. > The autoconf team chose to use a comma `,' character in the sed command because they reasoned that most persons wouldn't have path names with commas.

Different versions of autoconf cause problems here...

2002-04-27 Thread Andreas Bauer
Dear list, hopefully I'm not asking a FAQ, but even after a lot of googling and manual reading I did not find a definite answer to this: what is to do if envoking the configure script produces errors such as: autoheader: missing template: ENABLE_NLS autoheader: missing template: HAVE_CATGETS

Re: autoconf choking on paths containing comma

2002-04-27 Thread Sascha Silbe
On Sat, Apr 27, 2002 at 11:56:54AM -0400, Earnie Boyd [EB] wrote: EB> The autoconf team chose to use a comma `,' character in the sed command because they reasoned that most persons wouldn't have path names with commas. Most, but not all. EB> Yes it is. Change your path names. That's a very

Re: autoconf choking on paths containing comma

2002-04-27 Thread Earnie Boyd
Sascha Silbe wrote: > > EB> Yes it is. Change your path names. > That's a very narrow attitude. "If autoconf does not work for you, your environment >is broken". I'm glad not everyone thinks this way. > The solution is as simple as obvious and used everywhere else: Quote data if it >could con

(no subject)

2002-04-27 Thread Nobody
Subject: 2020Ŭ·´ÀÇ ½ÅÈ­... 2±â¿¡¼­µµ À̾îÁø´Ù...ÇöÀç ¸ðÁýÁß..[±¤°í] Return-Path: From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> X-Mailer: DreamMailingList Content-Type:text/html;charset=euc-kr 2020Ŭ·´