On 5 May 2005 at 22:43, Chris Lawrence wrote:
| On 5/5/05, Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote:
| >
| > On 5 May 2005 at 22:46, Kurt Roeckx wrote:
| > | On Thu, May 05, 2005 at 03:25:42PM -0500, Chris Lawrence wrote:
| > | > 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.
| > |
| > | It says:
| > | ## Use configure values
| > | AWK=${AWK-'gawk'}
| > |
| > | While on i386 it says:
| > | ## Use configure values
| > | AWK=${AWK-'mawk'}
| >
| > As I said in the previous mail, this is determined during built-time of
__R__
| > itself:
| >
| > [EMAIL PROTECTED]:~> grep AWK src/debian/R/R-2.1.0/etc/Renviron.in
| > AWK=${AWK-'@AWK@'}
| > [EMAIL PROTECTED]:~>
| >
| > Now, would we need gawk everywhere? Then I'll add it for 2.1.0-2. Do we
need
| > that soon?
| >
| > Or could the amd64 crowd enforce that locally /for now/ and I will have it
| > enforce globally by the next upload of R ?
|
| Well, ideally we should get the amd64 port to build with AWK=mawk
Agreed -- any idea why they differ from the default? I see mawk as Priority:
required whereas gawk is merely Optional.
Maybe that one wasn't built in a chroot but live on a box with gawk?
| (there's no reason to use gawk). Is there a configure option in R to
| specify which awk is used? Build-Conflicts: gawk would work too, but
| it might be a little heavy-handed.
Presumably I could specify it in the call to configure, but that should
amount to the same as calling for it in the Build-Depends.
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]
