I was trying to cross-compile bash for musl libc. The configure script reports:
checking for working sbrk... configure: WARNING: cannot check working sbrk if
cross-compiling
yes
However, I don't believe musl libc supports sbrk. However, autoconf seems to
default
to assuming yes and sets the
Date:Mon, 6 Nov 2023 14:28:24 -0500
From:Chet Ramey
Message-ID: <0ab6075e-22bf-43cd-992c-b2476f626...@case.edu>
| On 11/6/23 10:48 AM, Mike Jonkmans wrote:
| > According to these docs (what I make of it), resolving is done
| > in steps, the first applicable
On 11/6/23 10:48 AM, Mike Jonkmans wrote:
POSIX Command Search
According to these docs (what I make of it), resolving is done in steps,
the first applicable step is used:
1) No slash in the name.
1a) Run the builtin if the name matches that of a Special Builtin.
1b) List several names that
Hi,
I have some remarks/questions on POSIX Command Search and Execution,
related to bash and some to POSIX itself.
Introduction
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_09_01_01
describes what to do when a simple command name needs to be resolved.
A
On Mon, Nov 06, 2023 at 08:56:11AM -0500, Chet Ramey wrote:
> The null string (NULL) and the empty string ("") are not the same thing.
If this is true, then the man page has many inconsistencies that need
to be cleared up. For example, in the definition of PATH:
PATH The search path
On Nov 06 2023, Chet Ramey wrote:
> If nullglob is set, the non-matching pattern expands to the null string,
> which is removed by word splitting.
Since filename expansion happens after word splitting, this cannot be
true.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196
On Mon, Nov 06, 2023 at 08:56:11AM -0500, Chet Ramey wrote:
> If nullglob is set, the non-matching pattern expands to the null string,
> which is removed by word splitting.
Well, I guess that is one way to look at it, but this explanation does
not make much sense in my opinion since the results
On 11/6/23 9:22 AM, Andreas Schwab wrote:
On Nov 06 2023, Chet Ramey wrote:
If nullglob is set, the non-matching pattern expands to the null string,
which is removed by word splitting.
Since filename expansion happens after word splitting, this cannot be
true.
Then maybe a better way to
On 11/5/23 5:15 AM, Emanuele Torre wrote:
Today, a user in the #bash IRC channel of libera.chat, misunderstood how
nullglob is supposed to work because is documented incorrectly in the
man page:
'nullglob'
If set, Bash allows filename patterns which match no files to
