[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-gawk] About AWKLIBPATH
From: |
Andrew J. Schorr |
Subject: |
Re: [bug-gawk] About AWKLIBPATH |
Date: |
Wed, 7 Feb 2018 13:48:26 -0500 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Hi Hermann,
On Wed, Feb 07, 2018 at 07:25:43PM +0100, Hermann Peifer wrote:
> Here a loosely related question: Do I see this right that gawk installs
> its extensions like intdiv, etc. into PREFIX/lib/gawk-extensions whereas
> gawkextlib's XML extension is installed into PREFIX/lib/gawk. Is this
> how it should be? I am building from git, in both cases.
You should be able to see the default value of AWKLIBPATH compiled into
gawk like so:
unset AWKLIBPATH
gawk 'BEGIN {print ENVIRON["AWKLIBPATH"]}'
On my system, the installed gawk shows this:
bash-4.2$ gawk 'BEGIN {print ENVIRON["AWKLIBPATH"]}'
/usr/lib64/gawk
And that's where I find both the bundled gawk extensions and
the gawkextlib extensions:
bash-4.2$ ls /usr/lib64/gawk/
errno.so fork.so mpfr.so readdir.so revtwoway.so testext.so
filefuncs.so inplace.so ordchr.so readfile.so rwarray.so time.so
fnmatch.so lmdb.so pgsql.so revoutput.so select.so xml.so
But oy, I just built and installed gawk-4.2-stable, and you are right:
the extensions are now going in PREFIX/lib/gawk-extensions.
This is broken. It does not match the AWKLIBPATH compiled into gawk.
I am cc'ing address@hidden
Regards,
Andy
- Re: [bug-gawk] About AWKLIBPATH,
Andrew J. Schorr <=