Re: [Cgdb-users] configure problems
Brought to you by:
bobbybrasko,
crouchingturbo
From: Bob R. <bob...@co...> - 2003-04-20 18:14:23
|
On Sun, Apr 20, 2003 at 11:24:55AM -0600, Tim. wrote: > > I did update the version of automake since version 0.2.1. > > I have not seen the error you are getting yet.=20 > > Could you please send your OS 'uname -a' and your version of sed. > >=20 > > I am guessing you are on a Mac, is this true ? >=20 > No I'm on an intel linux machine. >=20 > uname -a: > Linux SpaceDolphin 2.4.20 #2 Thu Mar 27 20:36:05 MST 2003 i686 unknown >=20 > automake --version: > automake (GNU automake) 1.7.3 >=20 > autoconf --version: > autoconf (GNU Autoconf) 2.57 >=20 > sed --version > GNU sed version 3.02 >=20 > uh oh... I know it's not your guys's fault for sure. I just tried updati= ng my sed to the latest version and I got the same problems with its config= ure script too. >=20 > I compiled sed on a different machine, and copied the binary over so now = I'm at 4.0.7, however the problem still exists. >=20 > It must be with my automake/autoconf. I too upgraded them recently. It'= s a very odd problem because quite a few other configure scripts from other= programs work fine. >=20 > Anyway I will have to track this down. =20 >=20 > Thanks. >=20 I don't think it is a sed problem. Since I have the same version. I use linux 2.4.18 automake 1.7 autoconf 2.57 sed 3.02 This link is from automake's mailing list. It describes the problem you are seeing. http://sources.redhat.com/ml/automake/2001-10/msg00066.html I am pretty sure it is from upgrading from automake 1.4 to automake 1.5 or greater. I don't know why it works for me and not you. Let me know if you solve the problem and I'll continue looking into it. Bob Rossi |