public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1001468] eCos GNU tools 4.6.2
Date: Sat, 04 Feb 2012 19:40:00 -0000 [thread overview]
Message-ID: <20120204193944.653602F78006@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001468-13@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=1001468
--- Comment #12 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2012-02-04 19:39:38 GMT ---
(In reply to comment #11)
> Thus, you can use (for start) configure options for GCC 4.3.2 from
> eCosCentric. As you can see eCosCentric built and some cross tools
> (libraries) as gmp, mpfr; it seems to me it must be used for the GCC
> 4.6.2 build too to prevent the host's dependencies and may be it will
> need more (or less) libraries (need to investigate).
It was much easier to find dependences than I thought. Required items to
build GCC 4.6.2 are described in GCC documentation :-)
gcc-4.6.2/INSTALL/prerequisites.html
It seems to me GCC build requires GMP, MPFR, MPC libraries (Necessary to
Build GCC). So, these libraries look like SHOULD requirements. And PPL,
CLooG (IMHO) look like COULD requirements (Necessary to build GCC with
the Graphite loop optimizations), and may be even WON'T requirement for
eCos.
Sergei
--
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:[~2012-02-04 19:40 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-28 17:48 [Bug 1001468] New: " bugzilla-daemon
2012-01-28 17:55 ` [Bug 1001468] " bugzilla-daemon
2012-01-28 17:57 ` bugzilla-daemon
2012-01-28 17:59 ` bugzilla-daemon
2012-01-28 18:00 ` bugzilla-daemon
2012-01-28 18:01 ` bugzilla-daemon
2012-01-28 18:02 ` bugzilla-daemon
2012-01-28 18:03 ` bugzilla-daemon
2012-01-28 18:03 ` bugzilla-daemon
2012-01-28 18:04 ` bugzilla-daemon
2012-01-28 18:04 ` bugzilla-daemon
2012-01-28 18:13 ` bugzilla-daemon
2012-01-31 20:39 ` bugzilla-daemon
2012-01-31 20:56 ` bugzilla-daemon
2012-02-03 8:43 ` bugzilla-daemon
2012-02-03 18:54 ` bugzilla-daemon
2012-02-04 19:40 ` bugzilla-daemon [this message]
2012-02-06 9:16 ` bugzilla-daemon
2012-02-11 16:23 ` bugzilla-daemon
2012-02-11 20:52 ` bugzilla-daemon
2012-02-11 21:53 ` bugzilla-daemon
2012-02-14 20:26 ` bugzilla-daemon
2012-02-14 22:07 ` bugzilla-daemon
2012-02-21 20:37 ` bugzilla-daemon
2012-02-24 12:29 ` bugzilla-daemon
2012-02-24 12:48 ` bugzilla-daemon
2012-02-26 16:29 ` bugzilla-daemon
2012-02-26 16:49 ` bugzilla-daemon
2012-02-28 14:04 ` bugzilla-daemon
2012-03-02 16:19 ` bugzilla-daemon
2012-03-03 13:48 ` bugzilla-daemon
2012-03-03 14:30 ` bugzilla-daemon
2012-03-03 19:46 ` bugzilla-daemon
2012-03-03 21:18 ` bugzilla-daemon
2012-03-10 23:46 ` bugzilla-daemon
2012-03-13 14:31 ` bugzilla-daemon
2012-03-13 16:20 ` bugzilla-daemon
2012-03-15 15:44 ` bugzilla-daemon
2012-03-15 21:43 ` bugzilla-daemon
2012-03-16 8:36 ` bugzilla-daemon
2012-03-16 16:09 ` bugzilla-daemon
2012-03-18 0:41 ` bugzilla-daemon
2012-03-18 0:43 ` bugzilla-daemon
2012-03-18 13:06 ` bugzilla-daemon
2012-03-19 1:50 ` bugzilla-daemon
2012-03-19 8:01 ` [Bug 1001468] eCos GNU tools 4.6.3 bugzilla-daemon
2012-03-30 15:01 ` bugzilla-daemon
2012-03-30 15:20 ` bugzilla-daemon
2012-04-26 15:33 ` bugzilla-daemon
2012-04-27 9:20 ` bugzilla-daemon
2012-04-27 14:37 ` bugzilla-daemon
2012-04-27 15:25 ` bugzilla-daemon
2012-04-27 16:16 ` bugzilla-daemon
2012-05-25 20:32 ` bugzilla-daemon
2012-05-25 20:39 ` bugzilla-daemon
2012-05-26 2:51 ` bugzilla-daemon
2012-05-26 6:45 ` bugzilla-daemon
2012-05-26 15:37 ` bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2012-01-28 17:48 [Bug 1001468] New: eCos GNU tools 4.6.2 bugzilla-daemon
2012-01-28 17:55 ` [Bug 1001468] " bugzilla-daemon
2012-01-28 17:57 ` bugzilla-daemon
2012-01-28 17:59 ` bugzilla-daemon
2012-01-28 18:00 ` bugzilla-daemon
2012-01-28 18:01 ` bugzilla-daemon
2012-01-28 18:02 ` bugzilla-daemon
2012-01-28 18:03 ` bugzilla-daemon
2012-01-28 18:03 ` bugzilla-daemon
2012-01-28 18:04 ` bugzilla-daemon
2012-01-28 18:04 ` bugzilla-daemon
2012-01-28 18:13 ` bugzilla-daemon
2012-01-31 20:39 ` bugzilla-daemon
2012-01-31 20:56 ` bugzilla-daemon
2012-02-03 8:43 ` bugzilla-daemon
2012-02-03 18:54 ` bugzilla-daemon
2012-02-04 19:40 ` bugzilla-daemon
2012-02-06 9:16 ` bugzilla-daemon
2012-02-11 16:23 ` bugzilla-daemon
2012-02-11 20:52 ` bugzilla-daemon
2012-02-11 21:53 ` bugzilla-daemon
2012-02-14 22:07 ` bugzilla-daemon
2012-02-24 12:29 ` bugzilla-daemon
2012-02-24 12:48 ` bugzilla-daemon
2012-02-26 16:28 ` bugzilla-daemon
2012-02-26 16:49 ` bugzilla-daemon
2012-02-28 14:04 ` bugzilla-daemon
2012-03-02 16:19 ` bugzilla-daemon
2012-03-03 13:48 ` bugzilla-daemon
2012-03-03 14:30 ` bugzilla-daemon
2012-03-03 19:46 ` bugzilla-daemon
2012-03-03 21:18 ` bugzilla-daemon
2012-03-10 23:46 ` bugzilla-daemon
2012-03-13 14:31 ` bugzilla-daemon
2012-03-13 16:20 ` bugzilla-daemon
2012-03-15 15:44 ` bugzilla-daemon
2012-03-15 21:43 ` bugzilla-daemon
2012-03-16 8:36 ` bugzilla-daemon
2012-03-16 16:09 ` bugzilla-daemon
2012-03-18 0:41 ` bugzilla-daemon
2012-03-18 0:43 ` bugzilla-daemon
2012-03-18 13:06 ` bugzilla-daemon
2012-03-19 1:51 ` 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=20120204193944.653602F78006@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-bugs@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).