From: Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gnulib: import getline
Date: Sun, 2 May 2021 00:50:38 -0400 [thread overview]
Message-ID: <YI4vnmuuIgygkJ0V@vapier> (raw)
In-Reply-To: <9b1cfe9d-2366-f626-f555-3ee5a99cddbc@polymtl.ca>
On 01 May 2021 20:49, Simon Marchi via Gdb-patches wrote:
> On 2021-05-01 8:46 p.m., Mike Frysinger wrote:
> > On 01 May 2021 20:39, Simon Marchi wrote:
> >> On 2021-05-01 6:09 p.m., Mike Frysinger via Gdb-patches wrote:
> >>> We use getline in sim today which breaks on older systems that are
> >>> compliant with the latest POSIX standard.
> >>
> >> I can't really parse that sentence. Using getline doesn't work on older
> >> systems, because those older systems are compliant with the latest POSIX
> >> standard? Huh? Wouldn't being compliant with the latest POSIX standard
> >> be a good thing?
> >
> > sorry, meant "not compliant". getline is in POSIX, but not all targets
> > support it. e.g. Windows (mingw) omit it.
>
> Ah ok, that makes more sense, thanks. Still, please mention the
> specific platform in the commit message. I always understand better
> with a concrete example.
sure, that's np.
gnulib: import getline
We use getline in sim today which breaks on older systems that are
not compliant with the latest POSIX standard. For example, Windows
(mingw) omits getline so we fail to build there.
next prev parent reply other threads:[~2021-05-02 4:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 22:09 Mike Frysinger via Gdb-patches
2021-05-02 0:39 ` Simon Marchi via Gdb-patches
2021-05-02 0:46 ` Mike Frysinger via Gdb-patches
2021-05-02 0:49 ` Simon Marchi via Gdb-patches
2021-05-02 4:50 ` Mike Frysinger via Gdb-patches [this message]
2021-05-04 15:03 ` Tom Tromey
2021-05-04 17:46 ` Mike Frysinger via Gdb-patches
2021-05-04 19:19 ` Tom Tromey
2021-05-04 19:49 ` Mike Frysinger via Gdb-patches
2021-05-04 20:10 ` Tom Tromey
2021-05-04 21:22 ` Mike Frysinger via Gdb-patches
2021-05-02 7:14 ` Eli Zaretskii via Gdb-patches
2021-05-02 14:14 ` Mike Frysinger via Gdb-patches
2021-05-02 14:48 ` Eli Zaretskii via Gdb-patches
2021-05-02 15:12 ` Mike Frysinger via Gdb-patches
2021-05-02 15:24 ` Eli Zaretskii via Gdb-patches
2021-05-02 15:47 ` Mike Frysinger via Gdb-patches
2021-05-02 16:06 ` Eli Zaretskii via Gdb-patches
2021-05-02 16:12 ` Mike Frysinger via Gdb-patches
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=YI4vnmuuIgygkJ0V@vapier \
--to=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=vapier@gentoo.org \
/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