The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Adam Thornton <athornton@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Debugging help sought
Date: Thu, 6 Aug 2020 21:30:37 -0700	[thread overview]
Message-ID: <CAP2nic1f0u9VM6BHZ2tNtmkKGWiuYkNx2ihFFT21zDDav2+7bQ@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfoCk4LfKPi_eHCQry8cC_Ete+rZv8F=SYU1WhA+c1DyYw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 695 bytes --]

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: 1705 bytes --]

  reply	other threads:[~2020-08-07  4:31 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 [this message]
2020-08-07  5:49       ` Warner Losh
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=CAP2nic1f0u9VM6BHZ2tNtmkKGWiuYkNx2ihFFT21zDDav2+7bQ@mail.gmail.com \
    --to=athornton@gmail.com \
    --cc=imp@bsdimp.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).