Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups: comp.lang.c
Subject: Re: Linker error I've never seen before
Date: Thu, 09 Apr 2020 13:08:01 -0700
Organization: None to speak of
Lines: 21
Message-ID: <87y2r4juce.fsf@nosuchdomain.example.com>
References: <2aab30ec-f3e7-4b46-9be5-bbc5ddd01f91@googlegroups.com> <3085aa51-dee1-466f-8800-0978c2f0afef@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: reader02.eternal-september.org; posting-host="721337e81c79c5f5d54b212b11a7fff7"; logging-data="5942"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19l0Ogq+r7lHQFq5q5wvTuW"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
Cancel-Lock: sha1:9MZkviNRJSDqXrlsIIRlKnpiOy0= sha1:6xf9IwvH3DSEo8iRU+1fQXpzW/g=
Xref: csiph.com comp.lang.c:151279

Frederick Gotham <cauldwell.thomas@gmail.com> writes:
> I got it to compile with this option passed to the linker:
>
>     -Wl,--allow-shlib-undefined

No, you got it to *link* with that option.  It was already compiling
(or you wouldn't have gotten to the point of a linker error in the
first place).

I hadn't known about the "--allow-shlib-undefined" option before,
but it looks like it just inhibits error messages.  I wouldn't be
surprised if the resulting program failed at run time.

I see you've fixed the problem by defining your own log_error et
al functions.  I don't know whether you posted the above before or
afte that post.

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips Healthcare
void Void(void) { Void(); } /* The recursive call of the void */