From: Neal Becker <neal@ctd.comsat.com>
To: law@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: m68k-unknown-coff cross failure
Date: Fri, 05 Dec 1997 11:48:00 -0000 [thread overview]
Message-ID: <u9wwhjg1fo.fsf@neal.ctd.comsat.com> (raw)
In-Reply-To: <24788.881340976@hurl.cygnus.com>
>>>>> "Jeffrey" == Jeffrey A Law <law@hurl.cygnus.com> writes:
Jeffrey> In message < u9btyypnnm.fsf@neal.ctd.comsat.com >you write:
>> I retried with 971201, same results. I suppose I could try again
>> explicitly telling configure where to find the target includes, but as
>> you see from TOOL_INCLUDE_DIR it seems to have found them without
>> help.
Jeffrey> Well, as Mike Neuhauser noted in a previous message, there's an
Jeffrey> inconsistency in where configure & Makefile expect to put/find the
Jeffrey> target include files that we need to resolve.
See my recent post that hasn't been sent out to list yet. I finally
got this working.
The problem was that libgloss.h was included in gcc build, in which we
have:
/* Don't set the target flags, this is done by the linker script */
#undef LIB_SPEC
#define LIB_SPEC ""
That's why we always failed linking libiberty for the target. I
simply edited the specs file in the build/gcc directory to say:
*lib:
%{!shared:%{g*:-lg} %{!p:%{!pg:-lc}}%{p:-lc_p}%{pg:-lc_p}}
It's also true that the correct includes were not used, but
fortunately this was harmless in this case.
After making this change to specs the build completed. I have just
recompiled an example app for the target and loaded it into the
hardware, which is an mpeg2 satellite receiver, and it is working
normally.
next prev parent reply other threads:[~1997-12-05 11:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-01 12:31 Neal Becker
1997-12-01 17:20 ` Jeffrey A Law
1997-12-02 5:52 ` Neal Becker
1997-12-02 9:23 ` Jeffrey A Law
1997-12-03 5:46 ` Neal Becker
1997-12-05 8:53 ` Jeffrey A Law
1997-12-05 11:48 ` Neal Becker [this message]
1997-12-01 18:55 ` Robin Kirkham
1997-12-02 9:56 ` Jeffrey A Law
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=u9wwhjg1fo.fsf@neal.ctd.comsat.com \
--to=neal@ctd.comsat.com \
--cc=egcs@cygnus.com \
--cc=law@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).