Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Roland Kammerer <roland.kammerer@linbit.com>
To: drbd-dev@lists.linbit.com
Cc: "Milan P. Stanić" <mps@arvanta.net>
Subject: Re: [Drbd-dev] [BUG] drbdadm_parser.c:1968:63: error: 'glob_t' has no member named 'gl_flags'
Date: Mon, 14 Nov 2022 09:52:41 +0100	[thread overview]
Message-ID: <Y3IB2V2TXOzNac1H@rck.sh> (raw)
In-Reply-To: <Y2j1Lmr2afaEYvBu@m1>

On Mon, Nov 07, 2022 at 01:08:14PM +0100, Milan P. Stanić wrote:
> 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).
> 
> [...]
> 
> Musl libc glob.h doesn't have gl_flags nor GLOB_MAGCHAR because it is
> non standard glibc extension.

thanks for reporting, this should be fixed in
https://github.com/LINBIT/drbd-utils/commit/33d5e8f7066116bd0a706c7cdda4950895164d34

> 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.

I think reverting for now is perfectly fine, this deserved a fix, but I
don't think it actually happened in the wild that often... Or you pick
the proposed fix, which would be a good test for us as well. Currently
I'm not sure when the next official release will be done, current gut
feeling is not enough interesting things people would wait for has have
happened.

Regards, rck

  reply	other threads:[~2022-11-14  8:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 12:08 [Drbd-dev] [BUG] drbdadm_parser.c:1968:63: error: 'glob_t' has no member named 'gl_flags' Milan P. Stanić
2022-11-14  8:52 ` Roland Kammerer [this message]
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=Y3IB2V2TXOzNac1H@rck.sh \
    --to=roland.kammerer@linbit.com \
    --cc=drbd-dev@lists.linbit.com \
    --cc=mps@arvanta.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox