From: Alexey Neyman <noreply@github.com>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] f8ed70: Add support for noMMU xtensa
Date: Mon, 08 Apr 2019 15:11:00 -0000 [thread overview]
Message-ID: <crosstool-ng/crosstool-ng/push/refs/heads/master/e593d1-d0f484@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: f8ed7002c698a0833f7498a55b5badf905d36eee
https://github.com/crosstool-ng/crosstool-ng/commit/f8ed7002c698a0833f7498a55b5badf905d36eee
Author: Max Filippov <jcmvbkbc@gmail.com>
Date: 2019-03-23 (Sat, 23 Mar 2019)
Changed paths:
M scripts/build/kernel/linux.sh
Log Message:
-----------
Add support for noMMU xtensa
scripts/build/kernel/linux.sh only provides suffix to known
architectures when building toolchain targeting noMMU linux.
Add support for xtensa and assign uclinux suffix to it.
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
Commit: 4f360146eb582d7c994080a64e9e9e9e817bdbdb
https://github.com/crosstool-ng/crosstool-ng/commit/4f360146eb582d7c994080a64e9e9e9e817bdbdb
Author: Max Filippov <jcmvbkbc@gmail.com>
Date: 2019-03-23 (Sat, 23 Mar 2019)
Changed paths:
M scripts/build/libc/uClibc.sh
Log Message:
-----------
Fix uClibc build for noMMU target
uclibc_backend_once tries to build dummy shared libraries regardless of
whether shared libraries support for target is enabled or not, resulting
in build failure in noMMU bFLT configuration.
Only build dummy shared libraries when shared library support for target
is enabled.
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
Commit: d0f484f2566cfda1faaef193ef7316bca5dc8fb7
https://github.com/crosstool-ng/crosstool-ng/commit/d0f484f2566cfda1faaef193ef7316bca5dc8fb7
Author: Alexey Neyman <stilor@att.net>
Date: 2019-04-05 (Fri, 05 Apr 2019)
Changed paths:
M scripts/build/kernel/linux.sh
M scripts/build/libc/uClibc.sh
Log Message:
-----------
Merge pull request #1169 from jcmvbkbc/xtensa-fixes
noMMU xtensa fixes
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/e593d1e68d3c...d0f484f2566c
reply other threads:[~2019-04-08 15:11 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=crosstool-ng/crosstool-ng/push/refs/heads/master/e593d1-d0f484@github.com \
--to=noreply@github.com \
--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).