From: Mike Frysinger <vapier@gentoo.org>
To: Stefan Tauner <stefan.tauner@gmx.at>, newlib@sourceware.org
Subject: Re: [PATCH] libgloss: arm: break newlib dependency
Date: Mon, 9 Jan 2023 21:07:23 -0500 [thread overview]
Message-ID: <Y7zIWyMXre/Bsrlr@vapier> (raw)
In-Reply-To: <Y7vsjgVP64V1CAxL@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
On 09 Jan 2023 11:29, Corinna Vinschen wrote:
> On Jan 3 22:06, Mike Frysinger wrote:
> > On 04 Jan 2023 03:17, Stefan Tauner wrote:
> > > wouldn't it make sense to add the "include" directory itself to the
> > > build process(es) as include directory instead of prepending it to all
> > > #include statements?
> >
> > the include/ dir has headers that conflict with standard headers like
> > getopt.h. this causes build failures.
>
> What about using -idirafter instead?
that should work. newlib isn't using it today, so i didn't think we
wanted to start. if you're fine with it, i can try it.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-10 2:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 9:13 Mike Frysinger
2022-12-19 9:34 ` Corinna Vinschen
2022-12-19 10:08 ` Richard Earnshaw
2022-12-21 1:47 ` Mike Frysinger
2022-12-21 8:24 ` Corinna Vinschen
2022-12-22 22:03 ` Mike Frysinger
2023-01-03 14:56 ` Richard Earnshaw
2023-01-04 2:04 ` Mike Frysinger
2023-01-04 2:17 ` Stefan Tauner
2023-01-04 3:06 ` Mike Frysinger
2023-01-09 10:29 ` Corinna Vinschen
2023-01-10 2:07 ` Mike Frysinger [this message]
2023-01-10 8:43 ` Corinna Vinschen
2023-01-11 6:01 ` [PATCH v3] " Mike Frysinger
2023-01-11 9:14 ` Corinna Vinschen
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=Y7zIWyMXre/Bsrlr@vapier \
--to=vapier@gentoo.org \
--cc=newlib@sourceware.org \
--cc=stefan.tauner@gmx.at \
/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).