From: John Mills <Jmills@TGA.com>
To: 'eCos Discussion' <ecos-discuss@sourceware.cygnus.com>
Cc: John Mills <Jmills@TGA.com>
Subject: [ECOS] Tools-build Error and SH board questions
Date: Tue, 29 Jun 1999 15:02:00 -0000 [thread overview]
Message-ID: <FD7521AABD30D2118284006008AE0B6E03BFB4@ns1.tga.com> (raw)
Hello -
Question 1:
My latest build of ecosSWtools reports _compiler errors_ in building libm.a
for some 'sh/m*' targets - details follow. Are these serious? - any
suggestions?
Environment:
RH6.0 Linux, building from the RH6.0-patched GNUPro source tree
("redhat-908010"), configuring to:
--target=sh-hms \
--prefix=/usr/local/ecosSWtools-990319 \
[etc]
(1) warns it will not support 'target-libgloss' and
(2) reports compiler errors building 'libm.a' in some
target subdirectories.
(3) the overwhelming majority of the tools and libs now
seem to build fine.
Detail:
I attach an elided build/install-log, identifying (I hope) the offending
sections. I also tried building with the 'egcs' snapshots, but the GNUPro
sources seem to get further. (Thanks very much to any brave soul who looks
into the build log - I'll be happy to provide all or any other snippets of
the log upon request.)
Question 2:
I notice in the GNUPro sources there is a:
[...]/src/libgloss/sh/sh2lcevb.ld
This is a loadmap for the evaluation board I am using (EDK7045F). Has anyone
targeted this board with all or any of eCos? Has anyone got a working or
partial port of CygMon, or a correspondent for one of Hitachi's monitors for
this board?
Thanks for any leads -
John Mills, Sr. Software Engineer
TGA Technologies, Inc.
100 Pinnacle Way, Suite 140
e-mail: jmills@tga.com
Norcross, GA 30071-3633
Phone: 770-421-2100 ext.124 (voice)
770-449-7740 (FAX)
next reply other threads:[~1999-06-29 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-29 15:02 John Mills [this message]
1999-06-30 1:44 ` Jesper Skov
1999-06-30 5:56 ` Stan Shebs
1999-06-30 9:18 ` Daniel T. Schwager
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=FD7521AABD30D2118284006008AE0B6E03BFB4@ns1.tga.com \
--to=jmills@tga.com \
--cc=ecos-discuss@sourceware.cygnus.com \
/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).