Hi Guys, Coming into this late ... and not having read the full story on the bug I'd say that ...
On 5 May 2005 at 15:25, Chris Lawrence wrote: | On 5/5/05, Kurt Roeckx <[EMAIL PROTECTED]> wrote: | > On Thu, May 05, 2005 at 09:08:12PM +0200, Kurt Roeckx wrote: | > > It seems the environment variable AWK is set somewhere to gawk, I | > > just have no idea where. ... this happens at built time with configure. Just about everything does as Kurt Hornik is an autoconf wizard. Double-checking ... [EMAIL PROTECTED]:~> grep AWK src/debian/R/R-2.1.0/configure.ac AC_PROG_AWK [EMAIL PROTECTED]:~> Yup, looks like the GNU defaults. Now, in debian/control [EMAIL PROTECTED]:~> grep awk src/debian/R/R-2.1.0/debian/control [EMAIL PROTECTED]:~> I never specified this even though a /ton/ of other programs are requested as it was/is my understanding that one of these is build-essential. And aren't they plug-and-play compatible? Or does r-cran-maps require mawk and not gawk? | > I'm seeing this only in my amd64 chroot it seems. When I try the | > same in my i386 chroot, it uses mawk. All the buildd logs also | > use mawk, and I have no idea why it's different on amd64. | | Could be something in how r-base is built on amd64... Dirk, any ideas? | I think it has something to do with /usr/lib/R/etc/Renviron. | | > Please feel free to lower the severity of this bug. | | I'd rather see it fixed for sarge ;-) I could enforce it via build-depends, but so could r-cran-maps. Does this help? Dirk -- An economist is an expert who will know tomorrow why the things he predicted yesterday didn't happen today. -- Laurence J. Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
