From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 431821: Remove "pre-declaration" of config options
Date: Tue, 07 Feb 2017 06:10:00 -0000 [thread overview]
Message-ID: <589964b7dea50_8813fbf4ecddc3060262@hookshot-fe6-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 431821741f342ed0ee6e7b9b4b7b9dcb390f9f72
https://github.com/crosstool-ng/crosstool-ng/commit/431821741f342ed0ee6e7b9b4b7b9dcb390f9f72
Author: Alexey Neyman <stilor@att.net>
Date: 2017-02-06 (Mon, 06 Feb 2017)
Changed paths:
M config/target.in
Log Message:
-----------
Remove "pre-declaration" of config options
... these are apparently not needed with the current kconfig and only
result in warnings like "SYMBOL changed state" and "reassigning SYMBOL".
Perhaps, it was necessary to run kconfig without first generating
config.gen? But now all the targets that invoke $(CONF) have
`config_files` as a dependency.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: 82975ae7b0dfd03daa2d922925a971f1ab6b0ded
https://github.com/crosstool-ng/crosstool-ng/commit/82975ae7b0dfd03daa2d922925a971f1ab6b0ded
Author: Alexey Neyman <stilor@att.net>
Date: 2017-02-06 (Mon, 06 Feb 2017)
Changed paths:
M config/target.in
Log Message:
-----------
Merge pull request #579 from stilor/arch-32-warning
Remove "pre-declaration" of config options
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/46bfc8a4dc53...82975ae7b0df
reply other threads:[~2017-02-07 6:10 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=589964b7dea50_8813fbf4ecddc3060262@hookshot-fe6-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).