From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001083] Fix warnings on creating target.ld for i386 targets
Date: Sun, 02 Jan 2011 01:09:00 -0000 [thread overview]
Message-ID: <20110102010915.E03EC2F78004@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001083-104@http.bugs.ecos.sourceware.org/>
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001083
Jonathan Larmour <jifl@ecoscentric.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jifl@ecoscentric.com
--- Comment #5 from Jonathan Larmour <jifl@ecoscentric.com> 2011-01-02 01:09:11 GMT ---
(In reply to comment #3)
> Unfortunately, the compilers need substitution s/CFLAGS/ACTUAL_CFLAGS/ and in
> other places for those archs, i.e. on preprocessing stages (where compilers
> generate dependencies). There are more such places for 'powerpc' and 'sh'
> (sh2, sh3, ...) archs. My workaround just decrements the compiler's claims
> and does not calm builds there. Can I take risks and make all corrections
> without the ability to test all?
It seems safe. The difference between CFLAGS and ACTUAL_CFLAGS does not vary
between architectures. So if it is possible, it would be nice, thanks.
Jifl
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-01-02 1:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 18:33 [Bug 1001083] New: " bugzilla-daemon
2011-01-01 11:43 ` [Bug 1001083] " bugzilla-daemon
2011-01-01 12:38 ` bugzilla-daemon
2011-01-01 19:18 ` bugzilla-daemon
2011-01-01 19:35 ` bugzilla-daemon
2011-01-02 1:09 ` bugzilla-daemon [this message]
2011-01-02 14:00 ` bugzilla-daemon
2011-01-04 18:55 ` bugzilla-daemon
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=20110102010915.E03EC2F78004@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@ecos.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).