From: Warner Losh <imp@bsdimp.com>
To: Adam Thornton <athornton@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Debugging help sought
Date: Thu, 6 Aug 2020 23:49:44 -0600 [thread overview]
Message-ID: <CANCZdfqzdXEJ+zOf8u8GvbYR9bWMhA_v3_EzcVbu-z3ipNN0uA@mail.gmail.com> (raw)
In-Reply-To: <CAP2nic1f0u9VM6BHZ2tNtmkKGWiuYkNx2ihFFT21zDDav2+7bQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
It's likely too many. Ld used to have lots of fixed sized arrays... I had
to hack on the 2.10.1BSD to change supported ar formats and noticed. Also
had to tweak some of the constants to get something much bigger compiling.
The BSD ld had overlay suppot merged into it, but was otherwise quite
similar to V7, though I've not done a deep dive into ld from v7...
Tl;dr: chances are good more, smaller files will work.
Warner
On Thu, Aug 6, 2020, 10:30 PM Adam Thornton <athornton@gmail.com> wrote:
> So maybe I missed a symbol when I was trying to make everything unique in
> 8 chars? There are no external symbols; all that's in my forth.h are
> macros and typedefs.
>
> Adam
>
> On Thu, Aug 6, 2020 at 5:35 PM Warner Losh <imp@bsdimp.com> wrote:
>
>>
>>
>> On Thu, Aug 6, 2020, 9:48 AM Paul Winalski <paul.winalski@gmail.com>
>> wrote:
>>
>>> On 8/5/20, Adam Thornton <athornton@gmail.com> wrote:
>>> >
>>> > $ cc -o 4th forth.c
>>> > ld:forth.o: Local symbol botch
>>>
>>> I hate error messages like that. Would it have been that much extra
>>> trouble for ld to tell you which symbol caused the problem?
>>>
>>
>> It's a relocation entry it can't find a symbol for that's the issue...
>>
>> Warner
>>
>>> -Paul W.
>>>
>>
[-- Attachment #2: Type: text/html, Size: 2656 bytes --]
next prev parent reply other threads:[~2020-08-07 5:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 1:28 Adam Thornton
2020-08-06 2:01 ` Jim Capp
2020-08-06 3:04 ` Warner Losh
2020-08-06 3:08 ` Warner Losh
2020-08-06 5:55 ` Adam Thornton
2020-08-06 4:57 ` Dave Horsfall
2020-08-06 7:16 ` Otto Moerbeek
2020-08-06 15:47 ` Paul Winalski
2020-08-06 16:09 ` Larry McVoy
2020-08-06 16:19 ` Paul Winalski
2020-08-06 16:24 ` Larry McVoy
2020-08-06 23:41 ` Adam Thornton
2020-08-07 0:35 ` Warner Losh
2020-08-07 4:30 ` Adam Thornton
2020-08-07 5:49 ` Warner Losh [this message]
2020-08-07 5:54 ` Adam Thornton
2020-08-07 16:07 Noel Chiappa
2020-08-07 17:11 ` John Cowan
2020-08-07 20:48 ` Warner Losh
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=CANCZdfqzdXEJ+zOf8u8GvbYR9bWMhA_v3_EzcVbu-z3ipNN0uA@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=athornton@gmail.com \
--cc=tuhs@tuhs.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 NNTP newsgroup(s).