Re: build failure without system extension macros

2024-05-16 Thread Chet Ramey
On 5/16/24 3:40 PM, Collin Funk wrote: Hi Chet, On 5/16/24 7:25 AM, Chet Ramey wrote: Yes. This was inspired by https://lists.gnu.org/archive/html/bug-bash/2024-04/msg00158.html I'm not sure if you have dealt with this particular one yet, but I would just get rid of the u_char, u_short, u_lo

Re: build failure without system extension macros

2024-05-16 Thread Collin Funk
Hi Chet, On 5/16/24 7:25 AM, Chet Ramey wrote: > Yes. This was inspired by > > https://lists.gnu.org/archive/html/bug-bash/2024-04/msg00158.html I'm not sure if you have dealt with this particular one yet, but I would just get rid of the u_char, u_short, u_long, types. They are old BSD stuff tha

Re: build failure without system extension macros

2024-05-16 Thread Chet Ramey
On 5/16/24 12:21 AM, Grisha Levit wrote: Since 9c430f6b changed some files to no longer include config.h, building with glibc and an -std= in CFLAGS fails because getopt, used in support/bashversion.c and mksyntax.c, is guarded by _POSIX_C_SOURCE >= 2 || _XOPEN_SOURCE Yes. This was inspired by

build failure without system extension macros

2024-05-15 Thread Grisha Levit
Since 9c430f6b changed some files to no longer include config.h, building with glibc and an -std= in CFLAGS fails because getopt, used in support/bashversion.c and mksyntax.c, is guarded by _POSIX_C_SOURCE >= 2 || _XOPEN_SOURCE support/bashversion.c:69:17: warning: implicit declaration of function