From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: newlib@sourceware.org
Subject: How to regenerate newlib/newlib.hin?
Date: Wed, 28 Jun 2017 07:16:00 -0000 [thread overview]
Message-ID: <91884ee3-d430-0b68-0eb6-aac3aa7f97a6@embedded-brains.de> (raw)
Hello,
I struggle to add a new configuration option. How can I regenerate the
newlib/newlib.hin? I tried to use autoheader version 2.68:
autoheader: WARNING: Using auxiliary files such as `acconfig.h',
`config.h.bot'
autoheader: WARNING: and `config.h.top', to define templates for
`config.h.in'
autoheader: WARNING: is deprecated and discouraged.
autoheader:
autoheader: WARNING: Using the third argument of `AC_DEFINE' and
autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows one to define a
template without
autoheader: WARNING: `acconfig.h':
autoheader:
autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
autoheader: [Define if a function `main' is needed.])
autoheader:
autoheader: WARNING: More sophisticated templates can also be produced,
see the
autoheader: WARNING: documentation.
configure.in:251: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call
detected in body
../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from...
../libtool.m4:1080: _LT_SYS_MODULE_PATH_AIX is expanded from...
../libtool.m4:4213: _LT_LINKER_SHLIBS is expanded from...
../libtool.m4:5341: _LT_LANG_C_CONFIG is expanded from...
../libtool.m4:141: _LT_SETUP is expanded from...
../libtool.m4:67: LT_INIT is expanded from...
../libtool.m4:106: AM_PROG_LIBTOOL is expanded from...
configure.in:251: the top level
configure.in:251: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call
detected in body
../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from...
../libtool.m4:4213: _LT_LINKER_SHLIBS is expanded from...
../libtool.m4:5341: _LT_LANG_C_CONFIG is expanded from...
../libtool.m4:141: _LT_SETUP is expanded from...
../libtool.m4:67: LT_INIT is expanded from...
../libtool.m4:106: AM_PROG_LIBTOOL is expanded from...
configure.in:251: the top level
autoheader: warning: missing template: _NANO_MALLOC
autoheader: Use AC_DEFINE([_NANO_MALLOC], [], [Description])
autoheader: warning: missing template: _REENT_GLOBAL_ATEXIT
autoheader: warning: missing template: _RETARGETABLE_LOCKING
autoheader: warning: missing template: _WANT_REENT_GLOBAL_STDIO_STREAMS
autoheader: warning: missing template: _WANT_REGISTER_FINI
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
reply other threads:[~2017-06-28 7:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=91884ee3-d430-0b68-0eb6-aac3aa7f97a6@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).