From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 30dc7e: Add UCLIBC_HAS_LFS as always-enabled.
Date: Tue, 24 Jan 2017 00:12:00 -0000 [thread overview]
Message-ID: <58869be3ef1c0_5f253faf916c313c494a3@hookshot-fe1-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 30dc7e94c998a4977e06bdf9e500b6e7fcabfaf8
https://github.com/crosstool-ng/crosstool-ng/commit/30dc7e94c998a4977e06bdf9e500b6e7fcabfaf8
Author: Alexey Neyman <stilor@att.net>
Date: 2017-01-23 (Mon, 23 Jan 2017)
Changed paths:
A patches/uClibc-ng/1.0.20/110-has-lfs.patch
A patches/uClibc-ng/1.0.21/110-has-lfs.patch
Log Message:
-----------
Add UCLIBC_HAS_LFS as always-enabled.
Buildroot checks for this feature.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: aa24e9d913fc9385538ed6d493c094b33ef4d356
https://github.com/crosstool-ng/crosstool-ng/commit/aa24e9d913fc9385538ed6d493c094b33ef4d356
Author: Alexey Neyman <stilor@att.net>
Date: 2017-01-23 (Mon, 23 Jan 2017)
Changed paths:
M config/libc/uClibc.in.2
M scripts/build/libc/uClibc.sh
Log Message:
-----------
Add selection for RPC
So that uClibc config can be matched to Buildroot's expectations via
the menu, without the need for a saved config.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: 65e037b654eb1dc1cbef649269969a3cf9aa4adc
https://github.com/crosstool-ng/crosstool-ng/commit/65e037b654eb1dc1cbef649269969a3cf9aa4adc
Author: Alexey Neyman <stilor@att.net>
Date: 2017-01-23 (Mon, 23 Jan 2017)
Changed paths:
M config/libc/uClibc.in.2
A patches/uClibc-ng/1.0.20/110-has-lfs.patch
A patches/uClibc-ng/1.0.21/110-has-lfs.patch
M scripts/build/libc/uClibc.sh
Log Message:
-----------
Merge pull request #552 from stilor/uclibc-ng-for-buildroot
Restore uClibc-ng usability in buildroot
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/76099962bfda...65e037b654eb
reply other threads:[~2017-01-24 0:12 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=58869be3ef1c0_5f253faf916c313c494a3@hookshot-fe1-cp1-prd.iad.github.net.mail \
--to=stilor@att.net \
--cc=crossgcc@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).