From: "Milan P. Stanić" <mps@arvanta.net>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] [BUG] drbdadm_parser.c:1968:63: error: 'glob_t' has no member named 'gl_flags'
Date: Mon, 7 Nov 2022 13:08:14 +0100 [thread overview]
Message-ID: <Y2j1Lmr2afaEYvBu@m1> (raw)
Hi,
[ Please Cc to me, I'm not subscribed to this mailing list ]
I'm trying to build drbd-tools 9.22.0 on Alpine Linux which is based on
musl libc (and not glibc).
Build fail with this error:
-----------------------------
drbdadm_parser.c: In function 'include_stmt':
drbdadm_parser.c:1968:63: error: 'glob_t' has no member named 'gl_flags'
1968 | } else if (errno == ENOENT && glob_buf.gl_flags & GLOB_MAGCHAR) {
| ^
drbdadm_parser.c:1968:75: error: 'GLOB_MAGCHAR' undeclared (first use in this function)
1968 | } else if (errno == ENOENT && glob_buf.gl_flags & GLOB_MAGCHAR) {
| ^~~~~~~~~~~~
drbdadm_parser.c:1968:75: note: each undeclared identifier is reported only once for each function it appears in
make[1]: *** [<builtin>: drbdadm_parser.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/home/mps/aports/main/drbd-utils/src/drbd-utils-9.22.0/user/v9'
make: *** [Makefile:90: tools] Error 2
>>> ERROR: drbd-utils: build failed
-----------------------------
Musl libc glob.h doesn't have gl_flags nor GLOB_MAGCHAR because it is
non standard glibc extension.
I reverted https://github.com/LINBIT/drbd-utils/commit/4a1b590090bf676cdfb10c198505b95b9eeb3120
commit and then drbd-tools builds fine.
Not sure is this revert safe to push drbd-utils in next Alpine release
(which planned for next week) or there is better fix.
TIA
--
Kind regards
next reply other threads:[~2022-11-07 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 12:08 Milan P. Stanić [this message]
2022-11-14 8:52 ` [Drbd-dev] [BUG] drbdadm_parser.c:1968:63: error: 'glob_t' has no member named 'gl_flags' Roland Kammerer
2022-11-14 18:01 ` Milan P. Stanić
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y2j1Lmr2afaEYvBu@m1 \
--to=mps@arvanta.net \
--cc=drbd-dev@lists.linbit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.