Hi,
Issue: AdoptOpenJDK build process makes bash calls in a particular way.
An abbreviated (shorter pathnames) example is:
```
bash-5.0$ /usr/bin/printf "Building targets 'product-images
legacy-jre-image test-image' in configuration
'aix-ppc64-normal-server-release'\n" > >(/usr/bin/tee -a
/
On 11/03/2021 22:27, Chet Ramey wrote:
On 3/11/21 3:55 PM, Michael Felt (aixtools) wrote:
Sent from my iPhone
On 11 Mar 2021, at 18:15, Chet Ramey wrote:
On 3/11/21 11:28 AM, Michael Felt wrote:
Hi,
Issue: AdoptOpenJDK build process makes bash calls in a particular
way. An
On 16/03/2021 14:38, Chet Ramey wrote:
On 3/16/21 8:04 AM, Michael Felt wrote:
Decided to give bash-5.1 a try. I doubt it is major, but I get as far
as:
"../../../src/bash-5.1.0/lib/sh/tmpfile.c", line 289.11: 1506-068 (W)
Operation between types "char*" and "int&q
On 16/03/2021 16:21, Chet Ramey wrote:
On 3/16/21 11:07 AM, Michael Felt wrote:
On 16/03/2021 14:38, Chet Ramey wrote:
On 3/16/21 8:04 AM, Michael Felt wrote:
Decided to give bash-5.1 a try. I doubt it is major, but I get as
far as:
"../../../src/bash-5.1.0/lib/sh/tmpfile.c", l
On 11/03/2021 18:11, Chet Ramey wrote:
On 3/11/21 11:28 AM, Michael Felt wrote:
Hi,
Issue: AdoptOpenJDK build process makes bash calls in a particular
way. An abbreviated (shorter pathnames) example is:
```
bash-5.0$ /usr/bin/printf "Building targets 'product-images
legacy-jre-
(pathname);
if (fd < 0)
{
/* Two separate strings for ease of translation. */
On 17/03/2021 16:17, Michael Felt wrote:
On 11/03/2021 18:11, Chet Ramey wrote:
On 3/11/21 11:28 AM, Michael Felt wrote:
Hi,
Issue: AdoptOpenJDK build process makes bash calls in a particular
way.
27;returns' - it ends via sh_exit() and the end of the routine.
Next time - I'll save all of my debug changes. Got a bit too rigorous
when I cleaned up.
On 17/03/2021 19:03, Chet Ramey wrote:
On 3/17/21 11:52 AM, Michael Felt wrote:
OK - this process on github has not gone exactly as
On 17/03/2021 23:12, Chet Ramey wrote:
On 3/17/21 3:29 PM, Michael Felt wrote:
I tried as many combinations of commands as I could - and it seems
that the regular behavior of dup2 on the opened fifo is enough to
maintain communication.
It's not, since FIFOs exist in the file system and
Scraping through this - thanks for the lessons aka explanations.
On 18/03/2021 16:08, Chet Ramey wrote:
On 3/18/21 5:53 AM, Michael Felt wrote:
Yes, something to test. Thx. The ojdk scenario is: /usr/bin/printf >
>(tee -a stdout.log) 2> >(tee -a stderr.log).
So, yes, in thi
I can down the distribution, e.g.
ftp://ftp.gnu.org/gnu/bash/bash-4.4.18.tar.gz, unpack it, goto base
directory and run configure.
Thought I had reported this earlier, but guess not!
If after a successful build, I run "make distclean" - "./configure &&
make" no longer works.
e.g.:
root@x0
I'll start all over again - using the following structure:
cd dist; wget distro..tar.gz
cd ../src; gzip -dc ../dist/distro.tar.gz | tar xf -
mkdir ../distro; cd ../distro
../src/distro/configure --arguments; make; make distclean
../src/distro/configure --arguments; make
As I have not been bu
Hi,
I finally got around to patching and packaging bash-4.4.23 and had to
run a "make distclean" because I had copied the old version and without
the make distclean make kept looking for "bashversion" in the old path
.../bash-4.4.19/bashversion
This is just FYI - I'll install yacc, which is what
On 10/31/2018 9:03 PM, Michael Felt wrote:
> Hi,
>
> I finally got around to patching and packaging bash-4.4.23 and had to
> run a "make distclean" because I had copied the old version and without
> the make distclean make kept looking for "bashversion"
> On 10/31/2018 9:24 PM, Chet Ramey wrote:
>> On 10/31/18 3:03 PM, Michael Felt wrote:
>> Hi,
>>
>> I finally got around to patching and packaging bash-4.4.23 and had to
>> run a "make distclean" because I had copied the old version and without
> On 10/31/2018 9:31 PM, Chet Ramey wrote:
>> On 10/31/18 3:13 PM, Michael Felt wrote:
>>
>> Running "make test", and I amy have forgotten something I did in the past.
>> a) running tests as root (initially)
>> b) ends with:
>> run-vredir
>&g
> On 11/1/2018 12:43 PM, Michael Felt wrote:
>>> I am mainly surprised by "process file table is full" - is there
>>> something specific I can do to look at this more closely?
>> No, it's expected. That script tests the behavior when the process&#x
Hi.
I don't actually use bash myself - so something that would be apparent
to a bash user is invisible to me.
As part of the packaging of bash-5.0.18 (i.e., 5.0 at patch level 18) I
ran the test suite.
a) is there a flag I can pass so that it ignores the UTF-8 tests? I do
not want to not build U
Just repeated this on a system with bash that I did not package - and I
get the same results:
BASH_VERSINFO=([0]="4" [1]="4" [2]="0" [3]="1" [4]="release"
[5]="powerpc-ibm-aix6.1.0.0")
BASH_VERSION='4.4.0(1)-release'
...
```
_=/usr/bin/bash
aixtools@gcc119:[/home/aixtools]PS1='$ '
$ unset v
$ ex
On 15/10/2020 16:11, k...@plushkava.net wrote:
> On 15/10/2020 08:03, Michael Felt wrote:
>
>> $ exec > $ exit
>> root@x065:[/data/prj/gnu/bash/bash-5.0.18]
>>
>> ```
>>
>> As you can see by the return of the original PS1 - the sub-shell
>> (./b
On 15/10/2020 16:21, Chet Ramey wrote:
> On 10/15/20 3:03 AM, Michael Felt wrote:
>> Hi.
>>
>> I don't actually use bash myself - so something that would be apparent
>> to a bash user is invisible to me.
>>
>> As part of the packaging of bash-5.0.1
10/15/20 3:03 AM, Michael Felt wrote:
>>> Hi.
>>>
>>> I don't actually use bash myself - so something that would be apparent
>>> to a bash user is invisible to me.
>>>
>>> As part of the packaging of bash-5.0.18 (i.e., 5.0 at patch level 18)
test for AIX. If
not, we can consider this thread 'closed'.
Sincerely,
Michael
On 16/10/2020 15:16, Chet Ramey wrote:
> On 10/16/20 6:31 AM, Michael Felt wrote:
>
>> OK. While - perhaps the root cause is differences in error-codes, or
>> something like that - and not t
I am using patch 2.7.0 - and I get the warnings about dangerous files (what
is a dangerous file I ask myself) - but patching proceeds without any
problems.
Michael
On Thu, Oct 2, 2014 at 11:09 PM, Chet Ramey wrote:
> On 9/30/14, 2:18 PM, Matthew Gessner wrote:
> > I apologize, but I somehow sen
I do not mind installing yacc :)
How about the redefine of mbchar_t ?
On Fri, Oct 23, 2015 at 2:45 PM, Chet Ramey wrote:
> On 10/22/15 3:47 PM, aixtools wrote:
>> On 2015-10-15 16:23, Chet Ramey wrote:
>>> The first beta release of bash-4.4 is now available with the URL
>>>
>>> ftp://ftp.cwru.ed
h", line 47.22: 1506-334 (S) Identifier mbchar_t has
already been defined on line 175 of "../src/bash-4.4/include/shmbchar.h".
make: 1254-004 The error code from the last command is 1.
This is from a build done from the beta release from 24 hours ago.
Michael
On Mon, Oct 26, 2015
Sent from my iPhone
> On 11 Mar 2021, at 18:15, Chet Ramey wrote:
>
> On 3/11/21 11:28 AM, Michael Felt wrote:
>> Hi,
>> Issue: AdoptOpenJDK build process makes bash calls in a particular way. An
>> abbreviated (shorter pathnames) example is:
>> ```
>&
Sent from my iPhone
> On 17 Apr 2019, at 01:37, Paul Wise wrote:
>
>> On Tue, 2019-04-16 at 14:57 -0400, Chet Ramey wrote:
>>
>> Why take so much effort to (imperfectly) figure out and display
>> things you already know?
>
> Correctness. If what the user knows
You mean think they know, bett
27 matches
Mail list logo
