From: "David O'Shea" <dcoshea@gmail.com>
To: linux-8086 <linux-8086@vger.kernel.org>
Subject: Debugging "ld86: text segment too large for 16bit"
Date: Sun, 18 Jun 2017 20:39:52 +0930 [thread overview]
Message-ID: <CAN0DjM1v0qnw6HSRLm+ZoayU_C2Hb-woCRSthXGVkJ69y2U7QQ@mail.gmail.com> (raw)
Hi all,
I thought I'd try porting JOVE to see if an Emacs clone with a few
more features would work, but I get (would it be correct to say "the
dreaded"?) "ld86: text segment too large for 16bit".
I can't seem to find any options to bcc or ld86 to give me more
information to help me avoid the limitation. For example, it might be
nice to have a map file so I can see the sizes of all the symbols;
maybe I could identify some library functions that would be good to
avoid, or some feature in JOVE that I could try stripping out. Is
there some way to generate a map file during linking that I missed?
I'm assuming the intent is that you use objdump after linking to
generate a map, so the linker doesn't produce one while it's running?
It looks like it might not be hard to at least modify the error
message to show the actual number of bytes that needed to be fit into
the segment. I guess that might be useful - if it's 128K I may as
well give up :) If it's a few K, perhaps GCC would help me!
Thanks in advance,
David
reply other threads:[~2017-06-18 11:09 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=CAN0DjM1v0qnw6HSRLm+ZoayU_C2Hb-woCRSthXGVkJ69y2U7QQ@mail.gmail.com \
--to=dcoshea@gmail.com \
--cc=linux-8086@vger.kernel.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).