Date: Wed, 28 Nov 2001 09:02:00 -0800 From: "David O'Brien" <obrien@FreeBSD.org> To: Maxim Sobolev <sobomax@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports/shells/bash2 Makefile Message-ID: <20011128090200.C21712@dragon.nuxi.com> In-Reply-To: <3C04B25E.D048360A@FreeBSD.org>; from sobomax@FreeBSD.org on Wed, Nov 28, 2001 at 11:46:06AM %2B0200 References: <200111231540.fANFeQj83655@freefall.freebsd.org> <20011127183127.A18572@dragon.nuxi.com> <3C04B25E.D048360A@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 28, 2001 at 11:46:06AM +0200, Maxim Sobolev wrote: > > > Override CONFIGURE_TARGET, so that this configure script generated by > > > autoconf-2.52 doesn't generate a warning. > > > > Uh, why didn't you report this to me (as maintainer??). > > I am going to back this out as the port should not be running autoconf at > > all. If it is, then that needs to be fixed. `configure', but not > > `configure.in' is patched. > > Have you looked at the diff? I did not switch to autoconf or something > else similar. What I really did, was addition of single line > (CONFIGURE_TARGET=blabla). Yes I did. I had just gotten a bug report from someone saying that the bash2 port was trying to autoconf during the building phase. From your commit message, I thought you were seeing this also. I cannot yet preproduce it. > Perhaps I poorly expressed myself, but I > meant that configure script buindled with bash2 was generated (by bash > developers) using autoconf-2.52, and due to that it requires different > semantics of CONFIGURE_TARGET. Ah, now I follow you. I wonder why the committer that did the upgrade (with my knowlege) did not have a problem building it w/o your change. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011128090200.C21712>