From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: newlib <newlib@sourceware.org>
Subject: Regenerate newlib/newlib.hin?
Date: Mon, 11 Sep 2023 09:12:32 +0200 [thread overview]
Message-ID: <687108d5-4350-4833-8bd4-2e3ff458c498@embedded-brains.de> (raw)
Hello,
when I run "autoreconf" in "newlib", I get the following local changes:
diff --git a/newlib/newlib.hin b/newlib/newlib.hin
index e87a5eabbb..7a1d921d6e 100644
--- a/newlib/newlib.hin
+++ b/newlib/newlib.hin
@@ -375,6 +375,9 @@
/* nano version of malloc is used. */
#undef _NANO_MALLOC
+/* "The newlib version in string format." */
+#undef _NEWLIB_VERSION
+
/* Verify _REENT_CHECK macros allocate memory successfully. */
#undef _REENT_CHECK_VERIFY
@@ -422,4 +425,13 @@
/* Define if wide char orientation is supported. */
#undef _WIDE_ORIENT
+/* "The newlib minor version number." */
+#undef __NEWLIB_MINOR__
+
+/* "The newlib patch level." */
+#undef __NEWLIB_PATCHLEVEL__
+
+/* "The newlib major version number." */
+#undef __NEWLIB__
+
#endif /* !__NEWLIB_H__ */
Are these changes due to a local configuration or tooling issue or
should we check in these changes?
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
next reply other threads:[~2023-09-11 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 7:12 Sebastian Huber [this message]
2023-09-12 18:54 ` Hans-Bernhard Bröker
2023-10-15 9:21 ` Mike Frysinger
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=687108d5-4350-4833-8bd4-2e3ff458c498@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=newlib@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).