Bug 41428
| Summary: | autoconf213 requires nawk | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | David Brinegar <david.brinegar> |
| Component: | Individual Port(s) | Assignee: | Alan Eldridge <alane> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
Responsible Changed From-To: freebsd-ports->ade Over to maintainer Since /usr/bin/nawk is part of the base system, I have a little problem
following the logic here.
At least on my -stable system of today, awk and nawk are very different
things:
MD5 (/usr/bin/awk) = 8d5625e506ae0f1ee91a48cf90d30011
MD5 (/usr/bin/nawk) = 001104dd6941e31c5efc5c25e34d0bd5
So I do not feel the blanket change is appropriate.
If you can convince me a little more, then perhaps we can talk further :)
-aDe
State Changed From-To: open->feedback Asked for further information from submitter. Hmm, nawk isn't part of my base system and seems to still live in
the ports tree:
> which nawk
nawk: Command not found.
> whereis nawk
nawk: /usr/ports/lang/nawk
This base system was updated from the 4.6 CD, while ports are cvsup'd
regularly.
So I looked more closely at how the autoconf213 port decides to use
nawk, and it used awk this time. Maybe I previously picked up a
package built for a newer base system which has nawk. Anyway, the
current port seems to be fine -- it will pick awk if you don't have
nawk or gawk etc. I can't find the current package but the package
at ftp.freebsd.org uses awk so is also fine.
The only odd thing is that configure usually goes through all the
awks each time, but autoconf213 sticks you with the one it liked
when it was built, used to beautify the configure.log. So if that
awk is one from the ports then backing out that awk port breaks
autoconf213 without a dependency violation in the ports tree. Seems
like a situation where the port configuration should impact the
port dependencies, or autoconf213 configuration should be made less
aggressive in picking awks from ports. If you for example have
lang/gawk installed, then autoconf213 will be configured to require
it in the autoconf213 script.
Anyway, the immediate problem was solved by deinstalling the
incompatible package and installing from the port.
- David
On Thu, Aug 08, 2002 at 07:57:49PM -0500, Ade Lovett wrote:
> Since /usr/bin/nawk is part of the base system, I have a little problem
> following the logic here.
>
> At least on my -stable system of today, awk and nawk are very different
> things:
>
> MD5 (/usr/bin/awk) = 8d5625e506ae0f1ee91a48cf90d30011
> MD5 (/usr/bin/nawk) = 001104dd6941e31c5efc5c25e34d0bd5
>
> So I do not feel the blanket change is appropriate.
>
> If you can convince me a little more, then perhaps we can talk further :)
>
> -aDe
Responsible Changed From-To: ade->freebsd-ports Ade resigned. Responsible Changed From-To: ade->freebsd-ports Ade resigned. Responsible Changed From-To: ade->freebsd-ports Ade resigned. Responsible Changed From-To: ade->freebsd-ports Ade resigned. Responsible Changed From-To: freebsd-ports->alane I'll take it. State Changed From-To: feedback->closed /usr/bin/nawk is indeed part of the base system, so this PR is no longer relevant. |
Latest /usr/ports/devel/autoconf213 creates a script that requires nawk. Line 40: : ${AWK=nawk} then line 151: # Put the real line numbers into configure to make config.log more helpful. $AWK ' /__oline__/ { printf "%d:", NR + 1 } { print } ' $tmpout | sed ' /__oline__/s/^\([0-9][0-9]*\):\(.*\)__oline__/\2\1/ ' >&4 Fix: Patch to use "awk" instead of "nawk" looks to me like it would work. How-To-Repeat: Ditch nawk and try to configure, say, mail/mutt. You should observe "nawk not found" and not be able to proceed because the configure script is empty.