info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Build report for gawk 4.1.4 in the WIn10 WSL environment
91 views
Skip to first unread message
pjfarley3
May 1, 2017, 11:08:23 PM5/1/17
to
Hi All,
Just a short build report for gawk 4.1.4 using the Win10 Windows Subsystem for Linux (WSL) environment, which is (for the moment) actually Ubuntu 14.04 command line environment only (no X system, no graphical support).
After all the regular tool chain packages were installed, the configure and make ran without any errors. The make check reported only 3 errors, all to do with the readdir extension. There were no OK files for the dirlist and longlist tests, so they failed. The readdir test failed on a difference at byte 23.
All other tests passed.
A log of the check run is available if anyone wishes to see it.
I plan to test again once the Win10 "Creators" update hits my environment, when Ubuntu 16.04 will be available under WSL, with the goal of also building the gawk extensions package.
HTH
Peter
Just a short build report for gawk 4.1.4 using the Win10 Windows Subsystem for Linux (WSL) environment, which is (for the moment) actually Ubuntu 14.04 command line environment only (no X system, no graphical support).
After all the regular tool chain packages were installed, the configure and make ran without any errors. The make check reported only 3 errors, all to do with the readdir extension. There were no OK files for the dirlist and longlist tests, so they failed. The readdir test failed on a difference at byte 23.
All other tests passed.
A log of the check run is available if anyone wishes to see it.
I plan to test again once the Win10 "Creators" update hits my environment, when Ubuntu 16.04 will be available under WSL, with the goal of also building the gawk extensions package.
HTH
Peter
Kenny McCormack
May 1, 2017, 11:20:07 PM5/1/17
to
In article <a4888cb9-d16b-4110...@googlegroups.com>,
--
Rich people pay Fox people to convince middle class people to blame poor people.
(John Fugelsang)
pjfarley3 <pjfa...@yahoo.com> wrote:
>Hi All,
>
>Just a short build report for gawk 4.1.4 using the Win10 Windows
>Subsystem for Linux (WSL) environment, which is (for the moment)
>actually Ubuntu 14.04 command line environment only (no X system, no
>graphical support).
>
>After all the regular tool chain packages were installed, the configure
>and make ran without any errors. The make check reported only 3 errors,
>all to do with the readdir extension. There were no OK files for the
>dirlist and longlist tests, so they failed. The readdir test failed on
>a difference at byte 23.
Why not just use Cygwin?
>Hi All,
>
>Just a short build report for gawk 4.1.4 using the Win10 Windows
>Subsystem for Linux (WSL) environment, which is (for the moment)
>actually Ubuntu 14.04 command line environment only (no X system, no
>graphical support).
>
>After all the regular tool chain packages were installed, the configure
>and make ran without any errors. The make check reported only 3 errors,
>all to do with the readdir extension. There were no OK files for the
>dirlist and longlist tests, so they failed. The readdir test failed on
>a difference at byte 23.
--
Rich people pay Fox people to convince middle class people to blame poor people.
(John Fugelsang)
Kaz Kylheku
May 2, 2017, 12:46:30 AM5/2/17
to
On 2017-05-02, Kenny McCormack <gaz...@shell.xmission.com> wrote:
> In article <a4888cb9-d16b-4110...@googlegroups.com>,
> pjfarley3 <pjfa...@yahoo.com> wrote:
>>Hi All,
>>
>>Just a short build report for gawk 4.1.4 using the Win10 Windows
>>Subsystem for Linux (WSL) environment, which is (for the moment)
>>actually Ubuntu 14.04 command line environment only (no X system, no
>>graphical support).
>>
>>After all the regular tool chain packages were installed, the configure
>>and make ran without any errors. The make check reported only 3 errors,
>>all to do with the readdir extension. There were no OK files for the
>>dirlist and longlist tests, so they failed. The readdir test failed on
>>a difference at byte 23.
>
> Why not just use Cygwin?
Probably because successful Gawk build reports are a dime a dozen on
> In article <a4888cb9-d16b-4110...@googlegroups.com>,
> pjfarley3 <pjfa...@yahoo.com> wrote:
>>Hi All,
>>
>>Just a short build report for gawk 4.1.4 using the Win10 Windows
>>Subsystem for Linux (WSL) environment, which is (for the moment)
>>actually Ubuntu 14.04 command line environment only (no X system, no
>>graphical support).
>>
>>After all the regular tool chain packages were installed, the configure
>>and make ran without any errors. The make check reported only 3 errors,
>>all to do with the readdir extension. There were no OK files for the
>>dirlist and longlist tests, so they failed. The readdir test failed on
>>a difference at byte 23.
>
> Why not just use Cygwin?
Cygwin; where is the fun in that?
pjfarley3
May 2, 2017, 1:48:02 AM5/2/17
to
On Monday, May 1, 2017 at 11:20:07 PM UTC-4, Kenny McCormack wrote:
> In article <a4888cb9-d16b-4110...@googlegroups.com>,
> pjfarley3 wrote:
> In article <a4888cb9-d16b-4110...@googlegroups.com>,
> >Hi All,
<Build Report Snipped>
> Why not just use Cygwin?
Pure curiosity, actually. With an eye to experimenting to see if it may or may not be a usable command-line utility/tools environment when I may need it.
Also, just fun to try out. So far so good.
Peter
Marc de Bourget
May 4, 2017, 5:40:10 PM5/4/17
to
BTW, it is only available for Windows 10 64 bit (not for 32 bit).
I'm not shure if I have understood:
Has your 4.1.4 GAWK compilation been successful or not successful?
gawk -V shows in my "Microsoft" bash: GNU AWK 4.0.1
When will the bash been updated with GAWK version 4.1.4 and who does it?
Does someone should inform Microsoft that a new GAWK version is available?
pjfarley3
May 6, 2017, 1:46:28 AM5/6/17
to
On Thursday, May 4, 2017 at 5:40:10 PM UTC-4, Marc de Bourget wrote:
<Snipped>
So yes, the build was successful and I now have Gawk v4.1.4 running in my Win10 bash setup.
To build Gawk yourself you also first have to apt-get install all the packages needed to configure, make and install it. At a minimum, gcc, autotools, bison, and make are needed. I also installed the MPFR and readline libraries and their *-dev packages so that Gawk would build with those features too. Also gettext, which may have been installed by default, I do not remember for sure.
When the Win10 "Creators" update is finally stable and is released to our machines for update, the new bash environment will be upgraded to Ubuntu v16.04, which if I am reading the Ubuntu package lists correctly includes Gawk v4.1.3 by default. We will still have to build and install our own copy of Gawk v4.1.4 if we want it.
From what I have read online, if you already have a bash environment installed when the "Creators" update is eventually done, it will NOT automatically update the bash component. We will have to manually uninstall (using the lxrun command) and reinstall it to get the new Ubuntu version.
HTH
Peter
<Snipped>
> Hi Peter, I have also installed bash for the Windows command line now.
> BTW, it is only available for Windows 10 64 bit (not for 32 bit).
> I'm not shure if I have understood:
> Has your 4.1.4 GAWK compilation been successful or not successful?
> gawk -V shows in my "Microsoft" bash: GNU AWK 4.0.1
> When will the bash been updated with GAWK version 4.1.4 and who does it?
> Does someone should inform Microsoft that a new GAWK version is available?
As of today, the Win10-64 bash environment is Ubuntu v14.04, which only has Gawk V4.0.1 available to install with apt-get. That version of Gawk is installed by default. I downloaded the Gawk v4.1.4 tarball from the Gnu ftp site and built it myself in the Win10 bash environment, so now I have Gawk v4.1.4 in my Win10 bash setup, installed in /usr/local/bin.
> BTW, it is only available for Windows 10 64 bit (not for 32 bit).
> I'm not shure if I have understood:
> Has your 4.1.4 GAWK compilation been successful or not successful?
> gawk -V shows in my "Microsoft" bash: GNU AWK 4.0.1
> When will the bash been updated with GAWK version 4.1.4 and who does it?
> Does someone should inform Microsoft that a new GAWK version is available?
So yes, the build was successful and I now have Gawk v4.1.4 running in my Win10 bash setup.
To build Gawk yourself you also first have to apt-get install all the packages needed to configure, make and install it. At a minimum, gcc, autotools, bison, and make are needed. I also installed the MPFR and readline libraries and their *-dev packages so that Gawk would build with those features too. Also gettext, which may have been installed by default, I do not remember for sure.
When the Win10 "Creators" update is finally stable and is released to our machines for update, the new bash environment will be upgraded to Ubuntu v16.04, which if I am reading the Ubuntu package lists correctly includes Gawk v4.1.3 by default. We will still have to build and install our own copy of Gawk v4.1.4 if we want it.
From what I have read online, if you already have a bash environment installed when the "Creators" update is eventually done, it will NOT automatically update the bash component. We will have to manually uninstall (using the lxrun command) and reinstall it to get the new Ubuntu version.
HTH
Peter
Marc de Bourget
May 6, 2017, 3:45:08 PM5/6/17
to
0 new messages