From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: "Arsen Arsenović" <arsen@gentoo.org>
Cc: Andreas Schwab <schwab@suse.de>,
Florian Weimer <fweimer@redhat.com>,
libc-alpha@sourceware.org
Subject: Re: [PATCH v3 2/4] libio: Remove the usage of __libc_IO_vtables
Date: Mon, 6 Mar 2023 16:20:31 -0300 [thread overview]
Message-ID: <aa40b2aa-da40-ca6a-4fa3-eb012e4a0cca@linaro.org> (raw)
In-Reply-To: <87ilfdlmg9.fsf@gentoo.org>
On 06/03/23 16:10, Arsen Arsenović wrote:
>
> Adhemerval Zanella Netto <adhemerval.zanella@linaro.org> writes:
>
>>> FWIW, I have an interest in making a new port (as time permits...), so
>>> please also add an...
>>>
>>> #else
>>> # error "Update the port!"
>>>
>>> ... or such, if you choose to do that.
>>>
>>
>> The usual way now is to provide arch specific files through sysdep, so
>> if a new target does not provide it either build will fail (if it
>> includes direct or indirectly it) or by running the testsuite (which
>> run install on a temporary file at build directory).
>
> I meant a kernel port (i.e. a third contender besides Hurd and Linux).
> I might've misunderstood you, though, and this might not be moving
> something OS-specific out of sysdeps/ - if so, disregard.
Check the patch I just submit [1]: the idea would be to just add a
new sysdep/<system>/bits/stdio_lim.h as similar to what Hurd and
Linux does.
https://patchwork.sourceware.org/project/glibc/patch/20230306191642.347001-3-adhemerval.zanella@linaro.org/
next prev parent reply other threads:[~2023-03-06 19:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 21:11 [PATCH v3 0/4] Remove --with-default-link option Adhemerval Zanella
2022-12-27 21:11 ` [PATCH v3 1/4] Move libc_freeres_ptrs and libc_subfreeres to hidden/weak functions Adhemerval Zanella
2023-03-04 17:37 ` Carlos O'Donell
2022-12-27 21:11 ` [PATCH v3 2/4] libio: Remove the usage of __libc_IO_vtables Adhemerval Zanella
2023-03-04 17:37 ` Carlos O'Donell
2023-03-06 13:43 ` Adhemerval Zanella Netto
2023-03-27 12:53 ` Carlos O'Donell
2023-03-06 14:58 ` Arsen Arsenović
2023-03-06 16:01 ` Adhemerval Zanella Netto
2023-03-06 16:31 ` Andreas Schwab
2023-03-06 16:39 ` Adhemerval Zanella Netto
2023-03-06 16:53 ` Andreas Schwab
2023-03-06 17:24 ` Adhemerval Zanella Netto
2023-03-06 18:17 ` Adhemerval Zanella Netto
2023-03-06 18:47 ` Arsen Arsenović
2023-03-06 18:53 ` Adhemerval Zanella Netto
2023-03-06 19:10 ` Arsen Arsenović
2023-03-06 19:20 ` Adhemerval Zanella Netto [this message]
2023-03-06 19:26 ` Arsen Arsenović
2023-03-06 16:23 ` Andreas Schwab
2022-12-27 21:11 ` [PATCH v3 3/4] Remove --with-default-link configure option Adhemerval Zanella
2023-03-04 17:39 ` Carlos O'Donell
2022-12-27 21:11 ` [PATCH v3 4/4] Remove set-hooks.h from generic includes Adhemerval Zanella
2023-03-04 17:42 ` Carlos O'Donell
2023-03-04 17:37 ` [PATCH v3 0/4] Remove --with-default-link option Carlos O'Donell
2023-03-06 13:43 ` Adhemerval Zanella Netto
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=aa40b2aa-da40-ca6a-4fa3-eb012e4a0cca@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=arsen@gentoo.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).