From: Giacomo Tesio <giacomo@tesio.it>
To: newlib@sourceware.org
Subject: Porting newlib to a new operating system (build dependencies etc..)
Date: Mon, 27 Mar 2017 13:38:00 -0000 [thread overview]
Message-ID: <CAHL7psHOER1B1UfM7jnN3HHM=AZhzFQW1ZfHbg5FD16dPrnRYA@mail.gmail.com> (raw)
Hi, I'm porting newlib to Jehanne (http://jehanne.io/) to use it as a
POSIX façade.
I've noticed that many os developers just patch a specific version of
newlib and include that in their distribution, but I'd like to keep
the library updated by tracking the official git repository.
I've read that any contribution should be sent as a patch to this
mailing list, but I cannot find anything more specific about the
requirements of such patches and contributions. Right now, I'm
wondering how to produce such patches and I've found some difficulties
with `git diff`, but I'm also interested in the contribution process
itself (eg particular CLAs to sign and so on...).
BTW, I'm using the same (outdated) autotools that I use to build the
GCC cross compiler, but I've noticed that calling `autoreconf`
modifies several files tracked by git that are unrelated to the port
(various aclocal.m4, Makefile.am and so on).
What are the actual build requirements? Also, what is maintainer-mode?
Giacomo
reply other threads:[~2017-03-27 13:38 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='CAHL7psHOER1B1UfM7jnN3HHM=AZhzFQW1ZfHbg5FD16dPrnRYA@mail.gmail.com' \
--to=giacomo@tesio.it \
--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).